Skip to content
BrainRoad BrainRoad
Documentation Menu

Setting Up Webhook Triggers

Find your helper's Wake Webhook and Task Endpoint in Settings, connect an outside tool, and test that events arrive.

On this page

Webhook triggers let outside tools nudge your helper when something happens: a payment in Stripe, a code change in GitHub, a Zap firing in Zapier. This page covers where to find the URLs, how to connect a tool, and how to test.

Before you start, two requirements:

  • Webhook triggers work with the OpenClaw helper only. Hermes trigger URLs are not exposed through the dashboard yet.
  • Your helper must be running. The URLs route to your helper’s private workspace, so a stopped helper cannot receive calls, and the dashboard only shows the URLs while the helper is running.

Where to find your URLs

  1. Open Settings in the dashboard.
  2. Find the Developer Triggers section. It describes itself as advanced webhook URLs for connecting outside tools.
  3. If your helper is stopped, you will see a note asking you to start it first.

You will see two URLs and an Auth token:

  • Wake Webhook: https://app.brainroad.com/gw/<your-id>/hooks/wake. Sends a short note that wakes your helper so it looks at something now. Example body:

    { "text": "New payment received from Stripe", "mode": "now" }

  • Task Endpoint: https://app.brainroad.com/gw/<your-id>/hooks/agent. Hands your helper a specific task. Example body:

    { "message": "Summarize today's new orders" }

Both require the Auth token sent as a bearer token, meaning an HTTP header like Authorization: Bearer <your-token>.

Connecting an outside tool

The pattern is the same in most services:

  1. Copy the Wake Webhook URL (or Task Endpoint, if the tool lets you build the request body) from Settings → Developer Triggers.
  2. Open the outside tool’s webhook or integration settings.
  3. Paste the URL as the webhook destination.
  4. If the tool supports custom headers, add the Authorization: Bearer <token> header with your Auth token.
  5. Choose which events should fire, and save.

Tools like Zapier and Make that let you shape the request are the easiest fit, because you can set the header and write a plain-language text or message your helper will understand.

Testing

Many services have a “send test event” button. Use it, then check that your helper reacted, for example by asking it in chat what just came in, or by checking the Work Ledger in the dashboard.

If nothing arrives:

  • Confirm the helper is running. A stopped helper does not receive webhook calls.
  • Confirm the URL was copied exactly, including your ID.
  • Confirm the Auth token header is present and current.

The Auth token

The token is what stops strangers from sending your helper instructions. Treat it like a password.

If it leaks, or you want to cut off a tool you connected earlier, press Regenerate on the Developer Triggers card. The old token stops working, and every tool you connected needs the new one before it can send events again.

One caution worth stating plainly: anything that can call these URLs can put text in front of your helper. Only connect tools you control, and keep the token private. Even so, webhook input cannot approve anything on its own. Customer-facing actions your helper proposes still arrive as drafts in your Inbox for you to review, outside any narrow auto-approvals you have explicitly turned on.