Integrations overview

Connections, under Settings, is where you connect Nash to your other systems — the apps your team already uses, and the code your developers run. This section is the hub for setting all of that up and for checking that it's working.

Use it to bring in a tool you already have, to give another system programmatic access to Nash, and to see what those systems have been doing.

What's in Connections

Piece	When to use it
Connect Microsoft Teams	Send workflow notifications into your Teams channels. Connect the app once here, then pick the channel in a workflow action.
Connect Slack	Post Nash notifications into your Slack channels. Install the Nash bot in your Slack workspace, then add a Slack channel as a notification destination.
API keys	Give another system programmatic access to Nash. Create a key, scope what it can do, and manage or revoke it.
Webhooks	Receive Nash events in your own backend as they happen, instead of polling for them.
Request logs	Inspect the API requests that have already run, when you need to see what happened.

Note

Connections is where you set up and manage these systems from the portal. To learn how to actually use the Nash API — endpoints, payloads, webhook event schemas, and signature verification — see the developer docs at docs.usenash.com.

E-commerce connections

If you sell through Shopify, Toast, or Wix, those connections are set up with Nash rather than added from this screen. Reach out to Nash to get an e-commerce platform connected to your account.

Once a store is connected, you sync its locations into Nash from Locations in your network settings — that's where your store and pickup locations are kept up to date.

Related

• Manage locations — your pickup and dropoff locations, including where store locations sync in.
• What are workflows — where a connected Microsoft Teams channel is chosen and used.