Skip to main content

Automate customer support with Mintlify documentation & Zendesk AI agent

Workflow preview

Workflow preview
100%
Automate customer support with Mintlify documentation & Zendesk AI agent preview
Open on n8n.io

Important notice

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

1. Workflow Overview

This n8n workflow automates support ticket handling with AI driven classification, response generation, and safety checks. Responses are based solely on your Mintlify documentation, ensuring accura...

Best for

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

Tools used

@n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.lmchatopenrouter, n8n-nodes-base.switch, n8n-nodes-base.webhook, n8n-nodes-base.code, n8n-nodes-base.httprequest, n8n-nodes-base.noop

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
Automate customer support with Mintlify documentation & Zendesk AI agent
Workflow name
Automate customer support with Mintlify documentation & Zendesk AI agent

This n8n workflow automates support ticket handling with AI-driven classification, response generation, and safety checks. Responses are based solely on your Mintlify documentation, ensuring accuracy, consistency, and reduced manual effort in customer support.

✅ Trigger: New Ticket Received The workflow is triggered whenever a new support ticket is created.

🔍 Check for Assignee If the ticket is already assigned to a human agent, the bot does nothing and exits. If the ticket is unassigned, the bot continues processing.

🔢 Bot Response Count Check The workflow checks how many times the bot has already responded to this ticket. If the bot has replied more than 3 times, it stops and waits for a human to take over. This prevents endless loops and flags potentially complex cases for review.

🧠 AI-Based Ticket Categorization An AI model analyzes the ticket content and classifies it into one of the following categories:

  1. 🧾 Billing → Sends a predefined billing-related message.
  2. 📢 Advertising → Automatically deletes the ticket.
  3. 🚨 Fraud → Sends a predefined fraud-related message.
  4. ❓ Other → Proceeds to generate a dynamic response.

🤖 Mintlify Integration For tickets categorized as "Other", the customer’s question is sent to the Mintlify API, which returns a documentation-based answer.

✍️ AI Response Formatter The raw response from Mintlify is passed to an AI model that: Summarizes and rewrites the answer in a clear, friendly tone Limits the response to 120 words Adds conversational elements like “Hi,” “Thanks,” and a proper closing

🛡️ AI Confidence Filter A second AI model reviews the formatted response to ensure it sounds confident and accurate. It looks for uncertainty phrases like:

  • “I’m not sure”
  • “I don’t have enough information”
  • “It depends…” If the response is flagged as uncertain, the workflow stops and waits for a human agent to respond.

📤 Send Response & Update Ticket If the response passes the confidence check: The reply is sent to the customer The ticket status is updated to “Pending”

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 - AI Agent

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

Block 2 - OpenRouter Chat Model

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenRouter - lmChatOpenRouter
Config choices
Version 1

Block 3 - Message router

Type / Role
n8n-nodes-base.switch - switch
Config choices
Version 3.2

Block 4 - New ticket?

Type / Role
n8n-nodes-base.switch - switch
Config choices
Version 3.2

Block 5 - Webhook

Type / Role
n8n-nodes-base.webhook - webhook
Config choices
Version 2

Block 6 - Parse conversation

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 7 - Look for Mintlify topicId

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 8 - Add Mintlify topicID to ticket

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 9 - Create Mintlify Chat Topic

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 10 - Add Mintlify topicId to ticket tags

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 11 - Delete ticket

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 12 - Check if human agent is assigned

Type / Role
n8n-nodes-base.switch - switch
Config choices
Version 3.2

Block 13 - If human assigned, don't reply

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

Block 14 - OpenRouter Chat Model1

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenRouter - lmChatOpenRouter
Config choices
Version 1

Block 15 - Check uncertainty

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

Block 16 - If more that x replies, don't reply

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

Block 17 - If uncertain, don't reply

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

Block 18 - OpenRouter Chat Model2

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenRouter - lmChatOpenRouter
Config choices
Version 1

Block 19 - Message classifier

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

Block 20 - Uncertainty router

Type / Role
n8n-nodes-base.switch - switch
Config choices
Version 3.2

Block 21 - Billing suspected - escalate

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 22 - Fraud suspected - escalate

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 23 - Mintlify generated response (new)

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 24 - Mintlify generated response (existing)

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Showing the first 24 of 32 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow Automate customer support with Mintlify documentation & Zendesk AI agent
Complexity advanced
Nodes 32
Categories Ticket Management, AI Chatbot
Author Alex Gurinovich
Published 19 Jun 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/5046/5046.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 Automate customer support with Mintlify documentation & Zendesk AI agent do?

This n8n workflow automates support ticket handling with AI driven classification, response generation, and safety checks. Responses are based solely on your Mintlify documentation, ensuring accura...

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 Chatbot use case.