Failed Payment Follow-up
A failed invoice stops being a silent number on a dashboard and becomes a tracked case your team can act on. When Stripe reports a payment failure, a ModuleX agent pulls the details, re-sends the invoice, and posts the case to Slack.
Stripe
Slack
6 steps2 integrationsRuns on payment failure
A dashboard does not chase money. What failed-payment follow-up looks like when it depends on somebody remembering.
- 01Stripe records the failure, but a number on a dashboard does not chase itself.
- 02Finance exports failed invoices and pings people by hand when someone remembers to look.
- 03Without a nudge the customer never notices, and a recoverable lapse becomes a cancellation.
- Catch failurecard_declined · Team annual
- Re-send invoicesent to the payer
- Open case#ar-review
One workflow, six steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01Watch for invoice.payment_failedStripe
- 02Pull the invoice, customer, and planStripe
- 03Draft the case summaryModuleX
- 04Re-send the invoice to the payerStripe
- 05Post the case to #ar-reviewSlack
- 06Reply in-thread when it is paidSlack
The workflow is an editable graph. Watching events and pulling details run freely; re-sending the invoice and the Slack post wait for your opt-in approval until you loosen them. The graph is the receipt.
Failed payments, chased. Paste this into ModuleX chat, or hit Use this workflow. It drafts the graph, connects your accounts, and schedules it.
When a Stripe invoice payment fails, look up the customer, amount, and plan, re-send the invoice, and post the case to #ar-review in Slack. When the invoice is paid, reply in the same thread to close it out.
to: composerOr skip the workflow entirely. Ask the assistant in chat and it runs the same job agentically: it picks the right actions, chains them, and reports back. The composer is for when you want it repeatable.
A Stripe invoice payment just failed. Pull the invoice, customer, and plan, re-send the invoice, and post the case to #ar-review in Slack.
- stripe · retrieve_invoice · + customer
- stripe · send_invoice · re-sent
- slack · post_message · #ar-review
Case opened. Team annual plan, card_declined at renewal; the invoice is back in the payer’s inbox with a payment link, and #ar-review has the case thread with the amount and the decline reason.
Where this fits. The tools it runs on, and the teams that run it.
Keep the momentum. Nearby workflows that reuse the accounts you just connected.
Daily Inbox DigestEvery morning your team gets a clean digest of overnight email in Notion, without opening the inbox. A ModuleX agent reads the unread threads, summarizes them, and files a dated page in your Notion database.
Inbound Lead RoutingNew leads get scored the moment they arrive and the hot ones land in #sales while your reps are still at their desks. A ModuleX agent rates buying intent, posts the strong leads to Slack, and files every contact in HubSpot.
Support Ticket TriageNew tickets get read, prioritized, and routed the moment they land, and the urgent ones surface in Slack instead of sitting in a queue. A ModuleX agent classifies each Freshdesk ticket, sets its priority and tags, assigns it, and posts the ones that cannot wait.
About this use case.
Stripe’s invoice.payment_failed event. The agent watches for it by reading recent activity with list_events, so a failed charge starts the flow on its own.