Skip to main content
Connect Stytch to Brew so user and team events fire automations. Welcome a Consumer user who signs up, or a teammate added to a B2B organization. Send an offboarding email when a teammate is removed.
  • Trigger automations from Stytch events. Kick off email flows from Consumer (B2C) or B2B auth events.
  • Auto-sync contacts into your audience. Every Stytch event upserts the user / member into Brew with stytch-prefixed custom fields you can filter and segment on.
  • Connect a Consumer or B2B project. Consumer projects send user events, and B2B projects send member and organization events.
  • Cover lifecycle and team workflows in one place. Onboarding, invites, role changes, offboarding.
Stytch webhooks are available on Consumer and B2B projects. If the Webhooks page is missing in your Dashboard, check your plan on Stytch’s pricing page.
Every marketing recipient must have opted in to hear from you. Importing or syncing contact data into Brew is not permission to email it. See What You Can Send.

How It Works

Stytch works like every other event source. Brew gives you a webhook URL and verifies each delivery. Each verified event starts the matching Live automations and upserts the user or member into your audience with stytch-prefixed fields. Connected-Source Events has the full model. Two things are Stytch-specific. Brew checks each signature with the Standard Webhooks (Svix) spec. And it processes direct.* events only, dropping dashboard.* and scim.* events so an operator’s click in Stytch can’t email customers.

Setup

1

Generate your Brew webhook URL

In Brew, open Integrations, click the Stytch card, open the Setup tab, and click Generate webhook URL. Copy the URL Brew generates.
2

Pick your Stytch project type

Choose Consumer (B2C) or B2B in the Brew connect form to match your Stytch project. A Consumer project sends direct.user.* events, and a B2B project sends direct.member.* and direct.organization.create.
3

Add an endpoint in Stytch

Open stytch.com/dashboard, go to Webhooks → + Add Endpoint, and paste the Brew URL into the Endpoint URL field.
4

Subscribe to the events Brew supports

For Consumer projects: enable direct.user.create, direct.user.update, and direct.user.delete.For B2B projects: enable direct.organization.create, direct.member.create, direct.member.update, and direct.member.delete.Click Create.
5

Reveal the Signing Secret

On the endpoint settings page Stytch shows next, reveal the Signing Secret. The value starts with whsec_.
6

Paste the Signing Secret into Brew

Paste the whsec_… secret into the Brew connect form and click Connect. Brew verifies every webhook using the Standard Webhooks (Svix) spec.
7

Send an example event

In Stytch, open Webhooks, select your endpoint, and open Testing. Pick direct.member.create (B2B) or direct.user.create (Consumer) and click Send Example. Stytch signs it automatically.Check its delivery status in Stytch. Then confirm the Stytch integration page in Brew changes from Waiting for test event to Connected. The example also marks its event as received in the page’s Stytch events list.If the page doesn’t connect, click Disconnect on the Stytch integration page. Then repeat steps 1, 2 and 6 with the secret Stytch shows.If step 1 shows a different URL from your Stytch endpoint, update the endpoint. Then send the example again.An example only verifies the webhook: Brew adds no contact and starts no automation. Manage → Recent events shows it as Test event.
Brew only processes direct.* events (real API / SDK calls). Dashboard- and SCIM-source events are dropped so manual operator clicks don’t accidentally email your customers.

Supported Events

Once connected, every Stytch event below is provisioned automatically and available as a trigger in the automation builder. Brew has no per-event enable step: an event fires when the bound automation is Live. The Manage tab shows:
  • Webhook URL: the URL your Stytch endpoint points at
  • Stytch events: how many events Brew has received, and each event’s status
  • Recent events: up to 25 of the newest deliveries that passed the signature check
Once Brew has received an event, it reads Last event and how long ago. It reads No events yet if it hasn’t fired. No events in 90 days means none arrived in the last 90 days, which is how long Brew keeps each delivery. If an event reads No trigger, click Re-provision. A Stytch project sends only its own type’s events, so the other type’s events stay at No events yet. Brew supports the following 7 Stytch events: Consumer (B2C)
  • direct.user.create
  • direct.user.update
  • direct.user.delete
