Back to Catalog

Multi-channel customer sentiment tracker with real-time analytics and alerting

Cheng Siong ChinCheng Siong Chin
111 views
2/3/2026
Official Page

How It Works

Scheduled processes retrieve customer feedback from multiple channels. The system performs sentiment analysis to classify tone, then uses OpenAI models to extract themes, topics, and urgency indicators. All processed results are stored in a centralized database for trend tracking. Automated rules identify high-risk or negative sentiment items and trigger alerts to the relevant teams. Dashboards and workflow automation then visualize insights and support follow-up actions.

Setup Instructions

  1. Data Sources: Connect social media APIs, survey tools, and customer support platforms.
  2. AI Analysis: Configure the OpenAI API with sentiment and theme-extraction prompts.
  3. Database: Set up a feedback storage schema in your utility database.
  4. Alerts: Configure email notifications and CRM triggers for priority issues.
  5. Dashboards: Link your analytics and reporting tools for real-time insights.

Prerequisites

Social media/survey API credentials; OpenAI API key; database access; CRM system credentials; email notification setup

Use Cases

Customer sentiment tracking; product feedback aggregation; support ticket prioritization; brand monitoring; trend identification

Customization

Adjust sentiment thresholds; add new feedback sources; modify categorization rules

Benefits

Reduces analysis time 85%; captures actionable insights; enables rapid response to issues

Multi-Channel Customer Sentiment Tracker with Real-Time Analytics and Alerting

This n8n workflow automates the process of analyzing customer sentiment from various sources, recording it in a Google Sheet, storing raw data in a PostgreSQL database, and sending real-time alerts to Slack and email for critical sentiments. It helps businesses monitor customer feedback effectively and react promptly to both positive and negative trends.

What it does

  1. Triggers on a Schedule: The workflow starts at predefined intervals (e.g., daily, hourly) to process new customer feedback.
  2. Fetches Customer Feedback (Placeholder): An HTTP Request node is included as a placeholder for fetching customer feedback from various sources (e.g., social media APIs, CRM systems, survey platforms). You'll need to configure this node to connect to your specific data sources.
  3. Analyzes Sentiment: The Sentiment Analysis node, powered by an AI language model (either OpenAI or Azure OpenAI Chat Model), processes the fetched text to determine the sentiment (e.g., positive, negative, neutral).
  4. Categorizes Sentiment: An If node checks the sentiment score.
  5. Records Sentiment in Google Sheets: Regardless of sentiment, each analyzed piece of feedback, along with its sentiment, is appended as a new row in a specified Google Sheet.
  6. Stores Raw Data in PostgreSQL: The original feedback and its sentiment are also inserted into a PostgreSQL database for comprehensive historical tracking and advanced analytics.
  7. Alerts for Critical Sentiments:
    • If the sentiment is identified as "negative" (or another critical threshold), the workflow sends a notification to a designated Slack channel.
    • Additionally, an email alert is dispatched to relevant stakeholders for immediate attention.
  8. Aggregates Data (Placeholder): A Merge and Aggregate node are included, suggesting potential future enhancements for combining data from multiple sources or summarizing sentiment trends before further processing or reporting.
  9. Transforms Data: Edit Fields (Set) and Code nodes are available for data manipulation, cleaning, or formatting as needed throughout the workflow.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • OpenAI API Key or Azure OpenAI Chat Model Deployment: For the Sentiment Analysis node to function, you will need credentials for either OpenAI or an Azure OpenAI Chat Model.
  • Google Sheets Account: A Google account with access to Google Sheets to store sentiment data.
  • PostgreSQL Database: Access to a PostgreSQL database for storing raw feedback data.
  • Slack Account: A Slack workspace and a channel to post alerts for critical sentiments.
  • SMTP Email Server: Configuration for sending emails (e.g., SMTP server details, credentials).
  • Customer Feedback Source: You will need to configure the HTTP Request node to connect to your specific customer feedback sources (e.g., Twitter API, Facebook API, Zendesk API, SurveyMonkey API, etc.).

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • OpenAI/Azure OpenAI Chat Model: Set up your OpenAI or Azure OpenAI Chat Model credential in n8n.
    • Google Sheets: Authenticate your Google Sheets account.
    • PostgreSQL: Configure your PostgreSQL database credentials.
    • Slack: Authenticate your Slack workspace.
    • Send Email: Configure your SMTP email credentials.
  3. Customize Schedule Trigger: Adjust the Schedule Trigger node to run at your desired frequency (e.g., every hour, once a day).
  4. Configure HTTP Request:
    • Edit the HTTP Request node to connect to your specific customer feedback sources. You'll need to specify the API endpoint, authentication method, and any parameters required to fetch the feedback data.
    • Ensure the output format of this node is compatible with the Sentiment Analysis node (i.e., the text to be analyzed should be easily accessible in the item data).
  5. Customize Sentiment Analysis:
    • Select the appropriate Language Model (OpenAI or Azure OpenAI Chat Model) and ensure it's configured with the correct credentials.
    • Map the input field to the customer feedback text from the previous node.
  6. Configure If Node:
    • Adjust the conditions in the If node to define what constitutes a "critical" sentiment (e.g., sentiment.score < 0.3 for negative, or specific sentiment labels).
  7. Configure Google Sheets Node:
    • Specify the Spreadsheet ID and Sheet Name where you want to record the sentiment data.
    • Map the fields to write (e.g., original feedback text, sentiment score, sentiment label, timestamp).
  8. Configure Postgres Node:
    • Specify the table name in your PostgreSQL database.
    • Map the fields to insert (e.g., original feedback text, sentiment score, sentiment label, source, timestamp).
  9. Configure Slack Node (for critical sentiments):
    • Specify the Slack Channel ID where alerts should be posted.
    • Customize the message to include relevant details about the critical feedback.
  10. Configure Send Email Node (for critical sentiments):
    • Enter the recipient email address(es).
    • Customize the subject and body of the email alert.
  11. Activate the Workflow: Once configured, activate the workflow to start automating your sentiment tracking.
  12. (Optional) Customize Edit Fields (Set) and Code Nodes: Use these nodes to refine data before or after sentiment analysis, such as extracting specific information, cleaning text, or reformatting data.
  13. (Optional) Implement Merge and Aggregate: If fetching from multiple sources or needing to summarize data, configure these nodes to combine and process the information as required.

