Trigger automation webhook
Queue a run of a custom automation that has a webhook trigger, instead of waiting for the trigger’s configured event. Useful for running automations from CI/CD pipelines, release scripts, or any other system that already emits events. Only custom automations with a webhook trigger can be triggered; other triggers return a 404 response.
Authenticate with an organization API key that has write access.
404 response. To trigger a scheduled custom automation on demand instead, use Trigger automation.
Use cases
- CI/CD pipelines: Run a custom automation on every merge to
mainor after a release, without waiting for a scheduled run. - Release events: Run a custom automation from a release script when you cut a tag or publish a new SDK version.
- Internal tooling: Trigger automations from internal dashboards, Slack commands, or scheduled jobs you already run.
Get the webhook URL and auth header
Open the Automations page in your dashboard and click the settings button on a custom automation with a webhook trigger. The trigger card shows the full webhook URL and a Copy auth header action for theAuthorization: Bearer <api-key> header template.
Replace <api-key> with an unexpired organization API key with write access. Create or manage keys on the API keys page. Automations do not create, store, or rotate keys on your behalf.
Example
Trigger a webhook automation from a GitHub Action whenever code merges tomain:
Rate limits
This endpoint shares a rate limit with Trigger update and Trigger automation: up to 10 requests per 10 seconds per organization. Each queued run consumes credits at the same rate as any other custom automation run. See Credit pricing.Authorizations
The Authorization header expects a Bearer token. Use an admin API key. This is a server-side secret key. Generate one on the API keys page in your dashboard.
Path Parameters
The ID of the automation to trigger. Copy it from the automation's settings panel on the Automations page in your dashboard.
Response
Automation run queued successfully.
The ID of the queued automation run. Appears in the run history on the Automations page.