Workflow variables reference
Last updated: November 10, 2026
{{ variable }} placeholders let an action's inputs carry live data about the order, delivery, or job the workflow is acting on. Instead of typing a fixed value, you write a placeholder like {{ order.id }}, and when the step runs Nash fills in that order's real ID.
This is a general workflow capability — it works in the input fields of many actions. You can use it in a Send HTTP request step's path or body, in a message action, and in other action inputs that accept free text. This page is the catalog of placeholders you can reference.
Note
This is a beta feature. Reach out to Nash if you'd like early access.
Two ways a variable resolves
How a placeholder fills in depends on whether it's the only thing in the field:
A field that is exactly one
{{ ... }}and nothing else keeps the value's real type. You can drop in a whole number, or a whole object, not just text. For example, a field set to exactly{{ order.value_cents }}sends the number1299, not the text"1299". (This native-type behavior applies to the Send HTTP request action's fields.)Otherwise the placeholder is substituted into the surrounding text. In a field like
Order {{ order.external_id }} is on the way, the placeholder is replaced inline and the whole field renders as text.
Warning
A missing or unknown variable makes the step fail — it doesn't quietly send a blank. Reference only fields that exist for the trigger you're on. Which fields are available depends on what the trigger is about: an order trigger has
order.*; a delivery trigger hasdelivery.*and can reach the parentorder.*, and so on.
Event data
trigger_metadata.<...> reaches into the data the triggering event carried — for example the order or the attempt behind a delivery-status change. The path after trigger_metadata. depends on the shape of the event that fired the workflow, so it's specific to that trigger. If the path isn't present on the event, the step fails, so only reference data you know the event carries.
Results from earlier steps
node_var_<step> references the output an earlier step stored, where <step> is that step's name. Later steps can read it to branch or to pass a value onward.
The Send HTTP request action also records a few extra results for its step that you can branch on:
Placeholder | What it holds |
|---|---|
| The value the step captured from the response. |
| Whether the step succeeded — the text |
| The HTTP status code the request came back with. |
| How long the request took, in milliseconds. |
| A short, human-readable reason the step failed, if it did. |
The Generate document action records these results for its step. When it doesn't produce a document, the link and ID are empty and the page count is 0:
Placeholder | What it holds |
|---|---|
| The link to the generated document (Document link). |
| Nash's identifier for the stored document. |
| Whether a document was generated — |
| The number of pages in the document. |
Fields you can reference
Each entity has its own namespace — order.<field>, delivery.<field>, and so on. Write the field name in lowercase, with words joined by underscores, exactly as shown below (for example {{ order.pickup_phone_number }}). A namespace is only available when the trigger's context includes that entity.
Nash dispatches the delivery; a provider or your own fleet carries it out. The courier and provider fields below describe whoever is fulfilling the delivery.
Order — order.*
The order tables here are a selection of the most-useful fields. Orders carry many more; see Order fields & settings reference for what every order field means. Variable names follow the lowercase, underscore-separated pattern shown in the tables above — with a pickup_ or dropoff_ prefix where a field is specific to one end of the trip (for example order.pickup_phone_number, order.dropoff_address_city). When you're unsure of the exact name for a field, use one already shown here as your model.
Identity
Variable | What it holds |
|---|---|
| Nash's identifier for the order. |
| Your own order ID. |
| Your grouping ID linking related orders. |
| A reference string supplied with the order. |
| The order's current lifecycle status. |
| Status of the order's most advanced delivery attempt (Current Task Status in the condition picker); empty until the order is dispatched. |
| Status of the delivery on that attempt (Current Delivery Status); empty when the attempt has no delivery. |
Pickup and dropoff
Variable | What it holds |
|---|---|
| Business at each stop. |
| Pickup contact name (dropoff has the same pair). |
| Contact phone at each stop. |
| Contact email at each stop (dropoff is the customer email). |
| Full street address at each stop. |
| City (state, zip, and country follow the same |
| Free-text instructions for each stop. |
Timing
Variable | What it holds |
|---|---|
| Requested pickup window, in your org's timezone. |
| Requested dropoff window, in your org's timezone. |
| Minutes from now (negative once the time has passed). |
| Weekday name of the pickup time. |
Contents, value, and links
Variable | What it holds |
|---|---|
| The order's description. |
| Number of items. |
| ISO currency code. |
| Declared order value, in cents. |
| Tip, in cents. |
| Labels attached to the order. |
| Link to the order in the portal. |
| The Nash-hosted tracking page for the order. |
| Link to the order's packing slip as a printable PDF (empty when the order has no packing slip). |
| Link to the order's packing slip as a raw ZPL printer payload (empty when the order has no packing slip). |
Delivery — delivery.*
Also a selection. See Delivery fields & columns reference for what every delivery field means; variable names follow the same lowercase, underscore-separated pattern shown here (for example delivery.courier_phone_number). When you're unsure of the exact name, model it on one already shown above.
Variable | What it holds |
|---|---|
| The delivery's current status. |
| The provider (or your own fleet) fulfilling it. |
| The provider's own reference for this one delivery (shown as Provider Delivery Reference in the builder). |
| Estimated pickup time. |
| Estimated dropoff time. |
| Latest acceptable dropoff time. |
| The courier's name. |
| The courier's phone number. |
| The vehicle type. |
| The provider's tracking URL (often empty for own-fleet deliveries). |
| The Nash-hosted, customer-facing tracking page. |
| The Nash customer feedback page. |
| The proof-of-delivery photo. |
| Straight-line distance in meters from the courier's last reported location to the order's dropoff when the delivery completed (Courier Distance From Dropoff At Completion). Empty before completion, and when no courier location came in during the 2 minutes before completion. |
| ISO currency of the delivery's prices. |
| Base delivery fee the provider charged, before tolls, wait time, and other fees, in cents. |
| Total delivery price including fees, in cents. |
Package — package.*
The package.* namespace mirrors the order.* pickup, dropoff, address, contact, and value fields — reference them the same way, as package.<field>. It also carries a few package-specific fields:
Variable | What it holds |
|---|---|
| Your own package ID. |
| A reference string supplied with the package. |
| The package's description. |
| Number of items. |
| Declared value and its currency. |
| The package's delivery mode. |
Job — job.*
A job is the dispatched delivery Nash creates from an order.
Variable | What it holds |
|---|---|
| Nash's identifier for the job. |
| Your own job ID. |
| Link to the job in the portal. |
| Labels on the job (copied from the order). |
| Number of packages on the job. |
| Combined declared package value, in cents. |
Task — task.*
A task is one delivery attempt.
Variable | What it holds |
|---|---|
| Nash's identifier for the attempt. |
| The provider assigned to the attempt (shown as Provider in the builder). |
| The name of the provider carrying the attempt. |
| The contract of the quote the attempt was dispatched on (shown as Contract in the builder). It holds the contract's original ID, which stays the same when the contract is edited. Empty until the attempt has a winning quote. |
| The attempt's current status. |
| The attempt's sequence number, starting at 1. |
| The human-readable reason the attempt failed, if it did. |
Courier form — courier_form.*
Available on courier-form workflows, where a driver submits a form.
Variable | What it holds |
|---|---|
| The form's type. |
| The form's display name. |
| The value a driver submitted for a specific form field. Replace |
Provider — provider.slack_channel
Variable | What it holds |
|---|---|
| The Slack channel configured for the delivery's provider. |
Notifications use a different set
Customer notification messages have their own, friendlier set of tokens — aliases such as {{ dropoff_address }} and {{ driver.name }} — on top of these workflow variables. If you're composing a notification, use that vocabulary, not the entity variables here. See Notification events and variables reference.
Related
Build a workflow in the portal — where you place actions and fill in their inputs.
Send an HTTP request from a workflow — the action that templates a path, query, headers, and body.
How workflows work — triggers, conditions, and the overall model.