Summarize Slack threads into Jira tickets with OpenRouter and Slack approval
Ready for 3.0What this workflow does
This AI workflow has 16 nodes and runs when an HTTP POST request hits its webhook URL (plus 1 other trigger). Along the way it connects Jira Software and OpenRouter Chat Model. It also calls slack.com over HTTP.
How it runs
Trigger: When an HTTP POST request hits its webhook URL (plus 1 other trigger).
- Respond to Webhook: sends the response back to the webhook caller
- Config (Edit Fields (Set)): sets 6 fields: MESSAGE_COUNT, JIRA_PROJECT_KEY, JIRA_ISSUE_TYPE…
- Respond to Interaction (Respond to Webhook): sends the response back to the webhook caller
- Parse Payload Code (Code): runs custom JavaScript code
- Get conversation history (HTTP Request): calls slack.com
- If: checks a condition and branches into true / false
- Format Thread Code (Code): runs custom JavaScript code
- Create an issue (Jira Software): uses Jira Software
- Update Slack - Cancelled (HTTP Request): calls an HTTP API (POST)
- Ticket Drafter Agent (AI Agent): runs an AI agent, with model: Open AI Ticket Drafter
…plus 3 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)
- Respond to Webhook
n8n-nodes-base.respondToWebhook - Edit Fields (Set)
n8n-nodes-base.set - Webhook
n8n-nodes-base.webhook - Code
n8n-nodes-base.code - HTTP Request
n8n-nodes-base.httpRequest - If
n8n-nodes-base.if - Jira Software
n8n-nodes-base.jira - AI Agent
@n8n/n8n-nodes-langchain.agent - OpenRouter Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenRouter
From the author
Quick Overview This workflow turns a Slack slash-command request into an AI-drafted Jira ticket preview, then creates the Jira issue only after a user approves it in Slack using interactive buttons. How it works 1. Receives a Slack slash command via a webhook…