List workflow runs
Returns recent executions (runs) with their status, current node, and accumulated variables.
API key authentication - use your Zernio API key as a Bearer token
In: header
Path Parameters
Query Parameters
"running" | "waiting" | "completed" | "exited" | "failed"250Response 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.listWorkflowExecutions({ path: { workflowId: 'workflow_abc123', },});console.log(data);{
"success": true,
"executions": [
{
"id": "string",
"status": "running",
"currentNodeId": "string",
"waitingFor": {
"kind": "timer",
"nodeId": "string"
},
"variables": {},
"platformIdentifier": "string",
"conversationId": "string",
"stepCount": 0,
"lastError": "string",
"resumeAt": "2019-08-24T14:15:22Z",
"createdAt": "2019-08-24T14:15:22Z",
"updatedAt": "2019-08-24T14:15:22Z",
"completedAt": "2019-08-24T14:15:22Z"
}
],
"pagination": {
"total": 0,
"limit": 0,
"skip": 0,
"hasMore": true
}
}{
"error": "Unauthorized"
}{
"error": "Not found"
}Duplicate a workflow POST
Create an independent copy of a workflow's graph, name, description, and account binding. The copy is created in `draft` status with fresh execution counters and a new id — execution history is NOT copied. Useful for branching off a known-good workflow before making experimental edits.
Manually start a workflow run POST
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.