Send your own AuthKit emails: Invitations, Magic Auth, verification and password reset

Sending custom AuthKit emails requires disabling WorkOS’s default invitation, Magic Auth, email verification, and password reset messages at the environment level, then implementing handlers that receive an event, retrieve the complete object through its corresponding API endpoint, and send an email containing the withheld secret such as a link, token, or code. This approach supports objects created through the Dashboard and hosted AuthKit interfaces, while backend-created objects can usually be emailed directly from the API response. Invitation handling must cover both creation and resend events, while custom links may require configured redirects and token handling in an application’s own authentication pages. Email verification requires particular attention because it is always enabled and invited users who sign up with passwords may need verification when WorkOS no longer sends the invitation email. Teams should test these flows in staging, account for Directory Provisioning behavior, localize emails themselves where needed, and consider Custom Email Providers instead if they only need a branded sender domain rather than full control over message content and delivery logic.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.