Review Zendesk escalations with OpenAI, Qdrant, Slack and human approval

by Faraz Shoaib ✓ · 1 views · created 2026-09-15 · Ticket Management, AI RAG

What this workflow does

This workflow has 95 nodes and runs when an HTTP POST request hits its webhook URL (plus 2 other triggers). Along the way it connects Postgres, Redis and Slack. It also calls api.openai.com over HTTP.

How it runs

Trigger: When an HTTP POST request hits its webhook URL (plus 2 other triggers).

1. Validate event (Code): runs custom JavaScript code
2. Validate outcome payload (Code): runs custom JavaScript code
3. Find stalled executions (Postgres): run a query
4. Valid event? (If): checks a condition and branches into true / false
5. Valid outcome? (If): checks a condition and branches into true / false
6. Prepare watchdog alert (Code): runs custom JavaScript code
7. Load deployment (Postgres): run a query
8. Reject invalid event (Respond to Webhook): sends the response back to the webhook caller
9. Load feedback deployment (Postgres): run a query
10. Reject invalid outcome (Respond to Webhook): sends the response back to the webhook caller

…plus 82 more steps. See the full node list below.

Services it uses

PostgresRedisSlack

HTTP calls to: api.openai.com

Before you upgrade to n8n 3.0

Nodes used (9)

• Webhookn8n-nodes-base.webhook
• Coden8n-nodes-base.code
• Ifn8n-nodes-base.if
• Respond to Webhookn8n-nodes-base.respondToWebhook
• Postgresn8n-nodes-base.postgres
• HTTP Requestn8n-nodes-base.httpRequest
• Redisn8n-nodes-base.redis
• Slackn8n-nodes-base.slack
• Schedule Triggern8n-nodes-base.scheduleTrigger

From the author

Quick overview This workflow ingests Zendesk escalation events via a secured webhook, uses OpenAI plus Qdrant knowledge to draft an evidence-backed action plan, and routes it to Slack for human approval before writing a guarded private note back to Zendesk,…

View the original on n8n.io → Check your own copy