Skip to content
Orvanta Docs

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

Section titled “Trigger types”
TypeHow it starts a run
ManualA user clicks Run in the editor, or invokes orvanta flow run / orvanta script run.
ScheduleA cron expression fires the workflow on a recurring basis. See Schedules.
WebhookAn inbound HTTP request to the workflow’s unique webhook URL.
APIA programmatic call to the REST API.

Webhook triggers

Section titled “Webhook triggers”

Each workflow (script or flow) gets an autogenerated webhook URL. Posting to it creates a run and passes the request body in as arguments, matched by key to the workflow’s input parameters:

Terminal window
curl -X POST https://app.orvanta.cloud/api/w/demo/jobs/run_wait_result/p/u/bot/process_order \
  -H "Authorization: Bearer $ORVANTA_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"order_id": "ord_123"}'

See Webhooks for the full set of synchronous, asynchronous, and SSE stream endpoint variants, including the equivalent path for flows.

Manual triggers

Section titled “Manual triggers”
Terminal window
orvanta flow run f/demo/welcome --data '{"env": "production"}'

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

Choosing inputs

Section titled “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.

Section titled “Related”