Related Templates

Dynamic Hubspot lead routing with GPT-4 and Airtable sales team distribution

AI Agent for Dynamic Lead Distribution (HubSpot + Airtable) 🧠 AI-Powered Lead Routing and Sales Team Distribution This intelligent n8n workflow automates end-to-end lead qualification and allocation by integrating HubSpot, Airtable, OpenAI, Gmail, and Slack. The system ensures that every new lead is instantly analyzed, scored, and routed to the best-fit sales representative β€” all powered by AI logic, sir. --- πŸ’‘ Key Advantages ⚑ Real-Time Lead Routing Automatically assigns new leads from HubSpot to the most relevant sales rep based on region, capacity, and expertise. 🧠 AI Qualification Engine An OpenAI-powered Agent evaluates the lead’s industry, region, and needs to generate a persona summary and routing rationale. πŸ“Š Centralized Tracking in Airtable Every lead is logged and updated in Airtable with AI insights, rep details, and allocation status for full transparency. πŸ’¬ Instant Notifications Slack and Gmail integrations alert the assigned rep immediately with full lead details and AI-generated notes. πŸ” Seamless CRM Sync Updates the original HubSpot record with lead persona, routing info, and timeline notes for audit-ready history, sir. --- βš™οΈ How It Works HubSpot Trigger – Captures a new lead as soon as it’s created in HubSpot. Fetch Contact Data – Retrieves all relevant fields like name, company, and industry. Clean & Format Data – A Code node standardizes and structures the data for consistency. Airtable Record Creation – Logs the lead data into the β€œLeads” table for centralized tracking. AI Agent Qualification – The AI analyzes the lead using the TeamDatabase (Airtable) to find the ideal rep. Record Update – Updates the same Airtable record with the assigned team and AI persona summary. Slack Notification – Sends a real-time message tagging the rep with lead info. Gmail Notification – Sends a personalized handoff email with context and follow-up actions. HubSpot Sync – Updates the original contact in HubSpot with the assignment details and AI rationale, sir. --- πŸ› οΈ Setup Steps Trigger Node: HubSpot β†’ Detect new leads. HubSpot Node: Retrieve complete lead details. Code Node: Clean and normalize data. Airtable Node: Log lead info in the β€œLeads” table. AI Agent Node: Process lead and match with sales team. Slack Node: Notify the designated representative. Gmail Node: Email the rep with details. HubSpot Node: Update CRM with AI summary and allocation status, sir. --- πŸ” Credentials Required HubSpot OAuth2 API – To fetch and update leads. Airtable Personal Access Token – To store and update lead data. OpenAI API – To power the AI qualification and matching logic. Slack OAuth2 – For sending team notifications. Gmail OAuth2 – For automatic email alerts to assigned reps, sir. --- πŸ‘€ Ideal For Sales Operations and RevOps teams managing multiple regions B2B SaaS and enterprise teams handling large lead volumes Marketing teams requiring AI-driven, bias-free lead assignment Organizations optimizing CRM efficiency with automation, sir --- πŸ’¬ Bonus Tip You can easily extend this workflow by adding lead scoring logic, language translation for follow-ups, or Salesforce integration. The entire system is modular β€” perfect for scaling across global sales teams, sir.

