Connect Stytch to start branded emails when a Consumer user signs up or a member joins a B2B organization. Brew supports 7 Stytch event types across the Consumer and B2B products.
Stytch remains responsible for authentication. Brew only listens for events and creates and sends the emails that follow them.
Stytch labels each event with a source. Brew processes events from the direct source, which come from your API and SDK calls. Dashboard and SCIM events are recorded as unsupported and never start automations, so a change an operator makes in the Stytch Dashboard does not email customers.
direct.organization.create carries no recipient. Brew records it as unresolved and starts no automation. To email a person, use direct.member.create, which carries the member address.
Delete events carry only an ID. Brew looks up the email it saw earlier for that user or member on the current connection. If it has none, the event is recorded as unresolved.
direct.user.create, direct.user.update, and direct.user.delete come from Consumer projects. The organization and member events come from B2B projects.
Brew supports these 7 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 and stytch_project.
Consumer events set stytch_user_id. Member events set stytch_member_id, stytch_organization_id, and stytch_org_role. Delete events set stytch_account_status to deleted. 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. Member events add role, and direct.organization.create adds organizationName and organizationSlug. createdAt is a Unix timestamp in seconds.
Stytch user, member, and organization IDs are not merge tags. They land on the contact as stytch_* fields instead.
A Stytch account does not establish consent for marketing email. Record consent at sign-up and check it before promotional sends.
No. Stytch's own authentication messages are unchanged. Brew starts automations from the webhook events listed here, after Stytch has created, updated, or deleted the user or member.
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. Send Example deliveries, dashboard and SCIM events, and events without a known recipient never start automations.
