Workflow actions reference
Last updated: November 10, 2026
The full catalog of actions a workflow can run — the steps that do the work once a trigger fires and your logic passes. For how to place an action on the canvas, see Build a workflow in the portal. For triggers, conditions, and the overall model, see Workflow triggers, conditions, and actions.
Note
This is a beta feature. Reach out to Nash if you'd like early access.
How availability works
Not every action appears on every workflow. Three things decide what you can add:
The trigger's context. Every trigger works on one kind of thing — an order, a delivery, a task, or a job — and that context decides which actions the builder offers. An order trigger offers order actions (set a strategy, cancel the order); a delivery trigger offers delivery actions (flag it, cancel it). A handful of actions are available on any trigger.
Pre-creation triggers. The Order is being created trigger runs before the order is saved, so it can shape the order but can't send outbound messages. Messaging and other outbound actions are available on every trigger except that one. In exchange, it has two actions of its own — Update order text and Update order metadata — that no other trigger offers. The Order validation trigger is narrower still: Mark order invalid is the only action it offers.
Per-action availability. A few actions are turned on per organization (marked Available for some organizations below). If you don't see one, reach out to Nash.
The Order dispatched rule. On an order trigger, the delivery actions (Cancel delivery, Flag task or delivery, and Automatically reassign delivery) are offered only on the Yes branch of an Order dispatched rule, where the workflow has the order's current dispatched job and task to act on. The rule is available for some organizations; see Workflow triggers, conditions, and actions.
Nash dispatches the delivery; a provider or your own fleet carries it out. The cancel and reassign actions below act on the dispatch — they cancel or reassign who's assigned, they don't perform the delivery.
Tags and data
Action | What it does | Available on |
|---|---|---|
Add tag | Adds one or more tags. | Any trigger |
Add custom event | Emits a custom event that can trigger other workflows. See Use custom events. | Any trigger |
Extract metadata field | Pulls a metadata field out so later steps in the same workflow can use it. | Order, delivery, task, and job triggers |
Summarize | Summarizes order details into a value later steps can use. | Order triggers |
Generate document | Renders a PDF or ZPL label from your HTML template and stores it on the order or route. Later steps can use its link. | Available for some organizations |
Generate document is offered on order, route, delivery, and task triggers, and on Order is being created. A delivery or task run stores the document on its order. Fill in:
Document name — the name the document is stored under. Running the step again for the same order replaces the document with that name; renaming it stores a new document and keeps the one made under the old name.
Page size — A4, or A6 (label), which fits a parcel label.
Format — PDF, any printer, ZPL, 203 dpi label printer, or ZPL, 300 dpi label printer. Use ZPL for a thermal label printer, at your printer's resolution. ZPL labels always use the A6 page size.
Store as — Manifest, or Shipping label, which lists the document with the order's shipping labels. Get Shipping Label still returns only the carrier's label.
HTML template — a Jinja template. Order workflows can read
orderanditems; route workflows can readrouteandstops. Use theformat_datetimefilter for local times.CSS — optional styles. At-rules,
url(), and backslashes aren't allowed.Only generate when — an optional template expression. The document is skipped when it's false, for example when no item carries a tag.
The step's result is the Document link, which a later email, webhook, or HTTP request step can include — see Workflow variables reference. On Order is being created, a document that fails to render fails only its own step; the order is still created.
Order actions
Action | What it does | Available on |
|---|---|---|
Set dispatch strategy | Sets the order's dispatch strategy. | Order triggers |
Set optimization strategy | Sets the order's optimization strategy. | Order triggers |
Add requirements | Adds requirements to the order. | Order triggers |
Modify order price or tip | Changes an order's price or tip. | Order triggers |
Reschedule order | Moves or sets the order's pickup and dropoff windows — later by a set delay, to a target date, or to times counted from when the workflow runs. | Order triggers |
Remove order from route | Removes the order from its current route. If it isn't on a route, nothing changes. | Order triggers |
Cancel order | Cancels the current order. | Order triggers |
Update order text | Sets, prepends, or appends text on the order description or the pickup or drop-off instructions before dispatch. | Order is being created trigger only |
Update order metadata | Adds, updates, or removes one order metadata key while the order is being created. | Order is being created trigger only |
Mark order invalid | Adds a validation error so the order needs attention until it's fixed. The message can include | Order validation trigger |
Reschedule order has three methods. Delay moves every pickup and dropoff time later by the same amount — pick a quick delay of 12, 24, or 48 hours, or enter your own in minutes, hours, or days. Move to date moves the windows to a target date and keeps the same local pickup time. Either value can come from a workflow variable instead. Set windows sets any of the four times — the Pickup window and Dropoff window, each with Starts in and Ends in — counted from when the workflow runs, as an amount and unit or a workflow variable. A time you leave empty is cleared from the order, and at least one time is required. The editor shows an example of the resulting times and warns that the action replaces any pickup and dropoff times already on the order. Times under the organization's minimum lead time are raised to it.
Delay and Move to date work on scheduled orders that haven't been dispatched or archived. Set windows also accepts an order in now mode and switches it to scheduled. An order on a route has to be removed from the route first, and an order with a booked delivery window is changed through its booking, not here. On the Order is being created trigger, all three methods change the order before it's saved; there, Delay and Move to date leave a now-mode order unchanged.
Update order text and Update order metadata shape an order while it's being created, which is why only the Order is being created trigger offers them:
Update order text — choose the field (Order description, Pickup instructions, or Drop-off instructions) and how to apply your text: Replace existing text, Add before existing text, or Add after existing text. Turn on Only when instructions are missing (for the description, Only when the description is empty) to leave text that's already there untouched. Each action changes one field — add it again to change another.
Update order metadata — changes one key per action and keeps the rest of the order's metadata as it is: Add or update key, Add key if missing, or Remove key. Keys that Nash manages itself are protected and can't be changed.
Note
Workflows on the Order is being created trigger aren't available to every organization. Availability varies by organization — reach out to Nash for access.
Delivery actions
Action | What it does | Available on |
|---|---|---|
Flag task or delivery | Adds a flag named for the workflow so you can identify and sort it on the deliveries page. Flags the delivery when there is one, or the task when no delivery exists. | Delivery and task triggers, and the Task Attempts Exhausted trigger |
Cancel delivery | Cancels the current delivery's dispatch. | Delivery and task triggers |
Automatically reassign delivery | Reassigns the delivery using your current dispatch rules. | Delivery, task, and job triggers |
Notify provider: ready for pickup | Tells the delivery provider the order is ready for pickup. | Order, delivery, task, and job triggers, except pre-creation |
On the Task Attempts Exhausted trigger, Flag task or delivery flags the final failed attempt — its delivery if one was created, otherwise the task itself. Cancel delivery isn't offered there. When the job covers several packages, the trigger may not point to a single task or delivery, so there's nothing for the action to flag; add a condition ahead of it if those runs should stop before they reach the action.
On an order trigger, Cancel delivery, Flag task or delivery, and Automatically reassign delivery appear after an Order dispatched rule set to Yes, on its Yes branch. In organizations with that rule, the picker shows Cancel delivery and Automatically reassign delivery as unavailable until you add one, with a note to add the rule first.
Notify provider: ready for pickup has no settings. It notifies the provider on the order's current delivery once. Only providers that support it are notified, and nothing is sent once the courier has picked up or the delivery has finished. A job trigger on a job that covers several packages has no single delivery to notify, so nothing is sent.
Messaging
These outbound actions are available on every trigger except Order is being created.
Action | What it does | Available on |
|---|---|---|
Send an email | Sends an email to every recipient you list — email addresses, the people in a role, or a notification destination. | Any trigger except pre-creation |
Send an SMS | Sends a text message to every recipient you list — phone numbers, the people in a role, or a notification destination. | Any trigger except pre-creation |
Send a Slack message | Sends a message to a Slack channel. | Any trigger except pre-creation |
Send a webhook | Sends an event to your organization's registered webhook endpoints. | Any trigger except pre-creation |
Send a Teams message | Sends a message to a Microsoft Teams channel. | Available for some organizations |
Send to destinations | Notifies every contact on the notification destinations you choose, each on its own channel — for example email, SMS, or Slack. | Any trigger except pre-creation |
Call with an AI agent | Places a phone call with an AI agent. | Any trigger except pre-creation |
Send an email and Send an SMS each take a Recipients list. Select Add recipient for every row you need, then choose what the row is:
Email address (on an email) or Phone Number (on an SMS) — a contact you type in. The field accepts variables, so a row can resolve to the customer's own number or address when the workflow runs.
Role — everyone in your organization who holds the role you pick and has an email address (or, for an SMS, a phone number) on their user profile. Deactivated users, and members without that contact detail, are skipped.
Destination — the email addresses (or SMS numbers) saved on a notification destination. Only destinations with a contact for that channel are offered.
Roles and destinations are looked up each time the action runs, so adding someone to a role or editing a destination's contacts changes who later runs reach — you don't have to edit the workflow. A contact that appears more than once, for example typed in and also a member of a role, gets one message. One action sends to at most 250 recipients; anyone past that isn't messaged.
Send a webhook takes an Event title and a Message; both accept variables. Every webhook endpoint registered for your organization receives a notification.api_based event (and the older notification.message.created event) carrying the event title, the message, and the IDs of the order, job, task, and delivery the run is about, where the run has them.
Only send once per order
Some triggers fire more than once for the same order — Nash Order Needs Attention, for example, fires again each time a still-broken order is rechecked. To keep that from sending a message every time, turn on Only send once per order on Send an email, Send an SMS, Send a Slack message, Send a webhook, Send a Teams message, Send to destinations, or Call with an AI agent. It's off by default.
With the switch on:
The action sends the first time it runs for an order and is skipped for that order after that. Two days after that first send, it can send for the same order again.
Each action keeps its own count, so an email and a Slack message in the same workflow each send once.
Editing the workflow doesn't reset it — orders already notified aren't notified again because you published a change.
When a run has a job but no order, it counts per job instead.
A send that fails or reaches nobody doesn't count, so the next run can still send.
Route, activity, and Courier form submitted triggers don't run against an order or job, so the switch can't be turned on there and those runs send every time.
A skipped send still shows the step as Completed in the run. Open the run and the step reads Not sent: already sent for this order — see monitor workflow runs.
Events and integrations
Action | What it does | Available on |
|---|---|---|
Send HTTP request | Sends a request to an approved external API. See Send an HTTP request from a workflow. | Any trigger except pre-creation |
AI Decision | Chooses the workflow's next path using a yes/no judgment, a choice between outcomes you name, or a score. | Any trigger except pre-creation |
Run Custom Agent | Hands the workflow step to a configured Nash Agent and can branch on what it returns. | Available for some organizations |
Run browser automation | Runs a browser-automation script. | Available for some organizations |
Create, update, resolve, or assign route flags | Manages flags on a route from within the workflow. | Available for some organizations |
AI Decision is for a condition that's a judgment rather than a comparison — does this note describe a safety problem, which team should own this failure. Give it a Question or instructions and the Information to evaluate (only what you put there is evaluated), then pick a Decision type:
Yes / no — branches to Yes or No.
Choose an outcome — one branch for each outcome you name and describe.
Score against a rubric — you describe the levels and set a threshold; it branches to At or above threshold or Below threshold.
Every decision type also has an Uncertain branch, taken when the answer isn't confident enough, and an Error branch, taken when the decision couldn't be made. Connect a step to Error — without one, a failed decision fails the run. Any other branch you leave unconnected simply ends that path. A regular Test doesn't make a real decision; it follows Uncertain. To see a real one, save the workflow, test the step, and turn on Evaluate with the model.
Run Custom Agent invokes a Nash Agent — a separate product. The action lets a workflow call an agent you've already configured; setting up the agents themselves is done in Nash Agent, not here. See docs.usenash.com.
Related
Build a workflow in the portal — place these actions on the canvas.
Workflow triggers, conditions, and actions — the triggers and conditions that come before an action.
Notification events and variables reference — the events a workflow trigger can fire on.
Use custom events — chain one workflow into another with the Add custom event action.
Send an HTTP request from a workflow — call an approved external system with the Send HTTP request action.
Set up an HTTP connection — the org-admin setup that approves an external system for the Send HTTP request action.