Trigger DAG execution via webhook
Triggers a DAG execution via webhook. The DAG must have a webhook configured and enabled. Authentication depends on the webhook auth mode: bearer token only, bearer token plus HMAC, or HMAC only.
The request body is passed to the DAG as the WEBHOOK_PAYLOAD environment variable. If the DAG configures webhook.forward_headers, selected request headers are passed as the WEBHOOK_HEADERS environment variable. For safety, the Authorization header is never forwarded. The DAG run is enqueued and the endpoint returns immediately with the dag-run ID.
Path parameters
Name of the DAG file
the name of the DAG file
Query parameters
name of the remote node
Headers
Bearer token for webhook authentication (e.g., 'Bearer dagu_wh_...'). Required only when the webhook auth mode includes token authentication.
HMAC webhook signature in the format sha256=<hex>. Required only when the webhook auth mode includes HMAC authentication with strict enforcement. Sign the raw request body when X-Dagu-Profile is absent. When it is present, sign x-dagu-profile:<profile>\n<raw-request-body>.
Runtime profile name.
Runtime profile selected for this DAG run. The profile must be allowed by the webhook profile-selection policy. Omit the header to use the DAG's default profile resolution.
Request body
Example request
{
"dagRunId": "latest"
}Response
DAG run triggered successfully
Example response
{
"dagRunId": "latest"
}