Notification trigger reference

Last updated: August 16, 2026

Every trigger type you can pick, every merge field you can drop into a message, and the SMS sender settings — the companion to create a notification trigger.

The names and options below are exactly what the Type selector and message editor show. Each trigger's precise firing logic runs on Nash's side; the descriptions here state what the type is for. For a plain-language glossary of the trigger concepts, see Nash notification triggers glossary.

Trigger types by category

The Type selector groups triggers into five categories. When you pick one, its Settings block asks for that type's parameters (a status, a threshold, a zone, a timing window — some types take none).

Delivery

Type What it's for
Delivery Status Transition A delivery moves to a status you choose.
Delivery Incident Report An incident is reported on a delivery.
Task Reassignment A task is reassigned.
Autodispatch Failed Automatic dispatch fails for a delivery.
Delivery Cancellation Failed A cancellation attempt fails.
Delivery Creation Failed A delivery fails to be created.
Internal Driver Not Assigned No internal driver has been assigned.
Invalid Proof of Delivery Photo The proof-of-delivery photo is flagged invalid.
Delivery Completed Too Early A delivery is completed earlier than expected.
Tasks Attempts Exhausted A task runs out of attempts.
Status Triggered Too Early A status is set earlier than expected.
Driver Stacking A driver is stacked across deliveries.
Time Elapsed Since Status A set amount of time passes since a status.
Proof of Delivery Uploaded A proof-of-delivery is uploaded.
Courier Updated The courier on a delivery changes.
Timing Updated A delivery's timing changes.
AI Conversation Completed An AI conversation finishes.
Delivery Note Added A note is added to a delivery.

Driver

Type What it's for
Driver Geolocation A driver reaches a geolocation.
Zone Geolocation A driver enters or leaves a zone.
Driver location inconsistent with delivery status The driver's location doesn't match the delivery status.
Dropoff Delayed - Dropoff ETA too far after specified dropoff time The dropoff ETA runs too far past the specified dropoff time.
Pickup Delayed - Pickup ETA too far after specified pickup time The pickup ETA runs too far past the specified pickup time.

Status

Type What it's for
"Stuck" Status A delivery is stuck in a status.
Statuses changed too quickly Statuses change faster than expected.
Live Monitoring Status A live-monitoring status condition is met.
Activity Status Transition An activity moves to a status/action you choose.
Custom Event Listener A custom event with a matching name is emitted (via API or from another trigger).

Refund

Type What it's for
Refund Request A refund is requested.

Order

Available only when the orders feature is enabled for your organization.

Type What it's for
Address Validation Failed An order's address fails validation.
Nash order needs attention An order needs attention.
Nash order ready to fulfill An order is ready to fulfill.
Order Not Dispatched Close to Pickup An order isn't dispatched close to its pickup time.
Delivery Window Booked Timeout A booked delivery window times out.
Optimization Unassigned Order Optimization leaves an order unassigned.
Optimization Action Status An optimization action reaches a status.
API Based An API-based notification is sent to the system.
Order Modified An order is modified.

The "Stuck" Status, Pickup Delayed, and Dropoff Delayed types also offer an Auto-Resolve Flag option when you use Flag Delivery.

Merge fields

Type {{ in a Message to open this list. Nash substitutes each token with the delivery's value when the message is sent. Use the tokens verbatim — they are never translated. Availability of a given token depends on the trigger type and the data on the delivery.

Token Value
{{customer.email}} Customer Email
{{customer.email_address}} Customer Email Address
{{customer.first_name}} Customer First Name
{{customer.last_name}} Customer Last Name
{{customer.phone_number}} Customer Phone Number
{{pickup_business_name}} Pickup Business Name
{{pickup_business.phone_number}} Pickup Business Phone Number
{{pickup_address}} Pickup Address
{{pickup_datetime}} Pickup Datetime
{{pickup_location.email}} Pickup Email
{{pickup_instructions}} Pickup Instructions
{{pickup_eta}} Pickup ETA
{{dropoff_address}} Dropoff Address
{{dropoff_datetime}} Dropoff Datetime
{{dropoff_business_name}} Dropoff Business Name
{{dropoff_instructions}} Dropoff Instructions
{{dropoff_eta}} Dropoff ETA
{{provider_name}} Provider Name
{{driver.name}} Driver Name
{{driver.phone_number}} Driver Phone Number
{{org_name}} Organization Name
{{job_tracking_link}} Job Tracking Link
{{job_details_url}} Job Details URL
{{customer_feedback_link}} Customer Feedback Link (when feedback is enabled)
{{job_id}} Job ID
{{job_cfg_id}} Job Configuration ID
{{job_external_identifier}} Job External Identifier
{{delivery_id}} Delivery ID
{{provider_delivery_id}} Provider's Delivery ID
{{reference_id}} Reference ID
{{request_id}} Request ID
{{description}} Package Description
{{delivery_incident_report_type}} Delivery Incident Report Type
{{delivery_incident_report_message}} Delivery Incident Report Message
{{proof_of_delivery_photo_url}} Proof of Delivery Photo URL
{{pod_upload_url}} Proof of Delivery Upload URL

Order tokens (with the orders feature):

Token Value
{{nash_order_id}} Order ID
{{nash_order_pickup_location.email}} Order Pickup Email
{{nash_order_dropoff_location.email}} Order Dropoff Email
{{nash_order_portal_url}} Order Portal URL
{{nash_order_external_id}} Order External ID
{{nash_order_packing_slip_url}} Order Packing Slip URL (ZPL)
{{nash_order_packing_slip_pdf_url}} Order Packing Slip PDF URL
{{nash_order_validation_errors}} Order Validation Errors

Some trigger types swap in their own extra tokens — for example Refund Request adds refund fields (Refund Request ID, Status, Amount, Reason), Optimization Action Status and Activity Status Transition add their action/status/URL fields, and email destinations add location-email tokens. The {{ menu always shows what's available for the trigger and channel you're on.

SMS Sender Configuration

The Settings tab holds your organization's SMS sender — the Twilio setup Nash uses to send SMS notifications. (This tab is hidden for provider organizations.)

Field What it is
Enabled Turns the SMS sender on or off.
Account Type Custom Account (your own Twilio credentials and sender identity) or Nash Account - Custom Sender Identity (Nash's Twilio credentials with your sender identity). The selector is set up by Nash.
Account SID Your Twilio Account SID. Optional for a Nash account (set it only for a Twilio subaccount).
Auth Token Your Twilio auth token, entered for a custom account. It's masked; leave it blank to keep the existing token.
Messaging Service SID Optional Twilio Messaging Service SID.
From Number Optional sending number.

Select Save to store the configuration. Delete Settings removes the SMS sender from your organization; this can't be undone.

Related