Workflow trigger delivery
Generic workflow trigger. Any HTTP client POSTs an arbitrary JSON body to the trigger’s URL; the whole body becomes the run’s trigger context. Path: POST /api/workflows/triggers/{token}.
Authorizations
Section titled “Authorizations”Request Bodyrequired
Section titled “Request Bodyrequired”The generic webhook / trigger delivery body: an arbitrary JSON object the
caller posts. SupaCloud does not impose a fixed shape — the whole object is
handed to the workflow run as the trigger context (SC_TRIGGER_CONTEXT).
This is an honest record-of-unknown, NOT a fake structure: the runtime never
deserializes it into named fields.
object
Arbitrary trigger payload fields, forwarded verbatim to the run as
SC_TRIGGER_CONTEXT. Flattened so the component IS the open object the
caller posts (not a wrapper); the runtime never deserializes named fields.
Examplegenerated
{ "additionalProperty": "example"}Responses
Section titled “Responses”Delivery accepted (fired or skipped).
The standard webhook ack body returned by SupaCloud’s own trigger receivers:
{ "status": "fired" | "skipped" | "gone", "run_id": "<uuid>"?, "reason": "<text>"? }.
A receiver acks (200) even on a filtered-out delivery so the sender does not
disable the hook; run_id is present only when a run was started.
object
Why a delivery was skipped or is gone — present for skipped / gone.
The started workflow run id — present only when status = "fired".
fired (a run started), skipped (authenticated but filtered out) or
gone (a migrated email trigger past its grace window).
Examplegenerated
{ "reason": "example", "run_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "status": "example"}Malformed body (non-JSON / rejected content-type).
The canonical JSON body of every error response — the single source of truth
the frontend binds to. Every AppError serializes as this exact shape, and
the generated OpenAPI component ApiErrorBody (with its ErrorCode enum) is
what the frontend error schema is generated from, so there is no hand-written
error schema on either end.
object
Machine-readable, stable error code.
Present only on a quota-exceeded 403 — the inline upgrade-CTA payload.
object
The entitlement feature key that was hit, e.g. apps.max_count.
The plan’s limit for this key.
Where to send the user to upgrade.
Current usage (count or bytes, per the key).
Human-readable message (the server’s English text; the client may localize
by code).
Example
{ "code": "not_found"}Invalid or missing HMAC signature.
The canonical JSON body of every error response — the single source of truth
the frontend binds to. Every AppError serializes as this exact shape, and
the generated OpenAPI component ApiErrorBody (with its ErrorCode enum) is
what the frontend error schema is generated from, so there is no hand-written
error schema on either end.
object
Machine-readable, stable error code.
Present only on a quota-exceeded 403 — the inline upgrade-CTA payload.
object
The entitlement feature key that was hit, e.g. apps.max_count.
The plan’s limit for this key.
Where to send the user to upgrade.
Current usage (count or bytes, per the key).
Human-readable message (the server’s English text; the client may localize
by code).
Example
{ "code": "not_found"}Forbidden (issue-debate fail-closed gate / disabled automation switch).
The canonical JSON body of every error response — the single source of truth
the frontend binds to. Every AppError serializes as this exact shape, and
the generated OpenAPI component ApiErrorBody (with its ErrorCode enum) is
what the frontend error schema is generated from, so there is no hand-written
error schema on either end.
object
Machine-readable, stable error code.
Present only on a quota-exceeded 403 — the inline upgrade-CTA payload.
object
The entitlement feature key that was hit, e.g. apps.max_count.
The plan’s limit for this key.
Where to send the user to upgrade.
Current usage (count or bytes, per the key).
Human-readable message (the server’s English text; the client may localize
by code).
Example
{ "code": "not_found"}Unknown trigger token.
The canonical JSON body of every error response — the single source of truth
the frontend binds to. Every AppError serializes as this exact shape, and
the generated OpenAPI component ApiErrorBody (with its ErrorCode enum) is
what the frontend error schema is generated from, so there is no hand-written
error schema on either end.
object
Machine-readable, stable error code.
Present only on a quota-exceeded 403 — the inline upgrade-CTA payload.
object
The entitlement feature key that was hit, e.g. apps.max_count.
The plan’s limit for this key.
Where to send the user to upgrade.
Current usage (count or bytes, per the key).
Human-readable message (the server’s English text; the client may localize
by code).
Example
{ "code": "not_found"}Email trigger migrated past its grace window (email receiver only).
The standard webhook ack body returned by SupaCloud’s own trigger receivers:
{ "status": "fired" | "skipped" | "gone", "run_id": "<uuid>"?, "reason": "<text>"? }.
A receiver acks (200) even on a filtered-out delivery so the sender does not
disable the hook; run_id is present only when a run was started.
object
Why a delivery was skipped or is gone — present for skipped / gone.
The started workflow run id — present only when status = "fired".
fired (a run started), skipped (authenticated but filtered out) or
gone (a migrated email trigger past its grace window).
Examplegenerated
{ "reason": "example", "run_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "status": "example"}