Bind a journey to your site
Step by step — create the default registration, login, verification, onboarding or checkout flow, edit it, bind it, test it, and unbind if needed.
Nothing changes on your site until a journey is bound. Until then the built-in pages run as always, so you can build and test the flow first.
1. Create the default
Open /flows. As the site's owner you see the Journeys panel. On the journey you want — say Onboarding — click Create default. The standard flow is created and bound in one go.
2. Edit it
Click the journey's flow to open the canvas. The default onboarding flow is short: source → send the new member where they were heading, or to the dashboard. Add a step after the source:
- System email to send a welcome message.
- Add subscriber to start them on a sequence.
- Capture page to ask a question first, then continue.
Save.
3. Test it
Register a new account on the site, verify with the emailed code, and watch what happens after the code is accepted — that is the onboarding journey. For registration or login, use the same page you always did; the bound flow renders it. Read /executions for the run.
4. Bind a different flow
Built a flow of your own? Bind on the Journeys panel attaches it in place of the default. Only one flow is bound per journey.
5. Unbind
Unbind returns the process to the built-in page. The flow is kept.
What must be true
- A registration or login journey must reach a page: the register or login form is a page widget placed on a layout. A flow that ends without rendering shows a fault on screen with a link back to the canvas.
- The verify journey is entered from the emailed link at the verify step, so keep that step in place.