Daily · 9:00
Chase overdue invoices
Polite reminders, drafted on the due date, sent after you approve.
StripeMCPStripe agentFailed payments, followed up.
Each morning it reads yesterday's failed payments and refunds in Stripe. It logs them in a sheet and drafts a polite email for each failed one.
Your first signup includes $50 in free credits.
Daily · 9:00
Watch your Stripe payments
- Reads
- Stripe payments
- Grows
- A log and email drafts
- Lands in
- Sheet and Gmail
Ask for it once, in plain words.
No flowchart to draw. Describe the job in chat. TulipFarm sets up the agent and its workflow, and shows you both before anything runs.
You
Every day at 9, read yesterday's failed payments and refunds in Stripe. Add them to a sheet and draft a polite email for each failed payment in Gmail.
TulipFarm
I made an agent called Payments watch and a daily 9:00 schedule. It reads Stripe through a Custom MCP connection, with read tools only. Writing to the sheet and creating drafts asks you first. Activate it?
ActivateEdit first
One morning, start to finish.
Every run is saved as an agent task you can open, check and rerun.
- Schedule
Every day at 9:00
Run startedStarted - Reads
Failed payments and refunds in Stripe
5 failed, 2 refunds - Writes
A log line and an email draft for each failed payment
7 lines, 5 drafts - Asks first
Add rows to the sheet and create drafts
Approved - Creates
Rows in Sheets, drafts in Gmail
Delivered 9:04Completed
What lands in your sheet.
One row per payment event, with the reason and what happens next.
Payment log| Event | Customer | Amount | Next step |
|---|---|---|---|
| Failed | The customer A | $40 | Draft email waiting |
| Failed | The customer B | $40 | Card expired, draft waiting |
| Refund | The customer C | $25 | No action |
| Failed | The customer D | $90 | Draft email waiting |
What gets planted.
Three parts you own and can change at any time.
- Agent
Payments watch
Reads payments and writes in a calm tone.
- Table
Payment log
One row for each failed payment or refund.
- Workflow
Daily 9:00
Runs each morning.
Uses
- StripeMCPStripe
- Gmail
- Google Sheets
Add if you use it
Slack- QuickBooksMCPQuickBooks
It reads quietly. It asks before it acts.
Reads without asking
- Failed payments in Stripe
- Refunds
- Past follow-ups in the log
Asks you first
- Adding rows to the sheet
- Creating Gmail drafts
- Sending any email
It uses your own connections, so it never sees more than you can.
Grow it your way.
Read only
Review and allow only Stripe's read tools. The agent can then never change a payment.
Skip repeats
Do not draft again if you wrote to the same customer this week.
Weekly total
Add a Friday run that totals failed payments and refunds.
Questions, answered.
How does the agent reach Stripe?
Through a Custom MCP connection. Stripe is not built in. You add its MCP server, choose how to sign in (none, OAuth or API key), and review each tool before an agent can use it.
Can it refund or charge a card?
Only if you allow a tool that can. Leave those tools off and it can only read. Anything that writes asks you first.
Is the amount always exact?
It copies amounts from Stripe. Check any line against your dashboard before you send.
- StripeMCP
Mondays · 9:00
Review QuickBooks each week
Reads unpaid invoices and bills and drafts the reminders.
QuickBooksMCPEvery hour
Handle refund requests
Checks the order and your policy, then drafts a reply for you to approve.
Catch the failed card, keep the customer.
Public beta, open to everyone. Your first signup includes $50 in free credits.