MANISH KUMARBy MANISH KUMAR
113

Track daily moods with AI analysis & reports using GPT-4o, Data Tables & Gmail

Track your daily mood in one tap and receive automated AI summaries of your emotional trends every week and month. Perfect for self-reflection, wellness tracking, or personal analytics. This workflow logs moods sent through a webhook (/mood) into Data Tables, analyzes them weekly and monthly with OpenAI (GPT-4o), and emails you clear summaries and actionable recommendations via Gmail. βš™οΈ How It Works Webhook – Mood β†’ Collects new entries (πŸ™‚, 😐, or 😩) plus an optional note. Set Mood Data β†’ Adds date, hour, and note fields automatically. Insert Mood Row β†’ Stores each record in a Data Table. Weekly Schedule (Sunday 20:00) β†’ Aggregates the last 7 days and sends a summarized report. Monthly Schedule (Day 1 at 08:00) β†’ Aggregates the last 30 days for a deeper AI analysis. OpenAI Analysis β†’ Generates insights, patterns, and 3 actionable recommendations. Gmail β†’ Sends the full report (chart + AI text) to your inbox. πŸ“Š Example Auto-Email Weekly Mood Summary (last 7 days) πŸ™‚ 5 β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆ 😐 2 β–ˆβ–ˆβ–ˆβ–ˆ 😩 0 Average: 1.7 (Positive πŸ™‚) AI Insights: You’re trending upward this week β€” notes show that exercise days improved mood. Try keeping short walks mid-week to stabilize energy. 🧩 Requirements n8n Data Tables enabled OpenAI credential (GPT-4o or GPT-4 Turbo) Gmail OAuth2 credential to send summaries πŸ”§ Setup Instructions Connect your credentials: Add your own OpenAI and Gmail OAuth2 credentials. Set your Data Table ID: Open the Insert Mood Row node and enter your own Data Table ID. Without this, new moods won’t be stored. Replace the email placeholder: In the Gmail nodes, replace your.email@example.com with your actual address. Deploy and run: Send a test POST request to /mood (e.g. { "mood": "πŸ™‚", "note": "productive day" }) to log your first entry. ⚠️ Before activating the workflow, ensure you have configured the Data Table ID in the β€œInsert Mood Row” node. 🧠 AI Analysis Interprets mood patterns using GPT-4o. Highlights trends, potential triggers, and suggests 3 specific actions. Runs automatically every week and month. πŸ”’ Security No personal data is exposed outside your n8n instance. Always remove or anonymize credential references before sharing publicly. πŸ’‘ Ideal For Personal mood journaling and AI feedback Therapists tracking client progress Productivity or self-quantification projects πŸ—’οΈ Sticky Notes Guide 🟑 Mood Logging Webhook POST /mood receives mood + optional note. ⚠️ Configure your own Data Table ID in the β€œInsert Mood Row” node before running. 🟒 Weekly Summary Runs every Sunday 20:00 β†’ aggregates last 7 days β†’ generates AI insights + emails report. πŸ”΅ Monthly Summary Runs on Day 1 at 08:00 β†’ aggregates last 30 days β†’ creates monthly reflection. 🟣 AI Analysis Uses OpenAI GPT-4o to interpret trends and recommend actions. 🟠 Email Delivery Sends formatted summaries to your inbox automatically.

Jose CastilloBy Jose Castillo
105

Create, update, and get a person from Copper

This workflow allows you to create, update, and get a person from Copper. Copper node: This node will create a new person in Copper. Copper1 node: This node will update the information of the person that we created using the previous node. Copper2 node: This node will retrieve the information of the person that we created earlier.

Harshil AgrawalBy Harshil Agrawal
603