Manage customer inquiries from email & web forms with Slack & Google Sheets
This n8n workflow is designed to centralize the management and tracking of customer inquiries received through multiple channels (email and web forms).
Who's it for?
- Customer support teams
- Marketing teams
- Sales teams
- Small to medium-sized businesses
- Individuals looking to streamline customer inquiry processes
How it works / What it does
This workflow is designed to automatically collect, process, route, and track customer inquiries from different sources.
-
Multi-Channel Input: The workflow listens for inquiries from both incoming emails and web form submissions.
- Email Trigger: Monitors a specific inbox for sent emails.
- Webhook - Web Form: Listens for web form data submitted to a designated endpoint.
-
Data Extraction and Parsing:
- Extract Email Content: Extracts HTML content from incoming emails to get a clean text message.
- Parse Email Data: Extracts relevant information from the email, such as customer name, email address, subject, message, received timestamp, source ("email"), and inquiry type (e.g., "urgent", "billing", "general") based on the subject line.
- Parse Webhook Data: Extracts customer name, email, subject, message, received timestamp, source ("webform"), and inquiry type from the web form data based on the provided type or a default of "general".
-
Merge Inquiries: The parsed email and web form inquiry data are combined into a single stream for continued processing.
-
Route by Inquiry Type: The workflow then routes the inquiries based on the extracted
inquiryType.- Urgent Inquiries: Inquiries marked as "urgent" are routed to a specific Slack channel for immediate alerts.
- General Inquiries: Inquiries marked as "general" are notified in another Slack channel.
- Billing Inquiries: Inquiries marked as "billing" are routed to the general inquiries channel, or can be customized for a separate channel if needed.
-
Save to Google Sheets: All inquiry data is logged into a Google Sheet, which serves as a central repository, including details like customer name, email, subject, message, source, received timestamp, and inquiry type.
-
Send Auto-Reply Email: Customers receive an automated email reply confirming that their inquiry has been successfully received.
How to set up
-
Google Sheets:
- Create a new spreadsheet in your Google Drive.
- Name the first sheet "Inquiries" and create the following header row:
customerName,customerEmail,subject,message,source,receivedAt,inquiryType. - In the 'Save to Google Sheets' node, configure the Spreadsheet ID and Sheet Name. Link your Google Sheets credentials.
-
Email Trigger (IMAP):
- Set up the 'Email Trigger' node to connect to your IMAP email account. Test it to ensure it correctly listens for incoming emails before activating the workflow.
-
Webhook - Web Form:
- Copy the Webhook URL from the 'Webhook - Web Form' node and configure your web form to submit data to it. Ensure your web form sends fields like
name,email,subject,message, andtypein JSON format.
- Copy the Webhook URL from the 'Webhook - Web Form' node and configure your web form to submit data to it. Ensure your web form sends fields like
-
Slack:
- Configure your Slack credentials to connect to your Slack workspace.
- Update the relevant Slack Channel IDs in both the 'Notify Urgent - Slack' and 'Notify General - Slack' nodes for sending notifications for urgent and general inquiries.
-
Gmail:
- Set up your Gmail credentials to connect to your Gmail account.
- Ensure the 'Send Auto-Reply Email' node is correctly linked to your sending Gmail account.
Requirements
- An n8n instance
- A Google Sheets account
- An IMAP-enabled email account
- A Slack workspace
- A Gmail account
- A basic web form (to integrate with the Webhook node)
How to customize the workflow
- Add more Inquiry Types: You can add more specific inquiry types (e.g., "technical support", "returns") by adding more rules in the 'Route by Inquiry Type' node.
- Additional Notification Channels: To integrate other notification systems (e.g., Microsoft Teams, Discord, SMS) beyond Slack, create new routing outputs and add new notification nodes for the desired service.
- CRM Integration: Instead of or in addition to saving data to Google Sheets, you can add new nodes to connect to CRM systems like Salesforce, HubSpot, or others.
- Prioritization and Escalation: Implement more complex logic to trigger escalation processes or prioritization rules based on inquiry type or keywords.
- AI Sentiment Analysis: Integrate an AI node to analyze the sentiment of inquiry messages and route or prioritize them accordingly.
`
n8n Workflow: Manage Customer Inquiries from Email & Web Forms with Slack & Google Sheets
This n8n workflow automates the process of handling customer inquiries, whether they originate from email or a web form. It centralizes these inquiries by logging them in a Google Sheet and notifying a Slack channel, streamlining communication and tracking.
What it does
This workflow performs the following steps:
- Triggers on new emails or web form submissions: It can be activated by new emails received via IMAP or by an incoming webhook request (e.g., from a web form submission).
- Extracts and standardizes data: For email triggers, it extracts relevant information. For both triggers, it then standardizes the incoming data into a consistent format.
- Logs inquiry to Google Sheets: The standardized inquiry details are appended as a new row in a specified Google Sheet, creating a central record.
- Notifies Slack channel: A message containing the inquiry details is posted to a designated Slack channel, alerting the team to a new customer inquiry.
- Sends confirmation email (optional): For inquiries that are identified as "email" type, it sends a confirmation email back to the sender.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n instance: A running n8n instance.
- Email Account (IMAP): An email account configured for IMAP access, with credentials set up in n8n.
- Google Sheets Account: A Google account with access to Google Sheets, with credentials set up in n8n. You'll need to specify the Spreadsheet ID and Sheet Name.
- Slack Account: A Slack workspace with an app and bot token, with credentials set up in n8n. You'll need to specify the Channel ID.
- Webhook Source (Optional): If using the Webhook trigger, a system or form capable of sending HTTP POST requests to the generated webhook URL.
Setup/Usage
- Import the workflow: Download the provided JSON and import it into your n8n instance.
- Configure Credentials:
- Email Trigger (IMAP): Configure your IMAP credentials.
- Google Sheets: Configure your Google Sheets credentials (OAuth2 recommended).
- Slack: Configure your Slack credentials (OAuth2 recommended).
- Gmail: Configure your Gmail credentials (OAuth2 recommended) if you intend to send confirmation emails.
- Configure Nodes:
- Email Trigger (IMAP):
- Specify the
Folderto monitor (e.g., "INBOX"). - Set the
Check Intervalas desired.
- Specify the
- Webhook: If using, copy the
Webhook URLafter saving the workflow and configure your web form or external system to send POST requests to this URL. - Edit Fields (Set): Review and adjust the fields being set to match the incoming data from your email and webhook triggers. Ensure that
type,subject,from, andbodyfields are correctly mapped. - Google Sheets:
- Enter your
Spreadsheet ID. - Enter the
Sheet Namewhere inquiries should be logged. - Ensure the column headers in your Google Sheet match the fields being sent (e.g.,
Type,Subject,From,Body).
- Enter your
- Slack:
- Enter the
Channel IDwhere notifications should be posted. - Customize the
Textmessage to include relevant inquiry details using expressions (e.g.,{{ $json.type }}: New inquiry from {{ $json.from }} - {{ $json.subject }}).
- Enter the
- Switch: This node routes the workflow based on the
typefield.Case 0: Checks iftypeis 'email'.
- Gmail: If the
Switchnode routes to this path, a confirmation email will be sent.- Configure the
Toaddress using an expression like{{ $json.from }}. - Set the
SubjectandBodyof the confirmation email.
- Configure the
- Email Trigger (IMAP):
- Activate the workflow: Once configured, activate the workflow to start processing inquiries.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation
PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.