AI agents with WorkOS webhooks

Receive WorkOS webhooks on Trigger.dev and use them to start, resume or message your AI agents.

Get started now

What you can do with WorkOS webhooks

Start an agent

WorkOS events can start a new agent run. For example, an agent that sets up every user WorkOS directory sync adds.

Resume an agent

An agent can pause until the WorkOS event it needs arrives, for up to 90 days, and costs nothing while it waits.

Message an agent

WorkOS events can land in a running agent's conversation, so it acts on them with full context.

Events you can receive from WorkOS

Some of the events WorkOS sends. Your agent can filter on any of them.

View all events
dsync.user.created

Directory user created

dsync.group.created

Directory group created

connection.activated

SSO connection activated

user.created

User created

user.deleted

User deleted

Example

An agent that sets up every user WorkOS directory sync adds

import { webhook, webhooks } from "@trigger.dev/sdk";


export const workos = webhooks.endpoint.define({
  id: "workos",
  source: webhooks.workos(),
});


export const workosEvents = webhook({
  id: "workos-events",
  endpoint: workos,
  filter: "event.event == 'dsync.user.created'",
  onEvent: async ({ event }) => {
    // Start, resume or message your agent with the event
    console.log(event);
  },
});

Handled for you

Docs

Verified for you

webhooks.workos() checks the WorkOS-Signature header on every request. Bad requests are rejected before anything runs.

Retries don't run twice

Retries are matched on event.id, so a retried webhook doesn't start a second run.

Filter before anything runs

Only the WorkOS events you care about start a run. Filtered webhooks use no compute.

See every delivery

Every webhook is recorded with its payload, headers and the agents it reached, so you can debug it and replay it.

Get started

  1. 1

    Set up the agent

    Copy the starter prompt into your coding agent, like Claude Code, Cursor or Codex. It creates a Trigger.dev project and adds the webhook endpoint. Prefer to write it yourself? Start from the example above.

  2. 2

    Add the webhook in WorkOS

    Deploy your project, or run trigger dev, and the endpoint appears on the Webhooks page of the Trigger.dev dashboard with its URL. Add that URL in WorkOS's webhook settings and pick the events you need. The endpoint's Copy setup prompt button gives your coding agent the exact steps.

  3. 3

    Add WorkOS's signing secret

    Copy the signing secret from WorkOS. Then on the endpoint's page in the Trigger.dev dashboard, choose Set signing secret and paste it in, so Trigger.dev can check every request really came from WorkOS.

  4. 4

    Try it

    Send a test event from WorkOS, or use the endpoint's Test tab. It appears on the endpoint's Deliveries tab, with the agents it reached.

Related integrations

All 48 integrations

Clerk

Auth & identity

Linear

Productivity

Slack

Communication

Attio

Productivity

Autumn

Payments & billing

Brex

Payments & billing

Cal.com

Productivity

Calendly

Productivity

Ready to build with WorkOS webhooks?

Declare an endpoint, deploy, and paste the URL into your provider.

Get started for free