Detect failed Stripe payments and follow up with an AI agent
A failed payment found a week late is often a lost customer. Every morning, an Orkeste agent lists the payments that failed in Stripe, notes the reason, logs each case in Airtable, posts the list to your finance channel and drafts a short email asking the customer to update their payment method.
The problem
Stripe retries quietly and nobody looks until revenue is down at month end. By then the customer has moved on or forgotten.
How the workflow runs
Runs: Every day at the hour you set.
List failed payments: The agent lists recent payments and charges in Stripe and keeps the failed ones, with the reason Stripe recorded.
Log each case: It creates a record in your Airtable follow-up table: customer, amount, reason.
Alert finance: It posts the list to the finance channel in Slack.
Draft the email: It writes a short email adapted to the reason, such as an expired card.
Approve: The email waits in Validations for finance.
Send or draft: The approved email is sent from Outlook, or saved as a Gmail draft.
Customer emails wait for finance's approval. The agent never retries, refunds or cancels anything in Stripe.
Who does what
Payment watcher: Finds failed payments and prepares the follow-up.
Finance (human): Approves every customer email.
What this workflow does not do
Read only in Stripe: no retry, refund, pause or cancellation.
Reads recent payments in small batches; run it daily so none are missed.