On before sign up

You can use this event to check or block sign ups based on your requirements. For example, you could enforce strong passwords or only allow emails from a certain domain to sign up.

Interface actions that fire the On before sign up event

• Sign up with email↗

Example potential use cases

• Enforce password policy (length, complexity, breach list check)
• Allow‑/Deny‑list email domains (e.g., company emails only)
• Require a valid invite code or pre‑registration approval
• Block disposable/temporary email providers

Event data

Display Key	Example Value	Description
payload	{ email, password, name, image, callbackURL }	Raw sign‑up request body sent from the interface action.

Example payload

{
  "payload": {
    "email": "user@example.com",
    "password": "StrongP@ssw0rd!",
    "name": "Jane Doe",
    "image": "https://example.com/avatar.jpg",
    "callbackURL": "https://app.example.com/onboarding"
  }
}

How to cancel the sign up

If the information provided doesn't meet your custom requirements, add a Throw error action and write an error message in its Message. This will stop the sign up.

Example error message:

Password must be at least 12 characters and include a symbol.

SEND RESPONSE DOES NOT WORK HERE

Send Response is only available in API Endpoints and Middleware. Whatever result an Event Trigger returns is ignored: only an error stops the sign up.

SHOW A FRIENDLY MESSAGE IN YOUR INTERFACE

In the editor, the Sign up with email action fails with the message you wrote in Throw error. In your published app, this message is hidden for security reasons: the action fails with a generic Internal Server Error instead.

If you want your users to see why their sign up was refused, check the same rule in your interface too, before the Sign up with email action. For example, add a True/False split that shows an error message when the password is too short. On before sign up still blocks the sign up if someone gets around your interface.