Node Card
Category: Input Nodes
Type:
emailTypical position: Inside a Web Page node, in registration or profile-update forms requiring an explicit email field.
Properties
Outputs & Errors
| Property | Type | Default | Description |
|---|---|---|---|
| Email Only as Input | checkbox | false | When enabled, only the email field is collected (no combined identity input). |
| Is Primary | checkbox | true | Whether this is the user's primary email. Shown when Email Only as Input is enabled. |
| Email Type | text | NA | Label for non-primary email addresses (e.g., Business). Required when Is Primary is false. Shown when Email Only as Input is enabled. |
| Validation String | text | NA | Optional regex rule to validate the email format beyond standard email validation. |
| Validate MX Record | checkbox | NA | When enabled, validates the domain's MX record to confirm it can receive email. |
| Output / Code | Condition | Default message |
|---|---|---|
| NA | NA | Child nodes have no independent outputs: the parent Web Page node fires its output edge on form submission. |
Common Next Nodes
Web Page containing Email (output)→Create Userregister user with collected email
Web Page containing Email (output)→Send Emailsend verification email after collection
Usage Notes
Use the Email node in registration flows when you need to collect an email address explicitly (rather than using the combined Identity node). Enable Validate MX Record in environments where deliverability of verification emails is critical. For secondary email collection (e.g., a business email), set Is Primary to false and specify an Email Type label.