Skip to main content
Connect WorkOS to Brew, and its webhook events do two things:
  • Events. A new user can start a published automation, such as a welcome email.
  • Contacts. New users and profile changes add or update the person in your audience, with workos fields.
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 Connects

WorkOS sends the events selected on its webhook endpoint to Brew. A user.created event can start a published automation that uses WorkOS - User Created. A user.updated event can update an existing contact even when no automation uses the update trigger.

Requirements

  • A WorkOS environment and a Brew brand.
  • A WorkOS webhook endpoint that points to Brew and subscribes to the events you want Brew to receive.

Setup

To check an existing connection, open Webhooks in the WorkOS dashboard and select the endpoint that points to Brew. Check for a user.created subscription for signups, or a user.updated subscription for profile changes.

Events

Brew has 18 WorkOS triggers. All 18 declare email as a required string and createdAt as an optional integer. They also declare firstName and lastName as optional strings. Use these fields as merge tags. In the automation canvas, a WorkOS trigger node shows the event’s Payload and a Manage action.

Contacts

Brew can create a contact when an AuthKit user is created. The contact can include firstName and lastName. A user.updated event can change the first name on an existing contact, keeping its email and WorkOS user ID. A new WorkOS user contact can be subscribed, with no consent record. Confirm the person opted in before you send marketing email.

Check It Works

  1. Confirm WorkOS is connected. Review the published automations that use WorkOS - User Created.
  2. Use the WorkOS API to create a test AuthKit user in your connected Staging environment.
  3. Find the new user.created receipt in Brew. Check its matched automations and runs.
  4. Look up the test user’s email in Brew to check the contact.

Common Patterns

  • Welcome new users. Bind a welcome automation to WorkOS - User Created. To check delivery, look for Sent and Delivered in Analytics with WorkOS - User Created in the Source column.
  • Sync a name change. Edit a user’s first name in WorkOS. Find the WorkOS - User Updated receipt, then read the contact to check the new first name.

Limits

  • Organization events. Brew records organization.created, organization.updated, and organization.deleted, but they have no person to email. Their receipts read rejected with unresolved_recipient and zero runs. Readiness still reads received for them.
  • Receipts. A receipt shows its processing state and the runs it started, not the event’s values. Read the payload contract for declared fields and the contact for stored values.

Troubleshooting

In WorkOS Webhooks, check that the endpoint pointing to Brew subscribes to that event.
Brew may recognize a dsync.user.created sample from Send test event. Then Recent events shows Test event and Webhook verified · no contact or run.
Check which published automations use that trigger.

From an Agent or Code

Connecting WorkOS is app-only. After that, an agent connected over MCP can check deliveries and build automations. Ask in plain English:
“Has Brew received a user.created event from WorkOS, and did it start a run?”
“Build a welcome automation on WorkOS User Created and test it as a draft without sending email.”
From code:
  • GET /v1/integrations shows whether WorkOS is connected.
  • GET /v1/automations/triggers/{triggerEventId}/readiness returns delivery. delivery.status and delivery.lastReceivedAt show whether Brew saw an event and when.
  • GET /v1/automations/trigger-instances lists each receipt with its state, any rejection reason, and the runs it started.
  • GET /v1/automations/triggers/{triggerEventId}/contract returns the trigger’s declared fields.
A recognized dsync.user.created sample also sets delivery.status to received. Its receipt reads state: rejected with rejectionReason: test_event, so check the receipt to tell a sample from a real event.

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.