The flow
Starts it 1Logic 5Service 6
The steps in the order they run, from what starts it.
- 1Payment SucceededStripe triggerStarts it
- 2Set Invoice DefaultsSetLogic
- 3Has Billable Amount?IfLogic
- 4Fetch Stripe CustomerStripeService
- 5Skip Zero-Amount PaymentNo OpLogic
- 6Build Invoice PayloadCodeLogic
- 7PDFops Generate InvoicePdfopsService
- 8Alert Billing ChannelSlackService
- 9Archive to S3Aws S3Service
- 10Has Customer Email?IfLogic
- 11Log to Invoice LedgerGoogle SheetsService
- 12Email Invoice to CustomerGmailService
How it's built
- Starts on
- An event in a connected app
- Steps
- 12, with 2 branches
- Size
- Medium: a working afternoon
- Connects to
- Gmail, Google Sheets, S3, Slack, Stripe
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Gmail, Google Sheets, S3, Slack and Stripe accounts. 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. 12 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.
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 12 steps before you point it at anything that matters.