Skip to main content

Detect and route customer escalations with Claude, Slack and Linear

Workflow preview

Workflow preview
100%
Detect and route customer escalations with Claude, Slack and Linear preview
Open on n8n.io

1. Workflow Overview

Quick Overview This workflow receives support messages via a webhook, normalizes payloads from Gmail, Zendesk, Intercom, and HelpScout, and uses Anthropic Claude to detect escalation signals and se...

Best for

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

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.webhook, n8n-nodes-base.respondtowebhook, n8n-nodes-base.code, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.lmchatanthropic, @n8n/n8n-nodes-langchain.outputparserstructured, n8n-nodes-base.if

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Monfort N. Brian | 宁俊.

Original n8n.io source

1.1 Workflow description

Title
Detect and route customer escalations with Claude, Slack and Linear
Workflow name
Detect and route customer escalations with Claude, Slack and Linear

Quick Overview

This workflow receives support messages via a webhook, normalizes payloads from Gmail, Zendesk, Intercom, and HelpScout, and uses Anthropic Claude to detect escalation signals and severity, then posts alerts to Slack and creates Linear tickets for actionable cases.

How it works

  1. Receives an inbound support message via a POST webhook.
  2. Normalizes the incoming payload (Gmail, Zendesk, Intercom, HelpScout, or a raw test payload) into a consistent schema with customer details, subject, body text, and a source URL.
  3. Sends the normalized message to Anthropic Claude and parses the response into structured JSON containing escalation flags, severity, trigger phrases, a summary, and a suggested reply opening.
  4. Stops processing silently when the message is not an escalation (severity is none).
  5. Builds a formatted Slack alert and Linear issue payload, including SLA guidance, detected signals, and links back to the original conversation.
  6. Posts the escalation alert to a configured Slack channel.
  7. Creates a Linear ticket for critical, high, and medium severity escalations and sends a Slack DM to a manager for critical and high cases.

Setup

  1. Add an Anthropic API credential for the Anthropic Chat Model node.
  2. Add a Slack OAuth2 credential, set the target channel (for example, #escalations), and set the manager’s Slack user ID for direct messages.
  3. Add a Linear OAuth2 credential and replace the placeholder Linear team ID used when creating tickets.
  4. Copy the webhook URL from the webhook trigger and configure Gmail/Zendesk/Intercom/HelpScout (or your custom source) to POST message payloads to it in one of the supported formats.

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 - Sticky Note

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

Block 2 - Sticky Note1

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

Block 3 - Sticky Note2

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

Block 4 - Sticky Note3

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

Block 5 - Receive Message

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

Block 6 - Acknowledge Receipt

Type / Role
n8n-nodes-base.respondToWebhook - respondToWebhook
Config choices
Version 1.1

Block 7 - Normalize Inbound Message

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

Block 8 - Classify Escalation

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

Block 9 - Anthropic Chat Model

Type / Role
@n8n/n8n-nodes-langchain.lmChatAnthropic - lmChatAnthropic
Config choices
Version 1.3

Block 10 - Structured Output Parser

Type / Role
@n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices
Version 1.2

Block 11 - Build Actions

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

Block 12 - If Escalation

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.3

Block 13 - Post to Slack

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.4

Block 14 - If Create Ticket

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.3

Block 15 - Create Linear Ticket

Type / Role
n8n-nodes-base.linear - linear
Config choices
Version 1.1

Block 16 - If Notify Manager

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.3

Block 17 - Notify Manager

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.4

3. Summary Table

Workflow Detect and route customer escalations with Claude, Slack and Linear
Complexity advanced
Nodes 17
Categories Ticket Management, AI Summarization
Author Monfort N. Brian | 宁俊
Published 15 Jun 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/16393/16393.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 Detect and route customer escalations with Claude, Slack and Linear do?

Quick Overview This workflow receives support messages via a webhook, normalizes payloads from Gmail, Zendesk, Intercom, and HelpScout, and uses Anthropic Claude to detect escalation signals and se...

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