Manage notification destinations

Last updated: August 16, 2026

A destination is a named contact group that a trigger sends to. Each destination holds one or more channels — the actual places a message lands, like an email inbox, an SMS number, or a Slack channel. Set these up before (or while) you build triggers.

You'll find them on the Destinations tab of the Notifications workspace. See set up customer notifications for the workspace overview.

Create a destination

On the Destinations tab, select New Destination. Each destination is a card with:

  • Name — how the destination appears when you pick it in a trigger's Send To list.
  • Description — optional context.
  • Channels — one or more delivery channels. Use Channel to add another.

Channels you can add

Each channel takes the address or ID it needs. Some channels expose their own {{merge fields}} when you compose a message.

  • Email — enter one or more email addresses.
  • SMS — enter the phone number. Sending SMS relies on your organization's SMS sender — see SMS Sender Configuration.
  • Slack — enter the channel, plus a Slack Workspace ID. Use Test to send a test message and confirm the channel is reachable (see below). If you haven't yet, install the Nash Notification Bot in your Slack workspace first — see connect Slack.
  • WhatsApp — enter the WhatsApp number.
  • Webhook — posts to your configured webhook endpoints. Save the destination to enable the channel.
  • Push Notification (Nash Agent) — sends a push notification through Nash Agent.
  • Custom Agent — routes to a custom agent you select.

Note

Some channels — Voice AI, Pylon, and Zendesk — are set up by Nash rather than self-serve. Reach out to Nash if you'd like to route notifications to one of those.

Send a Slack test

On a Slack channel, select Test to send a test message straight to that channel. It sends a short test note so you can confirm the channel name is right and that the Nash bot can post there before you wire it to a live trigger. If the test can't be delivered, check that the channel name is correct and that the Nash bot has access to it.

Save

Select Save on the card. A saved destination becomes selectable in any trigger's Send To field. Whether a message ultimately arrives depends on the channel being reachable (a valid address, a bot with access, a working webhook endpoint) — the destination setup here is the client-side half.

Related