Sync Stripe refunds to Xero and send dispute alerts with Slack

## Stripe refunds and disputes to Xero and Slack ### How it works This workflow listens for Stripe refund and dispute events, enriches them with Stripe charge/invoice data, and routes them to the appropriate accounting or notification path. Successful refunds are mapped with tax configuration, checked against existing Xero manual journals to avoid duplicates, then either posted to Xero or reported in Slack as a duplicate. Stripe disputes generate a Slack alert, and a separate error trigger reports workflow failures to Slack. ### Setup steps - Configure Stripe trigger credentials and subscribe the refund trigger to the relevant refund succeeded event, and the dispute trigger to dispute created events. - Add Stripe API authentication for the HTTP Request nodes that retrieve charges and invoices. - Configure the Data Table used by Get Tax Config with the tax/account mapping expected by the Map Refund code node. - Set up Xero OAuth credentials and tenant details for the manual journal lookup and posting HTTP Request nodes. - Connect Slack credentials and set the target channels for duplicate refund alerts, dispute alerts, and failure alerts. - Review the code nodes to ensure field names, currency handling, journal narration, and Slack message formatting match your Stripe, Xero, and accounting conventions. ### Customization You can adjust the tax mapping table, Xero account codes, duplicate detection logic, and Slack channels/messages to match different regions, entities, or escalation rules.