Connect WorkOS to start branded emails when a user is created, verifies their email, resets a password, joins an organization, or is provisioned through directory sync. Brew turns 18 WorkOS event types into automation triggers.
WorkOS remains responsible for SSO, directory sync, sign-in, and password resets. Brew only listens for events and creates and sends the emails that follow them.
organization.created, organization.updated, organization.deleted, and connection.activated carry no recipient. Brew records them in Recent events as unresolved and starts no automation.
To email a person about a new organization, use an event that carries their address, such as organization_membership.created or invitation.accepted.
Membership, authentication, and directory events without an email address can still proceed when Brew has already seen a real email for the same WorkOS user, membership, or directory user on the current connection.
Brew supports these 18 event types:
Each verified event with a real email address creates or updates a Brew contact, matched by email, whether or not an automation uses the event. When the data is present, Brew sets first and last name, workos_user_id, and workos_email_verified.
Authentication events set workos_last_verification_at, workos_last_failed_auth_at, workos_last_password_reset_at, or workos_last_magic_auth_at. Membership and invitation events set workos_organization_id and workos_org_role. Directory events set workos_directory_user_id and workos_directory_id.
user.deleted and dsync.user.deleted set workos_account_status to deleted, and organization_membership.deleted sets it to removed_from_org. Brew does not remove the contact.
Use the selected event's declared payload schema for merge tags. Every event includes email, firstName, lastName, and createdAt when present. User events add emailVerified, organization events add organizationName, and membership and invitation events add role. createdAt is a Unix timestamp in seconds.
WorkOS object IDs are not merge tags, and neither are the IP address and user agent on authentication events.
Directory-synced employees have usually not opted in to marketing. Treat them as recipients of account and transactional notices unless they opted in separately.
Receiving an event and sending an email are separate steps. Confirm a matching automation is Live, then check its filters, execution history, recipient eligibility, and sending domain. Organization and connection events never start automations, and a recognized WorkOS test sample is recorded as a test event.
