Workflow Templates

Workflow Name: 👻 Exception Flow Template was created in n8n v1.90.2 Skill Level: Low Categories: n8n, Chatbot Stacks Error Trigger Slack node What this workflow does? This is a n8n Error Workflow. It will trigger when there is an error in another workflow. When this happens, it then tries to send an error notification to the preset Slack channel. How it works The Error Trigger node will trigger when there is an error in another workflow, as long as that workflow is set up to do so. A error notification will be sent to the Slack Channel. Set up instructions Create you Slack credentials, refer to n8n integration documentation for more information. Set up the Channel in 👻 Exception Alert node. For any n8n workflows to trigger this, switch to that workflow, select menu > settings, and set the Error Workflow to 👻 Exception Flow. How to adjust it to your needs Although this workflow template is part of the AI Chatbot Call Center Series, it could be used with any n8n workflows. Update the Channel in 👻 Exception Alert to your own channel https://chatpaylabs.com/blog/part-8-build-your-own-ai-chatbot-call-center-general-exception-flow-production-ready-n8n-workflow-free-download-

This workflow allows you to create, update and get a contact using the SendGrid node. Based on your use-case, you may want to add contacts to SendGrid from a different email service or from your CRM. Fetch the information of the contact using the node of that service. Connect the node with the SendGrid node and reference the value from the node.

This workflow allows you to create a post a Reddit and add a comment on the post. Reddit node: This node creates a post in the subreddit n8n. If you want to create a post in a different subreddit, enter the name of that subreddit instead. Reddit1 node: This node gets the post that we created previously. It returns the data like the post ID, title of the post, content of the post, etc. Reddit2 node: This node adds a comment on the post that we created earlier.

This workflow allows you to create, update and get a post using the Discourse node. Discourse node: This node creates a new post under a category. Based on your use-case, you can select a different category. Discourse1 node: This node updates the content of the post. Discourse2 node: This node fetches the node that we created using the Discourse node. Based on your use-case, you can add or remove nodes to connect Discourse to different services.

Support Director Agent with Customer Support Team Description Complete AI-powered customer support department with a Support Director agent orchestrating specialized support team members for comprehensive customer service operations. Overview This n8n workflow creates a comprehensive customer support department using AI agents. The Support Director agent analyzes support requests and delegates tasks to specialized agents for tier 1 support, technical assistance, customer success, knowledge management, escalation handling, and quality assurance. Features Strategic Support Director agent using OpenAI O3 for complex support decision-making Six specialized support agents powered by GPT-4.1-mini for efficient execution Complete customer support lifecycle coverage from first contact to resolution Automated technical troubleshooting and documentation creation Customer success and retention strategies Escalation management for priority issues Quality assurance and performance monitoring Team Structure Support Director Agent**: Strategic support oversight and task delegation (O3 model) Tier 1 Support Agent**: First-line support, basic troubleshooting, account assistance Technical Support Specialist**: Complex technical issues, API debugging, integrations Customer Success Advocate**: Onboarding, feature adoption, retention strategies Knowledge Base Manager**: Help articles, FAQs, documentation creation Escalation Handler**: Priority issues, VIP customers, crisis management Quality Assurance Specialist**: Support quality monitoring, performance analysis How to Use Import the workflow into your n8n instance Configure OpenAI API credentials for all chat models Deploy the webhook for chat interactions Send support requests via chat (e.g., "Customer can't connect to our API endpoint") The Support Director will analyze and delegate to appropriate specialists Receive comprehensive support solutions and documentation Use Cases Complete Support Cycle**: Inquiry triage → Resolution → Follow-up → Quality review Technical Documentation**: API troubleshooting guides, integration manuals Customer Onboarding**: Welcome sequences, feature tutorials, training materials Escalation Management**: VIP support protocols, complaint resolution procedures Quality Monitoring**: Response evaluation, team performance analytics Knowledge Base**: Self-service content creation, FAQ optimization Requirements n8n instance with LangChain nodes OpenAI API access (O3 for Support Director, GPT-4.1-mini for specialists) Webhook capability for chat interactions Optional: Integration with CRM, helpdesk, or ticketing systems Cost Optimization O3 model used only for strategic Support Director decisions GPT-4.1-mini provides 90% cost reduction for specialist tasks Parallel processing enables simultaneous agent execution Solution template library reduces redundant response generation Integration Options Connect to helpdesk systems (Zendesk, Freshdesk, Intercom, etc.) Integrate with CRM platforms (Salesforce, HubSpot, etc.) Link to knowledge base systems (Confluence, Notion, etc.) Connect to monitoring tools for proactive support Building Blocks Disclaimer Important Note: This workflow is designed as a foundational building block for your customer support automation. While it provides a comprehensive multi-agent framework, you may need to customize prompts, add specific integrations, or modify agent behaviors to match your exact business requirements and support processes. Consider this a starting point that can be extended and tailored to your unique customer support needs. Contact & Resources Website**: nofluff.online YouTube**: @YaronBeen LinkedIn**: Yaron Been Tags #CustomerSupport #HelpDesk #TechnicalSupport #CustomerSuccess #SupportAutomation #QualityAssurance #KnowledgeManagement #EscalationManagement #ServiceExcellence #CustomerExperience #n8n #OpenAI #MultiAgentSystem #SupportTech #CX #Troubleshooting #CustomerCare #SupportOps

This workflow sends a file to a Notion database of your choosing when a new file is created in a specific Google Drive folder. Prerequisites Notion account and Notion credentials. Google account and Google credentials. Google Drive folder to monitor for new files. How it works When a Google Drive file is created in the folder you specified, the workflow sends the file to the Notion database you created. The workflow uses the On file upload node to trigger the workflow when a new file is created in the folder. The Create database page node creates a new page in the Notion database you created. Setup Create a Notion database called "My Google Drive Files" with the following columns: Filename Google Drive File Share the database to n8n. In the n8n workflow, click on the Create database page node and select the database you created in step 1. In Google Drive, create a folder and navigate to it. Copy the URL of the Google Drive folder you are currently in. In the n8n workflow, add the folder URL to On file upload node.

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.

This workflow allows you to get all the slides from a presentation and get thumbnails of pages. Google Slides node: This Google Slides node will get all the slides from a presentation. Google Slides1 node: This node will return thumbnails of the pages that were returned by the previous node. Based on your use case, to upload the thumbnails to Dropbox, Google Drive, etc, you can use the respective nodes.

This workflow allows you to create, update, and get an item from Webflow. Webflow node: This node will create a new collection of the type Team Members in Webflow. If you want to create a collection with a different type, use that type instead. Webflow1 node: This node will update the item that we created using the previous node. Webflow2 node: This node will retrieve the information of the object that we created earlier.

This workflow allows you to create, update, and retrieve a record from FileMaker. FileMaker node: This node will create a new record in FileMaker. FileMaker1 node: This node will add a new field to the record that we created in the previous node. FileMaker2 node: This node will get the information about the record that we created earlier.

This workflow allows you to create, update and get a task in Microsoft To Do. Microsoft To Do node: This node will create a task with the importance High in the Tasks list. You can select a different list as well as the importance level. Microsoft To Do1 node: This node will update the status of the task that we created in the previous node. Microsoft To Do2 node: This node will get the task that we created earlier.

This workflow allows you to add, commit, and push changes to a git repository. Git node: This node will add the README.md file to the staging area. If you want to add a different file, enter the path of that file instead. Git1 node: This node will commit all the changes that were added to the staging area by the previous node. Git2 node: This node will return the commit logs of your repository. Git3 node: This node will push the changes to a cloud repository.