Workflow actions reference

Last updated: September 1, 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.
  • 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.

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

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
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

Delivery actions

Action What it does Available on
Flag delivery Adds a flag to a delivery so you can identify and sort it on the deliveries page. Delivery and task triggers
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

Messaging

These outbound actions are available on every trigger except Order is being created.

Action What it does Available on
Send an email Sends one or more emails. Any trigger except pre-creation
Send an SMS Sends a text message to a phone number. Any trigger except pre-creation
Send a Slack message Sends a message to a Slack channel. Any trigger except pre-creation
Send a Teams message Sends a message to a Microsoft Teams channel. Available for some organizations
Call with an AI agent Places a phone call with an AI agent. Any trigger except pre-creation

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
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

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