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
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"
}Restore a previous workflow version POST
Replace the current graph with the named version's snapshot. Before the swap, the current graph is itself snapshotted as a new version, so a restore is reversible. The workflow must be in `draft` or `paused` status (same gate as a normal graph edit). The returned workflow carries `restoredFromVersion` so the UI can surface which version was rolled back to.
List automation logs GET
Paginated list of every comment that triggered this automation, with send status and commenter info.