Flow Builder

Flows are directed graphs. A Trigger starts the run, each node returns an outcome, and edges decide where execution goes next. Nodes pass data through run context and reusable variables.

Core concepts

Use template variables in supported fields:

{{nodes.trigger.message}}
{{variables.customerName}}

Undefined or null values resolve to an empty string.

Trigger

Entry point for every flow. It inspects incoming WhatsApp messages and decides whether the flow should start.

A blank keyword/regex behaves as a catch-all trigger.

Edges: default

Context output: message text, remote JID, message ID, timestamp, trigger type, matched trigger value, selected row/button metadata when present.

Send Message

Sends a text message, image, or video to the current contact.

Edges: default

May terminate: yes. If it has no outgoing edge, the flow can end here.

Send Interactive

Sends a WhatsApp interactive list, button set, or product-style message. Lists are the most common option for menu flows.

{
  "sections": [
    {
      "title": "Main menu",
      "rows": [
        { "id": "sales", "title": "Sales" },
        { "id": "support", "title": "Support" }
      ]
    }
  ]
}

Edges: default plus edge rules for selected rows/buttons when configured by the editor.

Parking: yes. Interactive replies can resume routing from this node when the selected row ID belongs to the list.

Condition

Branches the flow based on text, selected row/button IDs, outcomes, or other context values. Branches are evaluated in order, and the first match wins.

Edges: one edge per branch and one default edge.

Context output: matchedBranch

HTTP Request

Calls an external HTTP API and stores the response.

Edges: success, error

May terminate: yes.

The executor validates outbound URLs before calling them. Private, loopback, link-local, and otherwise unsafe targets are blocked to reduce SSRF risk.

Delay

Pauses the run for a configured number of seconds.

Edges: default

Parking: yes.

Go To

Jumps directly to another node by ID. Use it for loops or returning to a menu.

Edges: none. The jump target is stored in node configuration, not represented as an edge.

Validation: publish fails if the target is missing.

Set Variable

Creates or updates named variables from static text or interpolated values.

customerName = {{nodes.user-input.capturedText}}

Edges: default

May terminate: yes.

Variables are referenced later with {{variables.name}}.

User Input

Sends an optional prompt and waits for the contact's next text message.

Edges: default, timeout

Parking: yes.

Context output: capturedText, plus the named variable when configured.

Media

Sends an image or video with an optional caption.

Edges: default

May terminate: yes.

LLM

Runs the placeholder LLM step and stores a response. The current executor records the prompt and writes a placeholder response until a model provider is configured.

Edges: default, error

May terminate: yes.

End

Marks the run as ended. End lives under Advanced in the editor because many action nodes can terminate implicitly.

Edges: none.

Edge summary

Validation before publish

Publishing calls the shared graph validator from @wp-engine/nodes.

Blocking errors include:

Warnings include unreachable nodes and implicit terminal nodes. Warnings help clean up the graph but do not always block publishing.

Common patterns

Simple auto-reply

Trigger -> Send Message

Menu with support capture

Trigger -> Send Interactive -> Condition
                         sales -> Send Message
                       support -> User Input -> Send Message
                       default -> Send Message

Follow-up loop

Send Message -> Delay -> Go To(target: Send Message)

Use loops carefully. Add an exit condition or timeout path so contacts do not get repeated messages indefinitely.