Slack bot

Connect Shipyrd to your Slack workspace and use three slash commands to lock, unlock, and check the status of any destination — without leaving Slack.

When you’d use this

Most teams already live in Slack during work hours. Pulling deploy data into Slack — and pushing actions back out — keeps the dashboard from being one more tab to remember.

What the Slack bot does

Two halves:

1. Slash commands — /shipyrd lets anyone in the workspace lock a destination, unlock one, or pull the current deploy status.
2. Notifications — Shipyrd posts deploy and lock events into the Slack channels you’ve configured per application. See Notifications for how that’s wired up.

Install

The Slack workspace connection lives at the organization level in Shipyrd. Connect it once and every application in the org can use it.

1. In Shipyrd, open your organization settings.
2. Connect Slack (you’ll be sent through the Slack OAuth flow).
3. Once connected, individual applications can add Slack channels for outgoing notifications. See Notifications.

Slash commands

/shipyrd lock appname [destination]
/shipyrd unlock appname [destination]
/shipyrd status [appname] [destination]

A few things to know:

• appname is the application’s slug — lowercase, matches what’s in Shipyrd.
• destination is optional. If the application has only one destination, Shipyrd uses it. If there are several, you’ll need to specify which one (Shipyrd will list them if you don’t).
• Lock and unlock post a public message to the channel so the rest of the team sees who’s holding what.
• Status with no arguments shows every destination across every application in the org.

How users get matched

The first time you run a slash command, Shipyrd looks up your Slack profile email and matches it against the email on your Shipyrd user. Once matched, the binding sticks — subsequent commands are attributed to you without any extra setup. If your Slack email doesn’t match any Shipyrd user in the organization, the command fails with a message saying so.

Notifications

When you have one or more Slack channels configured for an application, Shipyrd posts:

• Deploy lifecycle events (started, completed, failed) for that application’s destinations.
• Lock and unlock events.

Per-channel event filtering and managing the channel list both happen on the application’s Notifications page.

Related

• Notifications — manage the Slack channels and events behind the bot
• Deploy locks — what the lock/unlock commands act on
• Office hours — auto-locks the bot will report