Email Login

Enables users to log in using their email address and password. Skips the login form entirely when the user already has an active session.

Authentication

How to import

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

Node Topology

How the Flow Works

1. Entry: every request first hits Has Session.
2. Already logged in: Has Session True routes directly to Success Final, bypassing the login form entirely.
3. No session: Has Session False renders the Web Page (Email + Password inputs).
4. Form submitted: the Web Page Output feeds into Auth, which verifies the email/password pair.
5. Auth True: credentials valid; user is redirected to Success Final.
6. Auth False: invalid credentials; the flow loops back to the Web Page so the error is surfaced inline on the same form.
7. Failure Final is present on the canvas but has no incoming connections in the default template: wire it if you need a hard terminal failure path (e.g. from accountlocked).

---

Nodes Used & Why

Node	Role	Key config
Has Session	Skips login if the user already has an active session	No config needed
Web Page	Renders the login form container	Set Web Page Header to your app's login title
Email (child)	Collects the user's email address	Disable Email Only as Input to allow other identifiers
Password (child)	Captures the login password	Default type is login: no change needed
Auth	Verifies credentials and issues access token	Enable Auth Validation for statuses you want to handle explicitly
Success Final	Terminates on successful login	Set Redirect URL to your post-login destination
Failure Final	Not wired by default	Connect it when you need a terminal failure path

---

Key Design Decisions

HAS SESSION MUST BE THE FIRST NODE

Without Has Session, a user who is already logged in will land on the login form every time: even with an active session. Has Session True routes them directly to Success, skipping the form entirely.

Start → Web Page → Auth

Start → Has Session → (True: Success  |  False: Web Page → Auth)

WIRE AUTH NAMED ERROR EDGES FOR RECOVERY PATHS

Named edges are dormant until you enable Auth Validation in the Auth node's property panel. Any unconnected edge falls through to false (loops to form). Wire the edges where you need a dedicated recovery path: leaving them all as false means locked-out and unverified users see a generic "wrong credentials" message.

accountlocked→ Route to Unlock Account node or a locked-account info page

passwordexpired→ Route to an Update Password screen

emailunverified→ Route to Send Email (verification template)

phoneunverified→ Route to Send SMS (verification template)

LEAVING FAILURE FINAL UNCONNECTED IN PRODUCTION

The template ships with Failure Final unconnected: this is intentional for the default template but must be wired before going to production. Any path that reaches an unconnected Failure Final ends silently with no redirect.

Auth (accountlocked) → unconnected  (user sees a blank page)

Auth (accountlocked) → Failure Final (Redirect URL: /locked)  or dedicated unlock flow