Workflows

A Workflow is an automation graph that runs at the account level — not tied to any single agent. Workflows fire on triggers (conversation events, schedules, incoming webhooks), execute a graph of nodes, and can call external APIs, transform data, write to Tables, send messages, etc.

If a Flow is "what the agent says next", a Workflow is "what happens around the agent".

Each node carries nodeId, alias, position, type, and a typed data payload.

Reference validation: on create/update, the API validates every cross-resource reference inside data — aiModelId, customToolIds, tableId, recordTypeId, triggeredByAgentIds[], triggerByWebhookIds[], connectedAccountId, knowledgeBaseIds, etc. If any referenced id does not exist or does not belong to your account, the request returns 400 bad_request with details.issues[].code === "not_found" and the node is not persisted. See Errors.

Schema-level checks also apply to SCHEDULED_TRIGGER (cronExpression validated by cron-validate, timezone against IANA), WEBHOOK and API (url must be a valid URL).

Automation workflows expose one runtime variable per node, with name = nodeId. A node api_1 can be referenced downstream as {api_1}. This is in addition to explicitly declared Workflow Variables.

Interpolable fields include the same set as Flows, plus:

• AI Capture: prompt, instructions.
• Data Transformer: prompt.
• Tools AI: instructions, prompt.
• Transcription: audioUrl.
• Create Record Activity: rowId, content.
• WhatsApp template variables: templateVariables.header, body, buttons.

Capturing specific values. The API node can extract values from its JSON response into named variables via its variables field ({ key, value, fullResponse }), and AI_CAPTURE / TOOLS_AI / TRANSCRIPTION populate variables via captureVariables. All capture targets must reference a variable that already exists (create it first via POST /workflows/{workflowId}/variables). In captureVariables you may reference it by { "name": "<var>" } or { "id": <id> } — the API resolves and links it to the canonical { id, name, description }; an unknown name/key returns 400. For the API node's value path syntax (dot/[n] property access into the JSON response), see Flows → API node response paths.

Logs a manual activity on a specific Object record at workflow runtime.

{
    "nodeId": "node_create_activity_1",
    "type": "CREATE_RECORD_ACTIVITY",
    "position": { "positionX": 640, "positionY": 0 },
    "data": {
        "type": "CREATE_RECORD_ACTIVITY",
        "recordTypeId": 5,
        "rowId": "{contact_row_id}",
        "activityType": "PHONE_CALL",
        "content": "Llamada de seguimiento: {call_summary}"
    }
}

Validation: recordTypeId must point to a real record type on an Object (not a Table) in your account. activityType must be a valid enum value. Variables in rowId and content must exist — the API returns 400 with the offending variable name if any reference is unknown.

Iterates over an array stored in a workflow variable. The wire type is ITERATION.

{
    "nodeId": "node_loop_1",
    "type": "ITERATION",
    "alias": "Loop",
    "position": { "positionX": 320, "positionY": 0 },
    "data": {
        "type": "ITERATION",
        "variableName": "items",
        "variablePath": "data.items",
        "continueOnError": false
    }
}

Edges: connect three outgoing handles — body (for-each), completed (after all items), empty (null/empty list; does not route to completed). Inside the loop, {<loopNodeId>.item}, {<loopNodeId>.index}, and {<loopNodeId>.length} are available (use the loop node's nodeId from the graph). {<loopNodeId>.item} is the entire current item (JSON if object) — there is no {<loopNodeId>.item.field} dot-access. DYNAMIC_TABLES SEARCH stores a top-level array of rows; leave variablePath empty when looping that output.

Exits the current loop and continues on the loop's completed path. Place only inside a Loop body branch; outside an active loop the automation fails.

{
    "nodeId": "node_break_1",
    "type": "BREAK",
    "position": { "positionX": 640, "positionY": 0 },
    "data": { "type": "BREAK" }
}

Changes another automation's status (SET_ACTIVE, SET_DRAFT, or TOGGLE). Does not publish draft graph changes.

{
    "nodeId": "node_status_1",
    "type": "AUTOMATION_STATUS",
    "position": { "positionX": 320, "positionY": 0 },
    "data": {
        "type": "AUTOMATION_STATUS",
        "automationId": 1,
        "action": "SET_ACTIVE"
    }
}

automationId is validated at save time — it must exist in your account.

Sends a WhatsApp Business template message. Distinct from SEND_MESSAGE (conversation push).

{
    "nodeId": "node_wa_1",
    "type": "SEND_WHATSAPP_MESSAGE",
    "position": { "positionX": 320, "positionY": 0 },
    "data": {
        "type": "SEND_WHATSAPP_MESSAGE",
        "recipientMode": "PHONE_NUMBER",
        "personName": "{first_name} {last_name}",
        "phoneNumber": "{phone_number}",
        "phoneNumberId": "1132681309928224",
        "template": "hello_world",
        "templateVariables": { "body": { "1": "{first_name}" } }
    }
}

Resolve phoneNumberId and template via the read-only integrations endpoints below.

For SEND_WHATSAPP_MESSAGE, use a WhatsApp number where canSendMessages is true (an assistant is assigned).

Every time a workflow runs it records an execution. Read them to audit results, debug failures, or track credit usage.

List /public/v1/workflows/{workflowId}/logs — paginated, with optional status, start_date, and end_date filters. Each run (basic fields):

Detail /public/v1/workflows/{workflowId}/logs/{logId} — the run above plus node_results: [{ node_id, alias, type, success, error, ai_credits, created_at }], one entry per node that executed.

frontline workflows list --table
frontline workflows create --name "Daily CRM Sync"
frontline workflows nodes create --data '{"nodeId":"trigger_1","type":"TRIGGER","position":{"positionX":0,"positionY":0},"data":{"type":"TRIGGER","triggerType":"CONTACT_CREATED"}}'
frontline workflows analytics --start-date 2026-01-01 --end-date 2026-12-31
frontline workflows logs --workflow-id 2 --table
frontline workflows logs --workflow-id 2 --status FAILED --start-date 2026-01-01
frontline workflows logs get 9001 --workflow-id 2 --pretty
frontline integrations list --table
frontline integrations whatsapp-templates --table