Skip to main content

AI-powered customer feedback analysis & routing for Gmail, Zendesk, Slack & Pipedrive

Workflow preview

Workflow preview
100%
AI-powered customer feedback analysis & routing for Gmail, Zendesk, Slack & Pipedrive preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Who's it for This workflow is for Customer Success, Product, and Support teams who need to centralize and analyze unstructured customer feedback. It automates the process of identifying key themes ...

Best for

  • Ticket Management automation workflows
  • AI Summarization automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.manualtrigger, n8n-nodes-base.set, @n8n/n8n-nodes-langchain.lmchatopenai, @n8n/n8n-nodes-langchain.memorybufferwindow, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.outputparserstructured, n8n-nodes-base.gmailtool, n8n-nodes-base.pipedrivetool

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by PollupAI.

Original n8n.io source

1.1 Workflow description

Title
AI-powered customer feedback analysis & routing for Gmail, Zendesk, Slack & Pipedrive
Workflow name
AI-powered customer feedback analysis & routing for Gmail, Zendesk, Slack & Pipedrive

Who's it for

This workflow is for Customer Success, Product, and Support teams who need to centralize and analyze unstructured customer feedback. It automates the process of identifying key themes from various communication channels, allowing you to proactively address issues, track feature requests, and understand the voice of the customer without manual effort.

What it does

This workflow uses a powerful chain of AI agents to process customer feedback from end to end. It begins by using a Data Agent to gather all recent customer interactions from multiple sources, including Gmail, Pipedrive, Zendesk, and Slack.

Once the raw data is collected, a second AI Chain reads all the text and compresses it into concise, actionable "signals." A third AI Chain then takes these signals and intelligently clusters them into shared topics, assigning each a human-readable label like "Billing," "Performance," or "Feature Request."

Finally, a fourth AI Agent acts as a dispatcher. It analyzes the clustered topics and follows a set of routing rules defined in its prompt to take the appropriate action. It uses its tools to automatically create a Zendesk ticket for product feedback, send a Slack message for billing issues, create a Notion page for training opportunities, or send a direct email alert for high-risk accounts.

How to set up

To get this workflow running, you will need to configure the credentials and parameters for the following nodes:

  1. Configure Credentials: Add your credentials for the Config: Set LLM for Agents node and all of the Tool nodes (Gmail, Pipedrive, Zendesk, Slack, and Notion).
  2. Set Initial Parameters: In the Set: Initial Parameters node, update the placeholder email address and the Slack channel name for billing alerts.
  3. Update Slack Search Channel: In the Tool: Search Slack Messages node, set the channel you want the agent to search for feedback in.
  4. Activate Workflow: Once configured, you can run the workflow manually to start the analysis.

Requirements

  • An account with an LLM provider, such as OpenAI.
  • Accounts for the services you wish to connect (Gmail, Pipedrive, Zendesk, Slack, Notion).
  • This workflow requires n8n's Langchain community nodes to be installed on your instance.

How to customize the workflow

This workflow's logic is primarily driven by AI prompts, making it highly customizable:

  • AI Prompts: Adjust the prompts in any of the AI Agent or AI Chain nodes to change the data gathering, analysis, clustering, or routing rules to fit your business needs.
  • Data Sources: Add, remove, or swap out the "Tool" nodes in the AI Agent: Gather Customer Feedback section to connect to different data sources like Intercom, Salesforce, or a database.
  • Triggers: Replace the Manual Trigger with a Schedule Trigger to run the analysis automatically on a daily or weekly basis.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Manual Trigger: Start VOC Analysis

Type / Role
n8n-nodes-base.manualTrigger - manualTrigger
Config choices
Version 1

Block 2 - Set: Initial Parameters

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 3 - Config: Set LLM for Agents

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices
Version 1.2

Block 4 - Config: Set Agent Memory

Type / Role
@n8n/n8n-nodes-langchain.memoryBufferWindow - memoryBufferWindow
Config choices
Version 1.3

Block 5 - AI Agent: Gather Customer Feedback

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 2.2

Block 6 - AI: Structure Feedback Data

Type / Role
@n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices
Version 1.3

Block 7 - Tool: Get Gmail Messages

Type / Role
n8n-nodes-base.gmailTool - gmailTool
Config choices
Version 2.1

Block 8 - Tool: Get Pipedrive Notes

Type / Role
n8n-nodes-base.pipedriveTool - pipedriveTool
Config choices
Version 1

Block 9 - Tool: Get Zendesk Tickets

Type / Role
n8n-nodes-base.zendeskTool - zendeskTool
Config choices
Version 1

Block 10 - Tool: Search Slack Messages Export to Sheets

Type / Role
n8n-nodes-base.slackTool - slackTool
Config choices
Version 2.3

Block 11 - AI Chain: Extract Key Signals

Type / Role
@n8n/n8n-nodes-langchain.chainLlm - chainLlm
Config choices
Version 1.7

Block 12 - AI: Structure Key Signals

Type / Role
@n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices
Version 1.3

Block 13 - AI Chain: Cluster Signals into Topics

Type / Role
@n8n/n8n-nodes-langchain.chainLlm - chainLlm
Config choices
Version 1.7

Block 14 - AI: Structure Clustered Topics Export to Sheets

Type / Role
@n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices
Version 1.3

Block 15 - AI Agent: Route Topics to Actions

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 2.2

Block 16 - Tool: Create Zendesk Ticket

Type / Role
n8n-nodes-base.zendeskTool - zendeskTool
Config choices
Version 1

Block 17 - Tool: Send Email Alert

Type / Role
n8n-nodes-base.gmailTool - gmailTool
Config choices
Version 2.1

Block 18 - Tool: Create Notion Page

Type / Role
n8n-nodes-base.notionTool - notionTool
Config choices
Version 2.2

Block 19 - Note: Data Gathering

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 20 - Note: Analysis Chain

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 21 - Note: Action Agent

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 22 - Workflow Documentation

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 23 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow AI-powered customer feedback analysis & routing for Gmail, Zendesk, Slack & Pipedrive
Complexity advanced
Nodes 23
Categories Ticket Management, AI Summarization
Author PollupAI
Published 16 Oct 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/9782/9782.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does AI-powered customer feedback analysis & routing for Gmail, Zendesk, Slack & Pipedrive do?

Who's it for This workflow is for Customer Success, Product, and Support teams who need to centralize and analyze unstructured customer feedback. It automates the process of identifying key themes ...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Ticket Management, AI Summarization use case.