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 certain email 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 Send response action and send an error message. This will stop the sign up.

Example error response body:

{ "error": "Password must be at least 12 characters and include a symbol." }