Upload File and Run Workflow
POST/api/automation/workflows/:workflow/upload-and-run
Upload a file to a published workflow that has a File Upload trigger as its entry node, and run the workflow against it. The request is a multipart/form-data upload with a single file field.
settings:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
The run is queued asynchronously and the response returns 202 with an idempotencyKey that identifies the resulting execution - filter List Workflow Executions by filter[search] on that key to track it.
Returns 422 when the workflow is not published, has no File Upload trigger, or the file fails the trigger's format validation.
Path param: workflow = workflow id.
Request
Responses
- 202
- 401
- 403
- 404
- 422
- 429
Accepted
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Entity
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.