Triggers

A trigger determines when a workflow runs. Every run is created by exactly one trigger, and the trigger metadata is recorded on the run for auditability.

Trigger types

Type	How it starts a run
Manual	A user clicks Run in the editor, or invokes orvanta flow run / orvanta script run.
Schedule	A cron expression fires the workflow on a recurring basis. See Schedules.
Webhook	An inbound HTTP request to the workflow’s unique webhook URL.
API	A programmatic call to the REST API.

Webhook triggers

Each workflow has a unique webhook URL. Posting to it creates a run and passes the request body into the run context as input:

curl -X POST https://api.orvanta.cloud/api/v1/workflows/my-workflow/runs \
  -H "Authorization: Bearer $ORVANTA_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"order_id": "ord_123"}'

The JSON body is available to the first node via the run context (e.g. {{ trigger.order_id }}).

Manual triggers

orvanta flow run f/demo/welcome --data '{"env": "production"}'

Run a single script directly with orvanta script run <path> --data '{...}'.

Choosing inputs

Whatever the trigger, inputs are validated against the workflow’s declared input schema before the run starts. Invalid input is rejected with a clear error rather than producing a partial run.

Related

• Schedules — Cron-based recurring triggers.
• Workflows — How triggers fit into a workflow.
• Jobs and runs — What a trigger creates.