Manually start a workflow run
Kick off a run without waiting for an inbound message (useful for testing). Target an existing conversation by conversationId, or — WhatsApp only — a phone number via to (a conversation is found or created). text seeds the run's lastMessage variable. The graph must be runnable.
API key authentication - use your Zernio API key as a Bearer token
In: header
Path Parameters
Recipient phone (WhatsApp only)
An existing conversation to run in (required for non-WhatsApp workflows)
Simulated inbound text, seeded as the run's lastMessage variable
Response Body
application/json
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.workflows.triggerWorkflow({ path: { workflowId: 'workflow_abc123', }, body: { to: 'string', conversationId: 'conversation_abc123', text: 'Hello, world!', },});console.log(data);{
"success": true,
"execution": {
"id": "string",
"status": "string",
"currentNodeId": "string",
"waitingFor": {},
"variables": {},
"conversationId": "string"
}
}{
"error": "Unauthorized"
}{
"error": "Not found"
}List workflow runs GET
Returns recent executions (runs) with their status, current node, and accumulated variables.
Get an execution's timeline GET
Returns the per-step run-log for a single workflow execution: trigger fired, each node visited, edge handles taken, errors, and durations. Backed by Tinybird (90-day retention). Used by the Runs UI drawer to render the timeline.