← All use cases

Operations

Hourly

Failed payments handled every hour.

A workflow watches Stripe for failed charges and starts recovery. A second one reconciles what you billed against what your own database recorded after the books close.

5,000 free credits to start.

How it works

Three steps to a workflow

  1. Step 01

    Connect Stripe and your database

    A restricted Stripe key covers reporting workflows. Add write scopes only where a workflow must act. Your database gives the agent the other side of the reconciliation.

  2. Step 02

    Describe the rules

    Say when to email a customer, when to escalate to an owner, and what a mismatch means. The agent applies judgment where a rules engine needs a hundred branches.

  3. Step 03

    Run it hourly and monthly

    Recovery runs every hour and looks at the last hour of charges. Reconciliation runs after the books close. Both post where your revenue team reads.

The run

What one run looks like

Each line is a tool call. The agent finds the API it needs, reads the result, and acts. The full transcript stays on the run.

Hourly

Every hour, find failed charges from the last hour, start recovery, and escalate enterprise accounts.

  1. stripe·list failed charges in the last hour
  2. attio·look up the account owner and contact
  3. stripe·create hosted payment update links
  4. resend·send recovery emails
  5. slack·notify owners in #revenue

3 failed payments handled

  • $2,340 at risk across 3 accounts
  • Emails sent from [email protected]
  • 1 enterprise account escalated to @priya
  • Note added to each Attio record

Integrations

The tools this workflow uses

Connect each one once. The agent gets its full API, and the credential stays at the network layer.

FAQ

Questions, answered

Put a workflow on billing operations.

Write the prompt, pick the trigger, and read the first run.