CUSTOMER SUPPORT
Refund Approval Router with Stripe Risk Check to Slack
Routes incoming refund requests through a Stripe risk and amount check, then sends low-risk refunds to a fast-approve Slack channel and high-value or flagged ones…
How it runs
The automated pipeline, trigger to output.
- TriggerRefund request webhook receivedHTTP webhook
- ActionFetch charge and dispute history from StripeStripe
- LogicClassify routine vs escalated by amount and risk
- ActionPost routine refunds to fast-approve channelSlack
- OutputPost escalated refunds to manager channelSlack
What it does
This workflow triages refund requests by money and risk. It pulls the underlying Stripe charge, scores it on amount, refund history, and dispute/fraud signals, then posts to one of two Slack channels: routine refunds go to a self-serve approve queue, while large or risky ones go to a manager channel with the full charge breakdown attached. No refund gets approved blind, and small ones don't wait on a manager.
When to use it
Use it when all refunds currently funnel through one overloaded approver, or when high-dollar refunds need a second set of eyes but small ones shouldn't. It splits the queue by genuine risk.
How it works
- 1An inbound refund request hits the webhook trigger from your support tool or form.
- 2The agent retrieves the referenced charge and its dispute history from Stripe.
- 3Risk logic classifies the request as routine or escalated based on amount and signals.
- 4Routine refunds post to the fast-approve Slack channel with amount and charge ID.
- 5Escalated refunds post to the manager Slack channel with full reasoning.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect StripeCustomers, subscriptions, payments.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Customer Support workflows
Send a tailored Loom onboarding sequence on Front first-reply
When a new customer's first email lands in Front, this picks the Loom onboarding walkthroughs matching their plan and use case, builds a friendly sequenced reply.
Suggest the right Loom video by classifying Intercom message intent
Reads each new inbound Intercom conversation, classifies what the customer is trying to do, and surfaces the best-matching Loom walkthrough to the agent as an internal note.
Draft personalized fix-live replies for support to review
When a Sentry issue resolves, an agent reads each linked ticket's full thread and drafts a tailored 'your fix is live' reply per requester.
Close the loop with requesters when a Linear bug moves to Done
When a Linear issue created from a support escalation moves to Done after deploy, look up the originating Zendesk tickets and notify each requester that their reported bug is…
Reopen and notify Front conversations when their bug fix deploys
When a deploy resolves a Sentry issue, find the snoozed or closed Front conversations linked to it, reopen them, and send the customer a reply that the fix is now live.
Tell Intercom users their reported bug shipped after a Vercel deploy
On a successful Vercel production deployment, match the release's resolved Sentry issues to Intercom conversations and message each affected user that their reported issue is…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.