Run a workflow from the API

Open Settings, create an API key, and copy it when it is shown. For most scripts, grant workflows:read and workflow_runs:create. Add webhooks:manage only if you are creating standing webhook subscriptions.

Use GET /api/v1/workflows to list the workflows your key can run, or copy the id from the workflow URL in The Loom. If your key has a workflow allowlist, only those workflows are visible.

POST to /api/v1/workflows/{workflow_id}/runs with input_text. If the workflow declares params, fetch GET /api/v1/workflows/{workflow_id} first and send a params object using the returned select, number, text, and boolean definitions.

Send an Idempotency-Key header, such as a UUID, so a network retry does not start the same workflow twice.

For a simple script, poll GET /api/v1/workflow-runs/{run_id} every few seconds until status is completed, failed, cancelled, or awaiting_input.

For Zapier, Make, n8n, or your own queue, pass webhook_url when creating the run, or create a standing webhook subscription. Webhook payloads are signed, and the API reference at /docs/api has copy-paste verification snippets.

If status is awaiting_input, the workflow is paused for a human-review step. Send the reviewer to the app link from the API response or webhook payload. The v1 API does not have an approve/resume endpoint yet.