Send Suspended Email
Node Card
Category: Communication Nodes
Type:
send-suspended-emailTypical position: After email collection in a password reset or passwordless flow; or on the
4008 error edge of Auth to notify blocked users.Properties
Outputs & Errors
| Property | Type | Required | Description |
|---|---|---|---|
| Email Template Type | select | Yes | The category of email to send. Options: Email Verification, Welcome Email, PasswordLess Login, Forgot Password, Delete User, Add Email, 2FA, Reset Password, Forgot Pin. |
| Email Template Name | select | Yes | The specific template to use, filtered by the selected template type. Populated from configured email templates. |
| Email Provider | select | Yes | The email delivery provider to use. Populated from configured providers. |
| Error Handling | custommultiselect | No | Override default messages for specific error codes. Each selected error code becomes a named output edge on the canvas. |
| Output / Code | Condition | Default message |
|---|---|---|
true | Email sent successfully | Varies by template type |
false | Email send failed (catch-all for unhandled errors) | NA |
4007 | Identity not found in the directory | User does not exist |
4008 | Account is blocked by admin or policy | Your account is blocked |
4021 | Email domain is not permitted to register | Email is not allowed to register |
4037 | Email address is already associated with an account | Email address is already registered |
4039 | Token generation rate limit exceeded | You have reached a limit for generating token |
tip
Error edges only appear on the canvas when you explicitly select them in the Error Handling property. Unselected error codes fall through to the false output.
Common Next Nodes
Send Suspended Email (true)→Web Pagepassword reset / passwordless: collect token or new password
Send Suspended Email (true)→Failure Finalblocked-user notification: end flow with account-status message