Overview

After triggering a workflow via the API or webhook, you can fetch the run result programmatically to check status, inspect outputs, and retrieve artifact URLs.

Endpoint

GET https://api.flowfn.com/v1/app/runs/:id

Headers

x-api-key: your-app-api-key
x-app-code: your-app-code

Response fields

The response includes:

status – One of queued, running, succeeded, failed, timed_out.
tasks – Array of task run results, each with status, outputs, and duration.
trigger – Trigger metadata and the inputs that started the run.
created_at / updated_at – Timestamps.

Polling for completion

If the workflow is still running, poll the endpoint at intervals (e.g. every 2–5 seconds) until the status is terminal (succeeded, failed, or timed_out).

Artifacts

Tasks that produce files (images, PDFs, videos) store them as artifacts. Request signed artifact URLs from the run to get time-limited download links. See Workflow Runs and Artifacts.

Example: trigger and fetch

# Trigger a workflow
curl -X POST https://api.flowfn.com/v1/app/workflow/api/my-workflow \
  -H "x-api-key: sk_abc123" \
  -H "x-app-code: my-app" \
  -H "Content-Type: application/json" \
  -d '{"email": "user@example.com"}'

# Response includes run_id — use it to fetch the result
curl https://api.flowfn.com/v1/app/runs/RUN_ID \
  -H "x-api-key: sk_abc123" \
  -H "x-app-code: my-app"

Fetching Workflow Runs via API