Triggers and runs

A trigger starts a workflow without anyone opening the console. Every time a workflow runs, by a trigger or by a test, VoisX records a run you can inspect.

Trigger types

Add triggers on the workflow's Triggers tab. A workflow can have several.

Trigger	Starts the workflow when
Webhook	Another system sends an HTTP POST to the trigger's unique URL.
Scheduled (cron)	A cron schedule you set comes due.

note

The trigger list also offers Email, Slack, Call started and Call ended. You can save these, but they don't start workflows yet. The console marks them "Saved, but this trigger type doesn't fire yet."

Each trigger has an Active switch. Turn it off to pause the trigger without deleting it. The list shows when each trigger last fired.

Webhook triggers

1. On the Triggers tab, choose Webhook and click Add trigger.
2. Copy the URL straight away. It is shown only once.
3. Configure the other system to POST JSON to that URL.

The secret in the URL is the only credential, so treat the URL like a password. If it leaks, or you lose it, click Rotate webhook URL. A new URL is issued and the old one stops working immediately.

For the request and response format, see Webhooks.

Scheduled (cron) triggers

1. On the Triggers tab, choose Scheduled (cron).
2. Enter a cron expression with 5 fields: minute, hour, day of month, month, day of week.
3. Click Add trigger.

Schedules run in UTC. Some examples:

Expression	Runs
0 9 * * *	Every day at 09:00 UTC
*/15 * * * *	Every 15 minutes
0 6 * * 1-5	Weekdays at 06:00 UTC
30 4 1 * *	04:30 UTC on the 1st of each month

If a scheduled run can't start, for example because the organization has no credit, that tick is skipped. The next tick runs as normal.

Runs

Open the workflow's Runs tab to see its history. Filter by status and by time range (last 24 hours, 7 days, 30 days or all time).

Each run shows its input, output, any error, a node-by-node trace and its billable usage. Click View in canvas to see the path the run took.

Status	Meaning
Running	The run is in progress.
Completed	The run reached the end.
Interrupted	The run paused at a step that waits for a person, such as Human Handoff.
Failed	A step raised an error that no Error Handler caught.
Timed out	The run hit your plan's maximum run time and was stopped.
Abandoned	The run stopped unexpectedly, or it stayed paused for a long time without an answer, so VoisX closed it.

The Workflows list shows each workflow's total runs, success rate and average run time.

Limits

Your plan sets the maximum run time of a workflow run and how many runs can be in progress at once. A run also needs available credit in your organization to start. See Usage and billing.