Webhook Trigger

What it does

Triggered by incoming HTTP requests, like the API Endpoint trigger, but with additional support for asynchronous execution.

Configuring it

• Allowed Methods — required. Which HTTP methods the webhook accepts. Defaults to POST.
• Endpoint — the path to match. Defaults to /; use * to match all paths.

Async execution

When enabled, the webhook returns an executionId immediately instead of waiting for the workflow to finish.

• Retry — on failure, retries up to maxAttempts (1–10, default 3), waiting retryDelay milliseconds between attempts (100–3,600,000ms, default 1000ms), scaled by retryDelayMultiplier for exponential backoff (1–10, default 1 = fixed delay).
• Throttling — caps incoming requests to maxRequests (default 2) per windowSeconds (1–3600, default 1).

Examples

A synchronous webhook

{ "allowedMethods": ["POST"], "endpoint": "/shopify/orders" }

Async, with retry and throttling

{
  "allowedMethods": ["POST"],
  "endpoint": "/shopify/orders",
  "async": {
    "enabled": true,
    "retry": { "maxAttempts": 5, "retryDelay": 1000, "retryDelayMultiplier": 2 },
    "throttling": { "enabled": true, "maxRequests": 10, "windowSeconds": 60 }
  }
}

See also

• API Endpoint Trigger — Creates a dedicated API endpoint for synchronous workflow execution.
• GraphQL Trigger — Creates a native GraphQL endpoint with schema configuration and automatic field filtering.
• Schedule Trigger — Triggered on a scheduled basis using cron expressions.
• File Event Trigger — Triggered when a file is created, updated, or deleted in the store's managed file storage.