With the [Slack](https://slack.com) integration in [DeployHQ](https://www.deployhq.com), you can send deployment notifications to any Slack channel and trigger deployments directly from the Slack command line. Your team stays informed about every deployment without switching between tools, and developers can kick off a deploy without ever leaving Slack.

This guide covers the full setup: connecting Slack to your [DeployHQ](https://www.deployhq.com) project, configuring notifications for different deployment events, and using the `/deployhq` slash command to list projects, deploy, and monitor progress — all from within Slack.

[DeployHQ](https://www.deployhq.com) also supports [Discord and Microsoft Teams notifications](https://www.deployhq.com/blog/send-deployment-notifications-to-a-discord-or-microsoft-teams-channel) if your team uses a different chat platform.

## Why connect Slack to DeployHQ?

If your team already communicates in Slack, adding deployment notifications keeps everyone in the loop without extra effort:

- **Instant visibility** : The whole team sees when a deployment starts, succeeds, or fails — no need to check a separate dashboard
- **Faster incident response** : Failed deployment alerts land in Slack immediately, so the right people can react within seconds
- **Deploy without context-switching** : Trigger deployments from Slack using slash commands instead of loading the [DeployHQ](https://www.deployhq.com) interface
- **Audit trail in chat** : Deployment history lives in your Slack channel alongside the conversations that led to those deployments

## Setting up the Slack integration

To get started, navigate to the **Integrations** page in any [DeployHQ](https://www.deployhq.com) project, click **New Integration** , and choose **Slack** from the service picker.

You will see options to configure:

- **Message format** : The default format works well for most teams. We recommend keeping the rich text option enabled for clickable links and formatted output
- **Trigger events** : Choose when to send notifications (deployment started, finished, or failed)
- **Server filter** : Select which servers should trigger notifications — useful if you only want alerts for production deployments

![Slack config in DeployHQ](https://blog.deployhq.com/attachment/c7742ceb-b171-4e2a-b68f-5e30a9291cc8/j0Pqz-WK.png)

Click **Create Integration** and you will be redirected to Slack to authorize DeployHQ's access to your workspace.

![Authorise DeployHQ](https://blog.deployhq.com/attachment/96326bb3-753f-4055-bedf-72c135422657/thumb1400.png)

Once authorized, the integration is active and ready to use across your projects.

### Best practices for notification channels

How you organize Slack notifications depends on your team size and deployment frequency:

- **Small teams (1-5 developers)**: A single `#deployments` channel works well. Everyone sees everything
- **Multiple environments** : Use separate channels like `#deploys-staging` and `#deploys-production` to reduce noise. Configure each [DeployHQ](https://www.deployhq.com) server to notify the appropriate channel
- **Large teams with many projects** : Create per-project channels (`#deploy-api`, `#deploy-frontend`) so teams only see notifications relevant to their work
- **On-call workflows** : Route production failure notifications to a dedicated `#incidents` channel — especially useful if you've set up [zero-downtime deployments](https://www.deployhq.com/blog/zero-downtime-deployments-with-deployhq-a-step-by-step-guide) that your on-call team monitors

You can add the Slack integration to multiple projects, each pointing to a different channel. This gives you fine-grained control over who sees what.

## Receiving deployment notifications

Based on your notification settings, [DeployHQ](https://www.deployhq.com) sends a Slack message for up to three events:

- When a deployment **starts**
- When a deployment **finishes successfully**
- When a deployment **fails**

Each notification includes key details at a glance:

![Notification](https://blog.deployhq.com/attachment/518cd082-451b-461c-a9b8-1f8f41062533/l-Wlm-HBv.png)

The notification shows the commit message, deployment status, server name, and the start/end revisions. Clicking a revision link takes you directly to that commit in your repository host (GitHub, GitLab, or Bitbucket), and clicking the notification subject opens the full deployment report in [DeployHQ](https://www.deployhq.com).

### What to do when a deployment fails

When a deployment fails, the Slack notification gives you an immediate starting point for investigation:

1. Click the notification subject to open the deployment report in [DeployHQ](https://www.deployhq.com)
2. Check the deployment log for the specific error (build failure, connection timeout, permission issue). Our guide on [fixing SSH, SFTP, and FTP connection errors](https://www.deployhq.com/blog/troubleshooting-server-issues-with-deploy) covers the most common server-side issues
3. If the issue is in your build pipeline, check the [build pipeline logs](https://www.deployhq.com/support/build-pipelines) for detailed output
4. Fix the issue, push a new commit, and re-deploy — or trigger a redeployment directly from Slack

## Triggering deployments from Slack

Once you have authorized [DeployHQ](https://www.deployhq.com) in your Slack workspace, the `/deployhq` slash command becomes available. Start by typing:

```
/deployhq help
```

This displays all available commands:

![DeployHQ help](https://blog.deployhq.com/attachment/4035d1c7-b0b2-44ca-8e8b-11cbafb1965f/yf8Te-HC.png)

### Listing your projects

Use `/deployhq list` to see all projects you have permission to deploy:

![Available projects](https://blog.deployhq.com/attachment/5ae06f19-5347-4b09-bae7-a10d9ccd090e/0o4I2ND.png)

If your [DeployHQ](https://www.deployhq.com) account uses [team permissions](https://www.deployhq.com/support/your-account/team-members), each user only sees the projects they have been granted access to deploy.

### Running a deployment

To deploy, type `/deployhq deploy <project-permalink>` — for example:

```
/deployhq deploy api-test
```

You will see options to customize or deploy immediately:

![Deploy now](https://blog.deployhq.com/attachment/9bc80ea5-dc9a-4564-8b53-0a2c9eb15918/ih-I2HRb.png)

If your project has multiple servers, click **Customize** to choose a specific server or branch. Otherwise, click **Deploy Now!** to deploy the latest commit to your default server.

The deployment triggers immediately, and if you have notifications configured, you will see the progress in your Slack channel:

![Running deployment](https://blog.deployhq.com/attachment/229f3d8f-c2a4-4d7c-8c59-267a204a1a07/n1ZOq-NF.png)

And the completion notification once it finishes:

![Completed deployment](https://blog.deployhq.com/attachment/518e2828-aa3d-44aa-bfca-40319314c6bf/m-Ukx-Ll0.png)

## Troubleshooting common issues

**Notifications not appearing** : Verify that the integration is active in your [DeployHQ](https://www.deployhq.com) project settings. Check that the Slack channel still exists and that the [DeployHQ](https://www.deployhq.com) app has not been removed from your Slack workspace.

**Permission errors on /deployhq commands** : The user running the command must have deployment permissions in [DeployHQ](https://www.deployhq.com). Ask your account admin to check [team member settings](https://www.deployhq.com/support/your-account/team-members).

**Notifications going to the wrong channel** : Each project integration targets a specific channel. If you have moved channels or renamed them, update the integration settings in [DeployHQ](https://www.deployhq.com).

## Get started

For more advanced automation, you can also [trigger deployments via the](https://www.deployhq.com/blog/using-deployhq-s-api-automating-your-deployment-workflows-with-scripts-and-webhooks)[DeployHQ](https://www.deployhq.com) API using webhooks and scripts.

Ready to connect Slack to your deployments? [Sign up for DeployHQ](https://www.deployhq.com/signup) if you have not already — the Slack integration is available on [all plans](https://www.deployhq.com/pricing), including the free tier.

If you have questions about the Slack integration or any other aspect of [DeployHQ](https://www.deployhq.com), reach out to us at [support@deployhq.com](mailto:support@deployhq.com) or on [Twitter/X](https://x.com/deployhq).