CUSTOMER SUPPORT
Self-serve refund request auto-decision from a web form
Receives refund requests from your customer portal via webhook, checks Stripe charge age, usage, and refund history.
How it runs
The automated pipeline, trigger to output.
- TriggerRefund request received via HTTP webhookHTTP webhook
- ActionLook up charge details in StripeStripe
- ActionQuery usage and refund history in PostgresPostgres
- LogicAuto-approve if low-risk, else route to review
- ActionIssue refund in Stripe for approved casesStripe
- OutputPost borderline cases to Slack review channelSlack
What it does
Handles inbound refund requests submitted from your product or help center. It validates the request against policy, and when a case is unambiguous and low-risk it issues the Stripe refund automatically. Anything outside the auto-approve window is packaged with full context and dropped into a Slack review channel so an agent can decide quickly.
When to use it
Use it when you offer self-serve refunds and want to clear the easy 80% instantly while still giving humans the borderline cases — without letting anyone game the policy.
How it works
- 1The portal posts a refund request to an HTTP webhook with the charge ID and customer email.
- 2Stripe is queried for the charge amount, age, and whether it was already refunded.
- 3Postgres returns the customer's usage and count of prior refunds.
- 4A logic gate auto-approves when the amount is under the limit, the charge is recent, usage is low, and there are no prior refunds.
- 5Approved cases trigger a Stripe refund; everything else posts a context card to a Slack review channel.
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.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Customer Support workflows
Flag Live Intercom Chats With No Help Article and Alert Slack
When an Intercom conversation closes, checks whether the customer's question is already covered by a help article.
Negative VIP CSAT to Owner Callback Scheduler
When a VIP submits a low Intercom CSAT rating, drafts a recovery note with an LLM and books a callback on the account owner's Google Calendar within their working hours.
CEO Agent: Mine Last Month's Tickets and Publish a Deflection Plan
Monthly, an agent investigates the top recurring Zendesk ticket themes, drafts and publishes the highest-confidence help articles to ReadMe.
Mine a Discord Support Channel for Recurring Questions to Document
On a daily schedule, scans a Discord support channel for questions the community keeps asking, deduplicates against existing ReadMe docs.
Daily VIP Sentiment Digest for Account Owners
Each morning, pulls the prior day's Intercom conversations for VIP accounts, summarizes the overall mood per account with an LLM.
VIP Reply Sentiment Watcher with Account-Owner Escalation
Scores every inbound Intercom reply from a VIP customer for frustration and, when it crosses the anger threshold, pings the account owner in Slack with the conversation link…
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.