Update workflow
Update name, description, the graph, or reassign to a different account. The graph can be modified in any status, including active: a run already in progress reloads the saved graph at its next step, and a run parked on a node the edit removed completes instead of failing. Every graph edit is re-validated and an invalid graph answers 400 regardless of status. status is not a field of this request; use the activate and pause endpoints. Account swaps re-validate the graph against the new platform (so e.g. moving from WhatsApp to Facebook surfaces a start_call node as an error instead of silently saving an unrunnable graph).
Authorization
bearerAuth API key authentication: send your Zernio API key in the Authorization header, prefixed with Bearer.
In: header
Path Parameters
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
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.updateWorkflow({ path: { workflowId: 'workflow_abc123', }, body: { name: 'Example', description: 'Hello, world!', nodes: [ { id: 'abc123', type: 'trigger', }, ], },});console.log(data);{ "success": true, "workflow": { "id": "string", "name": "string", "description": "string", "status": "string", "entryNodeId": "string", "nodeCount": 0, "updatedAt": "2019-08-24T14:15:22Z" }}