> ## Documentation Index
> Fetch the complete documentation index at: https://docs.raydocs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Create a Workflow Run

> Launch a manual trigger with input data and optional run metadata.

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.

```json theme={null}
{
  "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](/api-reference/workflows/trigger-workflow-webhook). 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.