Refund watcher
By Toolspoke
Checks Stripe over the weekend and flags refunds and new disputes above your threshold in Slack.
Needs a Toolspoke account. You choose which project it installs into.
Stripe
Slack
Its last step
Post one message
- Stripe + Slack
- Required integrations
- Runs on a schedule
- Saturdays and Sundays at 6pm by default
- Post one message
- What its last step does
- Nothing destructive
- 0 of 25 actions in its tools
On this page
The short version
- What it is
- Checks Stripe over the weekend and flags refunds and new disputes above your threshold in Slack.
- Works with
- Stripe, Slack
- How often
- Saturdays and Sundays at 6pm, once you switch it on.
- What it never does
- Issue, cancel or change a refund.
- What you need
- A Toolspoke account, with Stripe and Slack connected.
How it works
What each run does, from the "Each run" part of its own instructions.
- Step 1:
Fix the window the last 24 hours.
- Step 2:
Read the events with list_events for refunds created and disputes created in the window. For each, get the charge it belongs to, so you have the original amount, the date it was paid, and the customer.
- Step 3:
Keep what matters
Every refund at or above the threshold. Every new dispute, at any amount. A dispute has a deadline, and the post must say it. Two or more refunds to the same customer in the window, whatever the amounts. A day where the total refunded is more than three times...
- Step 4:
Post one message to the channel chosen at install. Disputes first, with amount, customer and the date evidence is due. Then refunds, with amount, customer, and the refund reason Stripe recorded. End with the day's total refunded.
What you get
How the agent's own instructions describe what it hands back. Install it to see a real result.
Post one message to the channel chosen at install. Disputes first, with amount, customer and the date evidence is due. Then refunds, with amount, customer, and the refund reason Stripe recorded. End with the day's total refunded.
If nothing crossed the threshold, post nothing.
Integrations & requirements
Refund watcher needs Stripe and Slack to work. You sign in to each one yourself.
Stripe
RequiredInspect customers, payments, subscriptions, and invoices.
Authentication: Secret key
Slack
RequiredSearch conversations and send messages to your workspace.
Authentication: Bot token
Skills it follows
| Tool | Actions it offers |
|---|---|
| Stripe | 14 in all: 13 read, 1 write, 0 destructive. Nothing that deletes or permanently changes anything. |
| Slack | 11 in all: 7 read, 4 write, 0 destructive. Nothing that deletes or permanently changes anything. |
A project can switch any action off, and every call is logged. The counts are what each tool offers; which of them the agent uses is up to its instructions.
What it will never do
- Issue, cancel or change a refund.
- Change customer or payment metadata.
- Post card numbers, full email addresses or billing addresses to Slack.
If something goes wrong
If Stripe cannot be read, post that to Slack once. A silent weekend looks the same as a quiet weekend, and someone should know which one it was.
These are written into Refund watcher's instructions. They guide the agent, but they are not a permission. What it is allowed to touch is set by the access you grant.
When it runs
Refund watcher runs saturdays and Sundays at 6pm by default. Its routine arrives switched off. Turn it on when you are ready: every run costs your workspace money.
If nothing crossed the threshold, post nothing.
Install it into a project, or copy it to the builder and change its instructions, tools and skills.
Use Refund watcher
Pick a project and connect the tools it needs.