Autonomous customizable support chatbot on Intercom + Discord thread reports
Click here to access this Workflow for free.
Connect your own LLM-boosted chatbot to Intercom (f*** their overly priced FlN Agent), and stay in touch on Discord
This workflow connects your Intercom chat system with your own AI Agent and sends a complete log of each conversation to Discord using threads. It allows you to run a fully automated support system while maintaining full visibility of the bot's behavior in real time.
For every new conversation in Intercom, a thread is created in a specified Discord channel. Each message from the user, the AI, and even manual human responses is logged to the thread, offering full traceability and transparency.
You also have fine-grained control over the AI agent. By simply clicking the ⭐️ star in Intercom’s UI, support agents can instantly pause or resume AI responses for a specific chat — no coding or config changes needed.
Requirements
- A working n8n instance
- An Intercom account with permission to set up webhooks
- A Discord bot with the following permissions:
Send MessagesCreate Public/Private ThreadsManage Threads
- API credentials for your preferred LLM (OpenAI is used by default)
- Google Chrome or any browser to access Intercom’s UI
Setup
-
Intercom:
- Go to Intercom’s webhook settings.
- Add a webhook that listens to new incoming messages and points to the Webhook URL in this n8n workflow.
- Make sure to send full conversation data.
-
Discord:
- Create a Discord bot and invite it to your server with the required permissions.
- In the Discord + Token node at the top of the workflow:
- Add your bot token
- Add the ID of the channel where threads should be created
-
LLM / AI Agent:
- By default, the workflow uses OpenAI via HTTP Request.
- You can substitute it with any LLM provider of your choice.
- Make sure to set up your credentials in n8n and select them in the HTTP nodes.
-
HTTP Authentication Tips:
- For both Intercom and Discord API calls, it's recommended to create credentials in n8n's Credential Manager.
- Then, assign those credentials inside each HTTP Request node for a cleaner setup.
Usage
- When a new conversation starts in Intercom, a Discord thread is created automatically.
- Each message — user input, AI response, and human reply — is logged into the Discord thread in real time.
- The AI replies automatically unless the ⭐️ star is checked in Intercom:
- ☆ Unchecked = AI replies enabled
- ⭐️ Checked = AI replies disabled, human takeover enabled
This gives you on-the-fly control of each conversation’s automation level directly from the Intercom inbox.
Customization
- You can replace OpenAI with any LLM that provides a compatible API.
- Discord channel ID, thread naming, and message formatting can be customized to match your team’s preferences.
- You can expand the workflow to handle events like conversation closure or satisfaction ratings for deeper analytics.
If you need any help, or have any question, feel free to come discuss about it on Telegram
n8n Autonomous Customizable Support Chatbot for Intercom/Discord Thread Reports
This n8n workflow automates the process of handling incoming support requests, leveraging AI to understand the intent, retrieve relevant information, and generate appropriate responses or actions. It's designed to create a more efficient and intelligent support system.
Description
This workflow acts as an autonomous, customizable support chatbot. It receives incoming messages (likely from a webhook, suggesting integration with platforms like Intercom or Discord), processes them using an AI agent, and then routes the output to either generate a response or perform a specific action, such as creating a report. The AI agent utilizes a chat model, memory, and a Pinecone vector store for contextual understanding and information retrieval.
What it does
- Receives Incoming Data: The workflow is triggered by an incoming webhook, expecting a payload containing a support request or message.
- Initial Data Preparation: It sets specific fields on the incoming data, likely to standardize the input for the AI agent.
- AI Agent Processing: The core of the workflow, an AI Agent, processes the input. This agent is configured with:
- OpenAI Chat Model: To understand natural language and generate human-like responses.
- Simple Memory: To maintain conversational context within a session.
- Pinecone Vector Store: To retrieve relevant information from a knowledge base, enabling the chatbot to answer questions based on pre-existing data.
- OpenAI Embeddings: Used by the Pinecone Vector Store for semantic search.
- Output Filtering: The AI Agent's output is then filtered based on a condition, likely to differentiate between a direct AI response and a command/action.
- Conditional Routing (Switch): Depending on the filtered output, the workflow routes the data to different branches:
- True Branch (AI Response): If the AI determines a direct response is needed, it proceeds to generate and send that response.
- False Branch (Action/Report): If the AI detects a need for an action (e.g., creating a report), it proceeds down this path.
- Action/Report Generation:
- HTTP Request: Sends an HTTP request, likely to an external system (e.g., a reporting tool, another API) to create a report or perform a specific action.
- Intercom Integration: Integrates with Intercom, suggesting it can create or update conversations, or send messages within Intercom based on the AI's determination.
- Data Aggregation and Splitting: The workflow includes
AggregateandSplit Outnodes, which are likely used to manage data structures, potentially combining or separating information before or after processing by the AI or external services. - Final Response/Action: The workflow concludes by either sending an AI-generated response back (likely via the initial webhook or a platform-specific node like Intercom) or completing an external action.
Prerequisites/Requirements
- n8n Instance: A running n8n instance to host the workflow.
- Webhook Endpoint: An external system (e.g., Intercom, Discord, a custom application) configured to send messages/requests to the n8n webhook URL.
- OpenAI API Key: For the OpenAI Chat Model and Embeddings.
- Pinecone Account and API Key: For the Pinecone Vector Store (requires a pre-populated Pinecone index with your knowledge base).
- Intercom Account and Credentials: If using the Intercom node for communication.
- External API/Service Credentials: Any credentials required for the
HTTP Requestnode if it interacts with another external service for reporting or other actions.
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Webhook:
- Activate the "Webhook" node and copy its URL.
- Configure your external system (e.g., Intercom, Discord bot, custom application) to send POST requests to this URL with the relevant message payload.
- Set up Credentials:
- OpenAI: Create an OpenAI credential in n8n and link it to the "OpenAI Chat Model" and "Embeddings OpenAI" nodes.
- Pinecone: Create a Pinecone credential in n8n and link it to the "Pinecone Vector Store" node. Ensure your Pinecone index is set up and populated with the data you want the AI to reference.
- Intercom: Create an Intercom credential in n8n and link it to the "Intercom" node.
- Customize AI Agent:
- Review the configuration of the "AI Agent" node, including the prompt, tools, and other settings, to align with your specific support needs and knowledge base.
- Adjust the "OpenAI Chat Model" settings (e.g., model, temperature) as needed.
- Configure Logic Nodes:
- Review and adjust the conditions in the "Filter" and "Switch" nodes to accurately route messages based on the AI Agent's output and your desired workflow.
- Customize HTTP Request (if applicable):
- If the "HTTP Request" node is used for reporting or other actions, configure its URL, method, headers, and body to match the API of your target service.
- Activate the Workflow: Once all configurations are complete, activate the workflow.
The workflow will now listen for incoming messages, process them through the AI agent, and respond or take action accordingly.
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 Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte