Webhook

ActionFlows supports two complementary webhook products:

1. Incoming flow webhooks: external systems POST to a flow-specific URL to start a run.
2. Organization event webhooks: ActionFlows POSTs signed events (for example flow run lifecycle) to your HTTPS endpoints.

Receiving webhooks (flow trigger)

Open a flow → Webhooks. Create an endpoint, copy the URL, and POST to it from any HTTP client. Recent deliveries appear in the Incoming requests card.

See the Webhook trigger page for URL shape, idempotency, and security.

Organization event webhooks (outgoing)

In Organization → Webhooks, register one or more destination URLs and subscribe to events:

• flow.run.started
• flow.run.succeeded
• flow.run.failed

ActionFlows delivers a JSON body shaped like:

{
  "id": "evt_...",
  "type": "flow.run.succeeded",
  "created": "2026-07-30T12:00:00.000Z",
  "data": {
    "actionFlowId": "...",
    "organizationId": "...",
    "runHistoryId": "...",
    "status": "completed"
  }
}

Each delivery includes:

• X-ActionFlows-Event
• X-ActionFlows-Event-Id
• X-ActionFlows-Signature: t=<unix>,v1=<hmac-sha256>

Verify v1 as HMAC-SHA256 of `${t}.${rawBody}` using the signing secret shown once at create/regenerate time.

Delivery attempts and HTTP status codes are visible on the webhook detail page.

Sending webhooks from inside a flow

From inside a flow, the HTTP Request node can call any webhook URL: your own services, customer systems, or third-party tools.

Common patterns

• Form → ActionFlows → CRM: A landing page form posts to your flow, which validates the data and creates a contact.
• Stripe → ActionFlows → Slack: A payment event triggers a flow that summarises the order and posts to your team channel.
• ActionFlows → Your service: Subscribe an org webhook to flow.run.succeeded / flow.run.failed for indexing and alerting.

Idempotency

Send an X-Idempotency-Key header on inbound flow webhook calls. ActionFlows deduplicates inbound deliveries when that key is present.