Route IT service catalog requests in Slack with Postgres workflows
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 50 nodes and runs manually, when you click “Execute workflow” (plus 2 other triggers). Along the way it connects Postgres. It also calls slack.com over HTTP.
How it runs
Trigger: Manually, when you click “Execute workflow” (plus 2 other triggers).
- Postgres: run a query
- Set Catalog Config (Edit Fields (Set)): sets 4 fields: signingSecret, verifySignatures, itQueueChannelId…
- Code: runs custom JavaScript code
- Switch: routes items into 2 branches
- Respond - Acknowledge Slash Command (Respond to Webhook): sends the response back to the webhook caller
- Code: runs custom JavaScript code
- Respond - Reject Unverified (Respond to Webhook): sends the response back to the webhook caller
- Postgres: run a query
- Switch: routes items into 2 branches
- Code: runs custom JavaScript code
…plus 37 more steps. See the full node list below.
Services it uses
HTTP calls to: slack.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (9)
- Manual Trigger
n8n-nodes-base.manualTrigger - Postgres
n8n-nodes-base.postgres - Webhook
n8n-nodes-base.webhook - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - Switch
n8n-nodes-base.switch - Respond to Webhook
n8n-nodes-base.respondToWebhook - HTTP Request
n8n-nodes-base.httpRequest - If
n8n-nodes-base.if
From the author
Quick overview This workflow turns Slack into an internal IT service catalog by storing services in Postgres, collecting requests through Slack modals, routing approvals via Slack DMs, and either calling an external automation HTTP endpoint or posting the…