The flow
Starts it 1Logic 4Service 5
The steps in the order they run, from what starts it.
- 1New PaymentStripe triggerStarts it
- 2Get Stripe CustomerStripeService
- 3Merge Stripe and QuickBooks DataMergeLogic
- 4Merge Payment and QuickBooks CustomerMergeLogic
- 5GET Quickbooks CustomerHttp RequestService
- 6Use Stripe CustomerMergeLogic
- 7POST Sales ReceiptHttp RequestService
- 8POST Sales Receipt To QuickBooksHttp RequestService
- 9If Customer ExistsIfLogic
- 10Create QuickBooks CustomerQuickbooksService
How it's built
- Starts on
- An event in a connected app
- Steps
- 10, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Stripe
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Stripe 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. 10 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 10 steps before you point it at anything that matters.