B2B
  • direct.organization.create (recorded only: it carries no recipient, so Brew starts no automation)
  • direct.member.create
  • direct.member.update
  • direct.member.delete
In chat, say “Welcome new B2B members”. Brew scaffolds the automation with direct.member.create selected.

Common Patterns

Kind follows What You Can Send. Send transactional email, a direct response to something the person did, from a transactional-purpose domain. Marketing email needs the contact’s opt-in, and being synced from Stytch isn’t consent. Both means the confirmation is transactional and the follow-up is marketing. No email means the automation only syncs the contact and sends nothing.

Personalization

These resolve as merge tags in the email body, subject line, and preview text. Use a fallback wherever an empty value would read badly, like {{ firstName | there }}. The trigger. prefix reads the same field, so {{ trigger.firstName }} and {{ firstName }} resolve alike; see Namespaces. Every Stytch event carries firstName, lastName, and createdAt. The rest are event-specific, and a tag the event doesn’t declare blocks publishing.

Troubleshooting

Open the canvas and confirm at least one automation bound to this event is set to Live (not Draft). The Brew integration’s Manage → Recent events panel confirms the webhook is arriving.If it isn’t there, the issue is upstream (signing secret, or an endpoint not subscribed to the event). A Test event row is a Stytch Send Example, which verifies the webhook and runs nothing.If a real event is there but no email went out, check the automation is published. Then check the contact isn’t unsubscribed or suppressed.From an agent, check_trigger lists what blocks the trigger, and list_trigger_events shows each event’s match state and its runs.
A Stytch project sends only its own type’s events. Consumer projects send direct.user.*, and B2B projects send direct.member.* and direct.organization.create.Check that your Brew endpoint is on the project you want and subscribed to its events in setup step 4. A brand has one Stytch connection with one signing secret, so it verifies events from one Stytch endpoint. To move it to another project, click Disconnect on the Stytch integration page and repeat setup for that project.
The signing secret in Brew doesn’t match the one in Stytch’s Dashboard. Usually it was rotated in one place but not the other.Reveal the current secret on the Stytch endpoint settings page. In Brew, click Disconnect on the Stytch integration page, then repeat setup steps 1, 2 and 6. If step 1 shows a different URL from your Stytch endpoint, update the endpoint.Then send an example (step 7). Reconnecting starts the Stytch events list over.
Working as intended. Brew only processes direct.* events. That way, manual actions in the Stytch Dashboard and SCIM provisioning changes don’t email your customers.
Send Example only verifies the webhook. Brew starts no automation for an example.Build your automation as a Draft and run a test send from the email editor, then publish it to Live. Once it’s Live, trigger its event for yourself, for example by signing up a test user. Then watch the Manage → Recent events panel.

From an Agent or Code

Connecting Stytch and pasting the signing secret are app-only. From an agent or code, the rest is readable and buildable:
  • list_integrations or GET /v1/integrations confirms Stytch is connected to the brand.
  • check_trigger or GET /v1/automations/triggers/{triggerEventId}/readiness shows whether Brew has received an event and which Live automations consume it.
  • list_trigger_events lists recent deliveries, their match state, and the runs they started.
  • save_automation or POST /v1/automations builds an automation on any event above, and test_automation runs it to one address.
Stytch fires the events, so fire_trigger_event isn’t used here.

Requirements

  • A Stytch account with access to the Stytch Dashboard, so you can add a webhook endpoint and copy its signing secret

Need Help?

Our team is ready to support you at every step of your journey with Brew. Choose the option that works best for you:

Search Documentation

Type in the “Ask any question” search bar at the top left to instantly find relevant documentation pages.

Ask ChatGPT or Claude

Click here to open the Copy page menu at the top of this page, then send the page to ChatGPT, Claude, or your editor.