Create a Workflow Run

This endpoint launches a trigger.manual node. Token calls require workflows-write, workspaces-read, and a workspace administrator as the token owner. Use the webhook endpoint with workflows-execute for ERP webhook integrations.

{
  "trigger_node_id": "manual",
  "input_data": {"document_url": "https://example.com/invoice.pdf"},
  "metadata": {"client_id": "CLI-0042", "external_request_id": "REQ-789"}
}

Metadata follows the same string-object limits as webhook metadata. In multipart requests, send metadata as a JSON string field. The metadata rules configured on a webhook do not apply to a manual trigger. The server records the authenticated caller; supplied actor or origin fields do not change attribution. Token calls record origin api; authenticated browser calls record ui. The response is the lightweight run summary. Exact inputs remain available through the existing separate input endpoint. The existing idempotency_key field does not constitute a completed deduplication contract for external calls. Metadata request references identify requests but do not prevent duplicate runs.

Overview

Cookbook

Workspaces

Workspace Users

Extraction Templates

Extraction Sessions

Batch Operations

Documents

Workflows

Results

Create a Workflow Run