CUSTOMER SUPPORT
Refund Fraud Guard Against Internal Postgres Ledger
Cross-references each refund request against a Postgres ledger of prior refunds and Stripe charge data to flag serial refunders and duplicate claims before an agent issues money.
How it runs
The automated pipeline, trigger to output.
- TriggerRefund request webhook receivedHTTP webhook
- ActionFetch charge and refund state from StripeStripe
- ActionQuery refund ledger for history and duplicatesPostgres
- LogicApply serial-refunder and duplicate thresholds
- OutputWrite verdict and log request to ledgerPostgres
What it does
This agent protects against refund abuse. For each request it pulls the Stripe charge and queries your internal Postgres ledger for the customer's lifetime refund count, total refunded amount, and any open duplicate claim on the same order. If the customer trips an abuse threshold or the order was already refunded, it blocks with reasoning; otherwise it clears the request and records it in the ledger.
When to use it
Use it when a small set of customers drive a large share of refunds, or when duplicate refund claims slip through across channels. It gives agents an abuse signal grounded in your own history, not just Stripe's single-charge view.
How it works
- 1A refund request webhook starts the flow.
- 2The agent fetches the charge and refund state from Stripe.
- 3It queries the Postgres refund ledger for the customer's history and duplicate claims.
- 4Abuse logic compares counts and totals against your thresholds.
- 5The verdict is written back and the request is logged to the Postgres ledger.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect StripeCustomers, subscriptions, payments.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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
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.
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.
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.
Article Volume-Rebound Early Warning (Datadog)
Streams support ticket-tag events into Datadog, watches for topics whose volume is reaccelerating against a decaying article.
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.