Workflow nodes

A workflow is made of nodes. Each node is { "id", "type", "config" }, plus an optional label and canvas position. This page lists all 17 types and the fields their config takes. Every string field accepts {{variable}} interpolation, resolved when the node runs.

#trigger

Exactly one per workflow. It decides what starts a run. Outputs: one edge.

A whatsapp_event workflow never starts on the status of a message sent by a workflow, sequence or comment automation, so it cannot loop on itself.

#send_message

Sends one message into the run's conversation. Outputs: one edge.

Button and quick reply titles are capped at 20 characters, card titles and subtitles at 80. A postback with no payload gets pozy:workflow:<this workflow id>, so a tap answers this workflow's pending wait_for_reply. workflowId on a button starts that workflow instead.

Workflows can only send within the platform's messaging window. messageTag is not available: HUMAN_AGENT is reserved for replies typed by a person. On WhatsApp, a run that may start outside the 24-hour window must open with a template.

#wait_for_reply

Pauses the run until the contact answers. Outputs: reply or timeout.

A button tap also counts as a reply and sets {{postback.payload}} and {{postback.title}}; a quick reply tap sets {{quickReply.payload}} and {{quickReply.title}}. Each reply clears the previous tap.

#condition

Branches on variables. Outputs: the id of the first rule that matched, otherwise default.

{
  "id": "route",
  "type": "condition",
  "config": {
    "rules": [
      { "id": "vip", "variable": "contact.tags", "operator": "has_tag", "value": "vip" },
      { "id": "recent", "variable": "contact.lastInteractionHoursAgo", "operator": "less_than", "value": "48" }
    ]
  }
}

#delay

Waits, then continues. Outputs: one edge.

The run is suspended while it waits and resumes on a timer. Remember the messaging window: a long delay on Instagram or Facebook can push the next message outside it.

#a_b_split

Sends contacts down one of two branches at random. Outputs: a or b.

Tag each branch with add_tag so you can compare results later.

#end

Ends the run as completed. No config.

#set_variable

Sets run-scoped variables that exist only for this run. Outputs: one edge.

#set_field

Writes a custom field on the contact, which persists after the run. Outputs: one edge.

Fires contact.field_changed when the value changes. Does nothing on api_call runs that have no contact.

#add_tag and remove_tag

Add or remove one tag on the contact. Outputs: one edge.

Fire contact.tag_added and contact.tag_removed when they change something. Do nothing on api_call runs that have no contact.

#enroll_sequence

Puts the contact into a sequence. Outputs: success or error.

#webhook

Calls your server and saves the response. Outputs: success on a 2xx, otherwise error.

{
  "id": "lookup",
  "type": "webhook",
  "config": {
    "url": "https://api.acme.example/orders/lookup",
    "method": "POST",
    "headers": { "Authorization": "Bearer acme_internal_token" },
    "bodyTemplate": "{\"phone\": \"{{contact.phone}}\", \"text\": \"{{lastMessage}}\"}",
    "saveAs": "order"
  }
}

Then use {{order.body.status}} in a later message or condition. Check the signature or token on your side, since anyone who learns the URL could call it.

#hubspot_upsert_contact

Creates or updates the contact in the profile's connected HubSpot portal. Outputs: success or error (HubSpot not connected, or HubSpot refused the write).

Pozy updates the HubSpot contact already linked to this person, else one matching the email, then the phone, else it creates one. An existing HubSpot contact only gets the fields this node sets; empty values are skipped.

#ai

Asks a language model and saves the answer. Outputs: success, error, or tool:<name> when the model chooses one of your tools.

Use tools to let the model route the conversation: for example a book_demo tool whose edge leads to a booking message, and a human tool whose edge leads to a handoff.

#handoff

Ends the run as exited and flags the conversation for a person. No output edge.

To also pass a Meta thread to another app, call thread control when workflow.run.completed arrives with execution.status: "exited".

#start_call

Places a WhatsApp call to the contact. WhatsApp only. Outputs: success, permission_required or failed.

WhatsApp requires the person's permission before a business calls them. Route permission_required to a message explaining why you want to call. See WhatsApp calling.

#Validation

Saving a workflow checks that node ids are unique, that edges point at existing nodes, that WhatsApp-only nodes (start_call, template and interactive messages) are not used on other platforms, and that Instagram and Facebook-only fields (buttons, quickReplies, cards) are not used elsewhere. A problem answers 400 with a message that describes it.