Skip to main content
Variables are placeholders that Wave Runner replaces with real data when a workflow runs. Use them in any text field — SMS message body, API URL, CRM field value. Write {variable_key} and Wave Runner substitutes the actual value at runtime. For example:
Resolves to:

Inserting variables

Click + Insert Variable inside any text field in a node’s configuration panel. The variable picker opens — search by name or browse by category. Click any variable to insert it at your cursor position.
Type variables directly into any field without the picker. Type { followed by the variable key and }.
The picker only shows variables available for your workflow’s trigger type. Call Data variables do not appear in a Facebook Lead workflow, for example.

Variable reference

Contact info

Always available regardless of trigger type.

Call data

Available in workflows triggered by End of Call.
Call data variables resolve to empty strings if used in a workflow with a non-call trigger.

Appointment

Available when a booking was made during the call.
Use a Condition node to check {appointment.status} == 'booked' before sending a confirmation SMS, so it only fires when a booking actually occurred.

HubSpot contact

Available in workflows triggered by a HubSpot event. Additional properties — city, state, zip, country, job title — are available in the picker when a HubSpot trigger is active.

Facebook lead

Available in workflows triggered by Facebook Lead.

Custom variables

Define your own variables on the trigger node. Add entries to the Custom variables list on the trigger, give each a key (e.g., account_tier), and reference it anywhere in the workflow as {account_tier}. Use case: Trigger a workflow via webhook with a custom payload. Define the expected keys as custom variables so downstream nodes can reference them.

Example: SMS after a booked call

Next steps

Executions

Monitor workflow runs, inspect node logs, and troubleshoot failures.