Workflow triggers, conditions, and actions
Last updated: November 10, 2026
Every workflow is built from three kinds of building block: a trigger (the event that starts it), optional conditions and logic (which decide whether and how it continues), and actions (what it does). This page explains what each one is and how they fit together; the how-to and recipe articles link back here instead of repeating the model.
Workflows is a beta feature. If you don't see it in your portal, reach out to Nash if you'd like early access.
Triggers
A trigger is the event that starts a workflow — one trigger per workflow. Triggers are grouped into categories in the trigger picker:
Orders — order lifecycle events and pickup/dropoff time windows: Order is being created, Order validation, Order has been created, Nash Order Needs Attention, Order Not Dispatched Close to Pickup, Pickup Window Start, Pickup Window End, Dropoff Window Start, Dropoff Window End, Delivery Window Cutoff, Delivery Window Booked Timeout, Nash Order Ready to Fulfill, Optimization Unassigned Order, and Order Modified. The window-milestone triggers each fire a set number of minutes before, exactly at, or after that window edge. Delivery Window Cutoff fires a set number of minutes after the cutoff of the order's booked delivery window (0 fires at the cutoff itself); if the order moves to another window, the trigger moves with it. It fires whether or not the order has been dispatched, so add a condition if you only want orders that are still waiting. Delivery Window Cutoff availability varies by organization — reach out to Nash for access.
Deliveries — delivery tracking & status events: Delivery Status Transition, Stuck Status, Statuses Changed Too Quickly, Status Triggered Too Early, Time Elapsed Since Status, Delivery Incident Report, Driver Geolocation, Zone Geolocation, Driver Location Inconsistent, Dropoff Delayed, Pickup Delayed, Delivery Completed Too Early, Driver Stacking, Invalid Proof of Delivery Photo, Proof of Delivery Uploaded, Courier Updated, Timing Updated, AI Conversation Completed, and the Custom Event Listener, which listens for events other workflows emit. See use custom events.
Tasks — task dispatch & assignment events: Autodispatch Failed, Delivery Cancellation Failed, Internal Driver Not Assigned, Refund Request, Task Reassignment, and Live Monitoring Status.
Jobs — job-level events: Task Attempts Exhausted, Address Validation Failed, Delivery Creation Failed, and Job Updated. Job Updated runs when a request changes the job itself — for example a package update through the jobs API, or a dispatch strategy attached as the job is created. Edits made in the portal and changes to the order alone don't run it.
Activities — activity & optimization events: Activity Status Transition and Optimization Action Status.
Routes — route lifecycle events: Route Created, Route Started, Route Stop Completed, Route Completed, and Route Canceled.
Courier forms — Courier form submitted runs when a courier submits the courier form you select. This trigger is available for some organizations — reach out to Nash for access.
These are the same events Nash detects for notifications — the trigger list is the notification-event catalog wired as workflow start events. For the full list of events and the variables each one carries, see the notification events and variables reference.
Context
Each trigger works on one kind of thing — an order, a delivery, a task, a job, or a route — and that context is a real constraint: it decides which condition fields you can test and which actions you can add later in the same workflow. An order trigger gives you order fields and order actions; a delivery trigger gives you delivery fields and delivery actions. Pick the trigger that matches the thing you want the workflow to act on.
Conditions
A condition tests a property of the job against a value, using an operator. The properties you can test depend on the trigger's context (order, delivery, task, job, or route).
Operators: Greater Than, Less Than, Equals, Does Not Equal, Greater Than or Equal, Less Than or Equal, In, Not In, Starts With, Ends With, Contains, Does Not Contain, Matches Pattern, Does Not Match Pattern, Length. Presence operators take no value: Is Set, Is Missing (only
nullor a genuinely absent value counts as missing —0, an empty string, and an empty list are all set). Date/time fields add: Is After, Is Before, Is On or After, Is On or Before, Is Before Now, Is After Now, Is More Than N Minutes Ago, Is Within the Next N Minutes, Is More Than N Minutes After Another Field.Properties (representative — many more are available in the picker): Package / Order Value, Driver's Tip, Delivery Mode, Dispatch Strategy, Pickup Business Name / State / Zip / Country, Dropoff Business Name / City / State / Zip / Country, Items Count, Number of Packages, Package Count, Total Package Value, Driving Distance (meters), Drive Time (minutes), Day of Week, Minutes Until Pickup, Minutes Until Dropoff, Task Attempt Number, Weight (kg), Height / Width / Depth (cm), Volume (cm³), Max Item Length / Width / Height (cm), Max Item Weight (kg), Items Volume (m³), Tags, Contract, Courier Distance From Dropoff At Completion. Number fields show their unit in the label, so enter the value as a plain number in that unit.
Current local time — the clock at the order's pickup location when the workflow runs, as minutes since midnight. For example, to act only on orders created after 4 PM local time, test Current local time is greater than or equal to 960.
On an order trigger, Order Status stays at dispatched even after the job is canceled. To test where the delivery actually stands, use Current Task Status or Current Delivery Status — each reads the order's most advanced delivery attempt when the workflow runs and gives you a status picker for the value; both are empty until the order is dispatched. To skip canceled jobs, the simplest test is Job Canceled.
Contract is the contract of the quote a delivery attempt was dispatched on, picked from your contracts; use In to match any of several. It keeps matching after a contract is edited. A task that hasn't been dispatched on a quote yet has no contract, so on triggers that fire before dispatch, add Contract Is Missing with OR if those tasks should pass too.
Courier Distance From Dropoff At Completion is the straight-line distance, in meters, from the courier's last reported location to the order's dropoff when the delivery completed. It's empty before the delivery completes, and empty when no courier location came in during the 2 minutes before completion.
Add multiple conditions and combine them with AND / OR to match exactly the situations you care about.
Logic
Conditions can be arranged in a few shapes:
Filter — a straight gate: if the conditions aren't met, the workflow stops there.
Yes / No branch — send the job down one path when the conditions are met and a different path when they aren't, instead of just stopping.
Branch — split into multiple paths from the same workflow, so one workflow can handle several cases rather than you building a separate workflow for each.
Order dispatched
On an order trigger, Order dispatched branches on whether the order has been dispatched. Add it from the step picker, or pick it under Workflow context in a rule's property list. It stands alone — it can't be combined with other conditions in the same rule. The Yes branch works on the order's current dispatched job and task, so the steps after it can test job and task fields and use delivery actions such as Cancel delivery, Flag task or delivery, and Automatically reassign delivery. The No branch keeps only the order. It isn't offered on Order is being created or Order validation.
Order dispatched is available for some organizations — reach out to Nash for access.
One action branches too: AI Decision sends the workflow down a path per outcome when the question is a judgment rather than a comparison. See the workflow actions reference.
Actions
An action is what a workflow does once its trigger fires and its conditions pass — for example, add a tag, set a dispatch strategy, send a Slack message, flag or cancel a delivery, or emit a custom event. Which actions you can add depends on the trigger's context, and a few are available for some organizations only.
For the full list of actions — what each one does and where it's available — see the workflow actions reference.
See build a workflow to put these together.