CUSTOMER SUPPORT
Refund Fraud: Pre-Approval Gate via Refund Webhook
Receives a refund-approval webhook from your support tool, runs a synchronous Postgres linked-account and lifetime-refund check.
How it runs
The automated pipeline, trigger to output.
- TriggerRefund-approval webhook receivedHTTP webhook
- ActionQuery Postgres for links, limits, active holdsPostgres
- LogicApply policy: deny on hold/over-limit, else allow
- ActionWrite decision and reason to audit logPostgres
- OutputReturn allow/deny response; Slack on denySlack
What it does
Acts as a real-time decision endpoint your support or commerce app calls the instant an agent clicks Approve Refund. It synchronously evaluates the requester against linked accounts and lifetime refund limits and returns allow or deny, so risky refunds are stopped at the button rather than reversed after the fact.
When to use it
Use this when you can wire a webhook into your refund flow and want the fraud check to happen inline, not asynchronously. Ideal for high-value refunds where issuing first and clawing back later is costly.
How it works
- 1An HTTP webhook fires from your support tool carrying the order and customer identifiers.
- 2Postgres is queried for linked accounts, lifetime refund total, and any active fraud holds.
- 3A logic step applies the policy: deny on active hold or over-limit, allow otherwise.
- 4The decision and reason are written to the Postgres audit log.
- 5The flow returns a structured allow/deny response to the caller; denials also post to Slack for visibility.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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.