Turn a Stripe dispute into a Jira issue with the evidence deadline
Turns a Stripe dispute into a Jira ticket carrying the evidence deadline as the due date, a priority derived from hours remaining and amount, and a list of evidence to gather — then announces it in Sl.
The Stripe trigger subscribes to charge.dispute.created and verifies signatures itself. A Set node converts the amount from minor units and turns Stripe's Unix evidence deadline into both an ISO timestamp and hours remaining, which is the figure that makes urgency legible. A Switch derives priority from time first and amount second — under 72 hours is Highest regardless of size, a large amount is High, everything else is Medium via the fallback — and the three branches converge on a single Jira node. The ticket sets Jira's native due date from the evidence deadline so the dispute appears in the same overdue views as the rest of the team's work, and the description lists exactly what evidence to attach. Slack is notified after the ticket exists so the message quotes a real key. Failures route to an error rail on Discord that tells someone to check Stripe directly.
Key benefits
- ✓The evidence deadline lands in Jira's own due date, so a dispute cannot quietly age past it
- ✓Priority reflects hours remaining first, which is what actually decides whether you can respond in time
- ✓The ticket already lists the evidence to gather, so nobody starts by asking what to attach
- ✓Slack quotes the real issue key, posted after the ticket exists
- ✓Stripe access is read-only — the workflow never submits or concedes anything on your behalf
Use cases
- →Merchants who have lost disputes purely by missing the response window
- →Finance teams tracking chargebacks in Jira alongside other work
- →Ops teams that need dispute deadlines visible in existing overdue reports
- →Anyone whose Stripe dispute emails get lost among Stripe's other notifications
Integrations
Workflow preview (10 nodes)
The template's actual node layout and connections. Node parameters and credential slots unlock with the download.
What's inside (10 nodes)
A look at the node types this workflow uses. No purchase required — full parameters and credentials are yours after you buy.
From download to running in 3 steps
- 1Import. In n8n, open Workflows → menu → “Import from File” and pick the downloaded JSON.
- 2Connect. Add your own credentials on the app nodes - n8n highlights exactly which ones need them.
- 3Activate. Run it once to test, then toggle Active. The automation is live.
What you'll learn
Production levelProduction-grade: idempotency, dead-letter handling, and reconciliation included.
- •Moving data between Jira, Slack and Discord in a single run
- •Adding retries and an explicit error path to external calls
- •Testing against pinned sample data before connecting anything real
Every node carries its own documentation on the canvas, plus notes explaining why the architecture was built this way, a credential setup guide, troubleshooting, and three practice exercises. Sample data comes pinned to the trigger, so you can hit Execute and watch data flow before connecting a single account.
Common questions
What exactly do I get?
The complete, ready-to-import n8n workflow as a JSON file, delivered instantly after payment. Import it into your own n8n (cloud or self-hosted), add your credentials, and it runs.
How do I import it into n8n?
In n8n, open Workflows, click the three-dot menu, choose “Import from File”, and select the downloaded JSON. Then connect your own app credentials on the highlighted nodes.
Do I need anything else for it to work?
You need your own n8n instance and accounts/credentials for the apps this workflow connects to (Stripe, Jira, Slack, Discord). No coding is required.
What if it doesn't work for me?
If the file is faulty, won't import, or isn't as described, contact us within 7 days and we'll fix it or refund you - see our refund policy.
Can I modify or resell it?
You can freely adapt and use it in your own or your clients' projects. Reselling or redistributing the template file itself is not permitted.
Related templates
Recover failed Stripe payments with a dunning sequence
Classifies Stripe payment failures by decline code and responds differently to each: a soft retry note, a card-update request, or escalation to a human for hard declines. Every attempt is logged so recovery can be measured.
Approve documents: Slack for approvals
Approvals on n8n: runs when a form is submitted across Slack, Google Sheets, Notion and Discord, starting at "Stamp & Shape Invoice". 21 documented nodes.
Create quotes for approvals
Approvals on n8n: runs when a webhook arrives across Google Sheets, Google Drive, Slack and Discord, starting at "Download from Google Drive". Parses the incoming file into rows. 21 documented nodes.
Alert the team on new events: Google Sheets & Notion
Approvals on n8n: runs when a webhook arrives across Google Sheets, Notion, Slack and Discord, starting at "Compute HMAC Signature". 29 documented nodes.