Skip to main content
Only relevant if you’re on Supabase and have turned on Dreamlit-managed Supabase Auth emails. If you skipped it during onboarding, head to Settings → Database Connections, open your Supabase connection, and click Setup Supabase Auth.
Turning this on does not implement auth flows in your app. Your app must still call Supabase Auth APIs (sign-up, magic link, reset password, etc.). Dreamlit only handles the email delivery for those API-driven events.
The Supabase Auth Trigger runs when Supabase sends an auth event to Dreamlit via the Auth Hook configured during setup. It applies only if you use Supabase and have explicitly opted in for Dreamlit-managed Supabase Auth emails (this is not enabled by default). It is auto-installed with your Supabase connection and cannot be swapped or removed in the workflow builder.
Supabase Auth Trigger example

Example: Magic Link auth emails routed through Dreamlit.

​
Breakdown

Auth workflows fire from Supabase Auth API calls (e.g., sign up, magic link, password reset), not database changes.

Know when it fires

Supabase emits an auth event when your app calls its Auth APIs, such as: supabase.auth.signUp, signInWithOtp, resetPasswordForEmail, reauthenticate, updateUser({ email }), and admin.inviteUserByEmail. The Auth Hook forwards that event to Dreamlit, which kicks off this workflow.

Review available outputs

Each run exposes auth-specific fields you can use downstream: ConfirmationURL, Token, TokenHash, SiteURL, Email, Data, RedirectTo, and UserId.

Configuration is fixed

This trigger is created during Supabase setup. You cannot change its type, delete it, or replace it from the builder—adjust downstream steps (queries, emails, Slack) instead. If you skipped auth setup during onboarding, go to Settings → Database Connections, open your Supabase connection, and click Setup Supabase Auth to install the hook.

​
Explore further

Supabase setup

Learn how the Auth Hook is installed and how the six auth email types map to workflows.

Send Email step

Customize the auth email content that follows this trigger.