Automation library · Money admin

Recover failed Stripe payments with Claude and Gmail

Started by an event in a connected app, and works across Gmail. 13 steps, 2 branches: a working afternoon to understand properly.

Medium

13 stepsMedium: a working afternoon
2Branches: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 1Logic 9Service 3

The steps in the order they run, from what starts it.

  1. 1On Stripe payment failureStripe triggerStarts it
  2. 2Set config: brand, tone and final attemptSetLogic
  3. 3Read the failed invoiceCodeLogic
  4. 4Route by which attempt this isSwitchLogic
  5. 5Angle: assume a card expirySetLogic
  6. 6Angle: action is neededSetLogic
  7. 7Angle: access is at riskSetLogic
  8. 8Build the recovery emailCodeLogic
  9. 9Write the email with ClaudeHttp RequestService
  10. 10Attach the payment linkCodeLogic
  11. 11Email the customerGmailService
  12. 12Is this the last attemptIfLogic
  13. 13Alert you before it is written offGmailService

How it's built

Starts on
An event in a connected app
Steps
13, with 2 branches
Size
Medium: a working afternoon
Connects to
Gmail
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Gmail account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an event in a connected app.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 13 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 13 steps before you point it at anything that matters.