Journeys: registration, login, verification, onboarding, checkout
The site's own processes run as flows you can edit — what each journey does by default, and how to bind, unbind or recreate one.
A journey is a flow bound to one of the site's built-in processes. When a journey is bound, the process runs the flow; when nothing is bound, the built-in page runs as it always has. Nothing changes on a site until you bind something.
The journeys
- Register — the registration page and form → create the account → send to verification.
- Login — the sign-in page → sign in → send to the requested destination.
- Verify — the code page → verify the account → hand off to onboarding. Email links enter the flow at the verify step.
- Onboarding — where a freshly verified member goes: back where they were heading, or to the dashboard. Add steps here to welcome, ask questions, or start a sequence.
- Checkout — the checkout page for guests and members, and a background branch that runs when an order is placed (send a receipt, notify a channel, start a nurture).
The Journeys panel
On /flows, owners of the site see a Journeys panel listing each journey with what is bound to it:
- Create default — seeds the standard flow for that journey and binds it. Open it on the canvas and edit.
- Bind — bind an existing flow instead.
- Unbind — return the process to the built-in page.
Editing a journey
The pages a journey shows are ordinary page layouts with a form widget (register form, login form, verify form), so the look is edited like any page. The behaviour is the flow: add a step between register and verify to record where the visitor came from, or after verification to enrol them in a sequence.
A journey that reaches its end without showing a page is a fault, not a fallback — the flow tells you so on screen with a link to fix it.