The flow
Starts it 1Logic 2Service 9
The steps in the order they run, from what starts it.
- 1Watch new Stripe eventsStripe triggerStarts it
- 2Route by event typeSwitchLogic
- 3Getting line itemsHttp RequestService
- 4Check if customer exists as contactKlicktippService
- 5Getting charge IDHttp RequestService
- 6Update contact in KlickTippKlicktippService
- 7Transfer customers to KlickTipp with SOIKlicktippService
- 8Getting invoice linkStripeService
- 9Subscribe buyer to KlickTipp with DOIKlicktippService
- 10Route by SKU and total amountSwitchLogic
- 11Tag contact for high-value orderKlicktippService
- 12Tag contact for clothing purchaseKlicktippService
How it's built
- Starts on
- An event in a connected app
- Steps
- 12, with 2 branches
- 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. 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.