Stripe Refunds to Xero Sync + Slack Dispute Alerts (n8n)

Auto-sync Stripe refunds to Xero—with Slack alerts for duplicates, disputes, and failures

If you handle SaaS billing, this n8n workflow automatically listens for Stripe refund and dispute events, then syncs successful refunds into Xero as manual journals. You’ll also get Slack alerts for duplicate refunds, dispute creation, and any refund-sync errors.

What this workflow does

• Triggers on Stripe refund webhooks (the charge.refunded event) and extracts refund details from the payload.
• Processes only succeeded refunds: it stops unless the refund status is succeeded, then fetches the related Stripe charge and its invoice.
• Maps the invoice country to the correct Xero setup using an n8n Data Table, including the Xero tenant ID and clearing/revenue account codes.
• Prevents duplicates by retrieving recent Xero manual journals and checking whether the journal narration already contains the Stripe refund ID.
• Posts to Xero when not duplicated: creates a POSTED Xero manual journal that debits the revenue account and credits the clearing account for the refund amount.
• Alerts on duplicates by sending a Slack message and skipping the Xero post.
• Triggers on Stripe disputes (charge.dispute.created) and posts a Slack alert including amount, customer, reason, evidence deadline, and a Stripe dashboard link.
• Reports failures to Slack: if any step in the refund sync path fails, a Slack error workflow trigger posts the failing step and error details.

Use cases

• Keep Xero refund accounting up to date automatically when Stripe refunds occur.
• Reduce manual reconciliation by ensuring refunds post only once via narration-based duplicate detection.
• Stay on top of Stripe disputes with timely Slack alerts containing evidence deadlines.
• Get immediate visibility into sync issues for faster operational troubleshooting.

Technical details

• Integrations/credentials: Stripe (API key), Xero (OAuth2 connection to your organisation), Slack (access to your target channel).
• n8n components: if, code, http request, slack, data table, and support nodes like sticky note.