Registration

Captures email and password, checks whether the account already exists, and creates the user profile if it does not. If the user already exists the form is shown again with an inline error.

Registration

How to import

In the Admin Console go to Workflows → New Workflow → From Template, select Registration, and click Import.

Node Topology

How the Flow Works

1. Entry: The flow begins at the Web Page (Registration form with Email + Password).
2. Form submitted: the Web Page Output feeds into User Exists, which checks whether the email is already registered.
3. User Exists True: account already registered; the flow loops back to the Web Page so the error is surfaced inline on the same form.
4. User Exists False: no existing account; the flow proceeds to Create User.
5. Create User True: profile created successfully; user is redirected to Success Final.
6. Create User False: creation failed (e.g. blocked email, policy violation); user is sent to Failure Final.

---

Nodes Used & Why

Node	Role	Key config
Web Page	Renders the registration form	Set Web Page Header and Submit Button Text
Email (child)	Collects the email address	Enable Validate MX Record to block disposable addresses
Password (child)	Captures the new password	Enable Confirm Password for registration flows
User Exists	Prevents duplicate account creation	True loops back to the form: error shown inline
Create User	Persists the new identity profile	Wire error 4021 (blocked email) if you need a dedicated error page
Success Final	Terminates on successful registration	Set Redirect URL to your post-registration destination
Failure Final	Terminates on a creation error	Set Redirect URL to a generic error page

---

Key Design Decisions

USER EXISTS TRUE MUST LOOP BACK TO THE WEB PAGE

Looping back keeps the user on the same form so the duplicate-email error is surfaced inline: the user can correct their email without losing any other input. Routing True to Failure Final instead gives no recovery path.

User Exists (true) → Failure Final  (dead end, no recovery)

User Exists (true) → Web Page  (inline "already registered" error)

SKIPPING USER EXISTS AND GOING DIRECTLY TO CREATE USER

Without User Exists, an existing email will hit Create User, receive a duplicate-account error, and surface as an unhandled failure rather than a clean inline message. Always check existence before attempting creation.

Web Page Output → Create User

Web Page Output → User Exists → (true: loop to form  |  false: Create User)

WIRE CREATE USER NAMED ERROR EDGES FOR POLICY VIOLATIONS

Unhandled errors on Create User fall through to false → Failure Final. For errors where the user can take action, route to a dedicated page instead.

4021Email on block list→ Route to a dedicated blocked-email error page

4110Required field missing→ Return to Web Page with a validation message