Workflow Docs

Variables

Use data from earlier nodes in messages, conditions, and integrations.

Variables let you use information from earlier steps in later ones. The editor looks at what is connected before the step you are editing and lists available fields (message, customer, trigger, HTTP response, branch labels, and more).

When to use

  • Personalize message body text (WhatsApp, Messenger, Instagram).
  • Drive If / Else and Switch case conditions.
  • Bind Fireberry field values, HTTP request body placeholders, or task title/body slots.
  • Map Update Customer fields from data produced earlier in the flow.

How it works in the editor

  1. Connect the node you are configuring to nodes that run before it in the flow.
  2. Open the node form. Fields that support variables show a tree picker (or “Add variable” for {{1}}-style placeholders).
  3. Pick a fixed value from an upstream node or, where supported, an expression.
  4. At runtime, the workflow engine resolves the binding to the actual value for that execution.

The picker lists fields from connected upstream nodes. Branch nodes (answers, If / Else paths, switch cases, timeout, and fallback) still expose their parent’s context so you can reuse trigger and message data downstream.

Configuration (by field type)

PatternWhat it doesWhen to use
Tree pickerSingle binding to one upstream field or expressionFireberry values, Update Customer, If conditions, template variable slots
{{n}} placeholdersNumbered slots in free text; each slot gets its own bindingHTTP body, task title/body
Inline body editorWhatsApp/Messenger/Instagram body with variable chipsMessage actions

Flow behavior

  • On the node you are editing, variable pickers are for using upstream data, not for defining new outputs (message nodes and switch cases add outputs for later steps when you configure them).
  • Clearing a binding in the picker clears that field on the node.
  • If no upstream nodes are connected, the picker may be empty; connect triggers and actions first.

Examples

Greet by name after a trigger

  1. Start with a Pingmee Trigger (or channel trigger) that exposes customer/message variables.
  2. Add WhatsApp (or Messenger/Instagram) and connect from the trigger.
  3. In Body, open the variable picker and insert the customer name (or nickname) from the trigger branch.

HTTP POST with dynamic JSON

  1. Add HTTP Request after a node that produces data.
  2. Set method to POST and write body JSON with {{1}}, {{2}}, etc.
  3. Use Add variable and bind each {{n}} to the upstream fields you need.

On this page

When to useHow it works in the editorConfiguration (by field type)Flow behaviorExamplesGreet by name after a triggerHTTP POST with dynamic JSONRelated