Skip to main content
Triggers are points in the Auth0 process where Actions can be added for required customization. Multiple Actions can be placed in a trigger, executing in sequence. Excluding the Custom Token Exchange, triggers can be synchronous (blocking) or asynchronous (non-blocking). Every Auth0 Action receives two objects when its trigger fires:
  • The event object is read-only transaction context: details about the user, request, client, tenant, and connection at the moment the trigger fired.
  • The API object exposes the methods your Action can call to change the outcome of the transaction, such as denying access, adding token claims, triggering challenges, or caching data.
The objects differ per trigger and may differ based on your connection (such as connection).
  • Signup and Login: When a user is added to a database or passwordless connection (Signup), or as part of a user’s authentication transaction (Login).
  • MFA Notifications: When using SMS as a factor for (MFA) or to configure a custom provider.
  • Password Reset: When a password reset request is initiated.
  • Machine to Machine: When an application, instead of a user, is authenticated and authorized to use your APIs.
  • Custom Token Exchange: When a Custom Token Exchange Request is received to log a user in.