Handle failed payment renewals with AI analysis, Jira tickets and Slack alerts
Needs changesWhat this workflow does
This workflow has 10 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects Slack and Jira Software.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Validate Payload (Function): runs custom JavaScript (legacy Function node)
- Payload Valid? (If): checks a condition and branches into true / false
- AI Analysis (OpenAI): uses OpenAI
- Slack: uses Slack
- Priority Switch (Switch): routes items into 1 branches
- Set High Priority (Edit Fields (Set)): sets or maps fields
- Set Standard Priority (Edit Fields (Set)): sets or maps fields
- Create Jira Finance Ticket (Jira Software): uses Jira Software
- Slack: uses Slack
Services it uses
Before you upgrade to n8n 3.0
2 things in this workflow are removed in n8n 3.0. Fix them before you upgrade:
- OpenAI (legacy) in AI Analysis: replace with OpenAI node (AI section).
- Function (legacy) in Validate Payload: replace with Code node, mode 'Run Once for All Items'.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| OpenAI (legacy) AI Analysis | OpenAI node (AI section) |
| Function (legacy) Validate Payload | Code node, mode 'Run Once for All Items' |
Nodes used (8)
- OpenAI
n8n-nodes-base.openAi - Switch
n8n-nodes-base.switch - Edit Fields (Set)
n8n-nodes-base.set - Webhook
n8n-nodes-base.webhook - Function
n8n-nodes-base.function - If
n8n-nodes-base.if - Slack
n8n-nodes-base.slack - Jira Software
n8n-nodes-base.jira
From the author
Webhook from Payment Provider → Jira Finance Ticket → Slack Invoice Follow-up Automation This workflow automates failed subscription renewal processing by validating webhook data, using AI to analyze urgency and churn risk, creating a Jira Finance Task and…