Receive notifications and trigger deployments with Slack

With the Slack integration in DeployHQ, 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 project, configuring notifications for different deployment events, and using the /deployhq slash command to list projects, deploy, and monitor progress — all from within Slack.

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 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 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

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

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 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 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 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:

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.

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
2. Check the deployment log for the specific error (build failure, connection timeout, permission issue)
3. If the issue is in your build pipeline, check the build pipeline logs 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 in your Slack workspace, the /deployhq slash command becomes available. Start by typing:

/deployhq help

This displays all available commands:

Listing your projects

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

If your DeployHQ account uses team permissions, 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:

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:

And the completion notification once it finishes:

Troubleshooting common issues

Notifications not appearing: Verify that the integration is active in your DeployHQ project settings. Check that the Slack channel still exists and that the DeployHQ 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. Ask your account admin to check team member settings.

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.

Get started

Ready to connect Slack to your deployments? Sign up for DeployHQ if you have not already — the Slack integration is available on all plans, including the free tier.

If you have questions about the Slack integration or any other aspect of DeployHQ, reach out to us at support@deployhq.com or on Twitter/X.