Workflows

Update workflow

Changed on

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).

patch/v1/workflows/{workflowId}

Request

  • Base URL: https://zernio.com/api
  • URL: https://zernio.com/api/v1/workflows/{workflowId}
  • Auth: HTTP bearer

Path parameters

workflowIdstring required

Request body

namestring
descriptionstring
entryNodeIdstring nullable
accountIdstring

Reassign the workflow to a different SocialAccount. platform and profileId are derived server-side from the new account (the client never sends them directly). The account must belong to the caller's team and be on a workflow-supported platform (whatsapp, instagram, facebook, telegram, twitter, bluesky, reddit, tiktok). Changing this triggers a graph revalidation against the new platform.

Response

Workflow updated

successboolean

Changes

  • fd4ba69cb07aRevision changes
    • info

      added the new hubspot_upsert_contact enum value to the request property //

  • f8c8f34fb41aRevision changes
    • warning

      added the new account enum value to the / response property for the response status