Notifications

Push deploy and lock events out of Shipyrd into the channels your team already watches. Slack first, plus generic webhooks for anywhere else.

When you’d use this

Deploy data sitting in a dashboard nobody opens isn’t worth much. Notifications turn the events your team cares about — deploy started, deploy completed, deploy failed, destination locked or unlocked — into messages that show up where the team already is.

What gets sent

Shipyrd posts notifications for the same set of events to whichever channels you’ve connected:

Slack

Slack lives at two levels in Shipyrd:

  1. Connect Slack to your organization once. This is what installs the Shipyrd Slack app in your workspace and makes the slash commands available everywhere. See the Slack bot page.
  2. Per-application channels. Once Slack is connected, each application can post into one or more Slack channels. You manage that on the application’s page in Shipyrd — add channels, choose which events post, remove them when they get noisy.

It’s normal to point production deploys at one channel (#engineering) and staging deploys at a quieter channel (#deploys-staging).

Outgoing webhooks

For destinations that aren’t Slack — internal status pages, custom dashboards, another team’s notification system — each application can also have outgoing webhooks. Shipyrd POSTs a JSON payload to the URL you provide on every event.

Add or remove webhooks on the application’s page. There’s no client library you need to install on the receiving side; it’s just an HTTP POST.

Quieting things down

If a channel or webhook is too noisy, you have two levers:

  1. Turn off specific event types for that destination.
  2. Split traffic — production to one channel, lower environments to another (or to nowhere).