Workflows
Execute Workflow
Execute a published workflow for a linked account.
POST
Execute a workflow for a linked account via a manual trigger. The workflow must be published and owned by the linked account. Execution is asynchronous by default; set the
Option 2 — Session token
sync_execution header to run synchronously and return the result inline.
The
slug header is required — it names the application the workflow belongs to. Without it the call fails with Workflow ID and slug are required.Authentication
This endpoint is scoped to a linked account (it runs that account’s private workflow), so it accepts either authentication method. Option 1 — API keyYour Refold API key.
The linked account that owns the workflow.
Session token. Format:
Bearer YOUR_SESSION_TOKENPath Parameters
The published workflow ID (from List Workflows). The workflow must be published before it can be executed.
Headers
The application slug the workflow belongs to.
Config to scope execution to. Defaults to the linked account ID.
Run synchronously and return the result inline.
Tag to label the resulting execution.
Return sanitized request headers in the response.
Body Parameters
The execution input, matching the workflow’s request structure.
Response
- 200 OK
- 400 Bad Request
Returns the execution result. For async runs this is an acknowledgement with the execution reference; for sync runs it includes the workflow output.