Notification trigger reference

Last updated: September 4, 2026

How a trigger is configured: its per-type Settings, the Advanced scoping conditions, the flag and custom-event options, and the organization's SMS sender — the configuration companion to create a notification trigger.

For the catalog of trigger events you can fire on and the {{token}} message variables you can drop into a message, see notification events and variables reference.

Each trigger's precise firing logic runs on Nash's side; the names and options below are exactly what the Type selector and message editor show.

Settings

Once you pick a Type, its Settings block asks for that type's firing parameters — a status, a threshold, a zone, a timing window. Some types take none. For example, Delivery Status Transition asks which status the delivery must reach; Time Elapsed Since Status asks for a duration and a status set; Zone Geolocation asks which zones to watch. The trigger events list notes what each type fires on.

Flag and custom event

A trigger can annotate the delivery or record an event whether or not it sends a message:

  • Flag Delivery — adds a flag to the delivery so you can spot and sort it on the delivery page.
  • Auto-Resolve Flag — offered for the "Stuck" Status, Pickup Delayed, and Dropoff Delayed types when you use Flag Delivery. When on, the flag clears itself once the condition no longer holds.
  • Add Custom Event — records a named custom event in the delivery's activity when the trigger fires, which downstream automations can listen for.

Advanced conditions

Expand Advanced to scope which deliveries a trigger applies to:

  • Only Selected Dispatch Strategies — limit it to the chosen dispatch strategies.
  • Only Selected Contracts — limit it to the chosen contracts. Available only when the orders feature is enabled for your organization.
  • Only Selected Conditions — limit it to deliveries whose metadata matches the key/operator/value conditions you build.

SMS sender configuration

The Settings tab holds your organization's SMS sender — the credentials for your SMS provider (Twilio) that 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 provider credentials and sender identity) or Nash Account - Custom Sender Identity (a Nash-managed sender with your sender identity). The selector is set up by Nash.
Account SID Your provider account SID. Optional for a Nash account (set it only for a subaccount).
Auth Token Your provider auth token, entered for a custom account. It's masked; leave it blank to keep the existing token.
Messaging Service SID Optional 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