When a deployment goes out, your team needs to know — immediately. Whether it is a production hotfix at 2 AM or a scheduled release during business hours, real-time [deployment notifications](https://deployhq.com/blog/selectable-deployment-notifications) keep everyone aligned and reduce the risk of miscommunication.

[DeployHQ](https://www.deployhq.com) integrates natively with both **Discord** and **Microsoft Teams** , so deployment alerts land directly in the channels your team already uses. No more switching between tools or wondering whether that latest push actually went live.

In this guide, we will walk through setting up both integrations step by step.

## How Deployment Notifications Work

When you trigger a deployment in [DeployHQ](https://www.deployhq.com) — whether manually, via [automatic deployment hooks](https://deployhq.com/blog/streamlined-automatic-deployment-hooks), or through a [CI/CD pipeline](https://deployhq.com/blog/building-a-ci-cd-pipeline-from-scratch-with-deployhq-a-step-by-step-guide) — the platform can notify external services at key stages of the process.

```
flowchart LR
    A["Git Push / Manual Trigger"] --> B["DeployHQ"]
    B --> C["Build & Deploy"]
    C --> D{"Notification Integrations"}
    D --> E["Discord Channel"]
    D --> F["Teams Channel"]
    D --> G["Slack, Email, etc."]
```

Notifications are sent per-server, so you can configure different channels for staging vs. production, or send all deployment events to a single channel — it is entirely up to you.

## Setting Up Discord Notifications

The Discord integration uses OAuth to connect directly with your Discord server. There is no need to manually create webhooks.

### Step 1: Add the Integration

In your [DeployHQ](https://www.deployhq.com) project, navigate to **Integrations** in the left sidebar and click **New Integration**. Select **Discord** from the list of available services.

### Step 2: Authorize With Discord

You will be redirected to Discord's authorization page. Sign in (if needed) and grant [DeployHQ](https://www.deployhq.com) permission to post to your server.

### Step 3: Choose a Channel

During the authorization flow, Discord will ask you to select which channel should receive deployment notifications. Pick the channel that makes sense for your team — a dedicated `#deployments` channel works well.

### Step 4: Configure Triggers

Back in [DeployHQ](https://www.deployhq.com), choose when notifications should fire:

- **All servers** : Every deployment to any server triggers a notification
- **Specific servers** : Only deployments to selected servers (e.g., production only) trigger a notification

Click **Create Integration** to finish.

### What It Looks Like

![Discord deployment notification example](https://blog.deployhq.com/attachment/8364ee57-745b-4f16-b6d2-755d8f849ef9/FXf-Yp3v.png)

The notification includes the project name, server, deploying user, and deployment status — giving your team immediate visibility into what changed and who pushed it.

## Setting Up Microsoft Teams Notifications

The Teams integration uses an **Incoming Webhook connector** , which you will create in Teams and then paste into [DeployHQ](https://www.deployhq.com). [DeployHQ](https://www.deployhq.com) also supports **Power Automate Workflows URLs** , which are automatically detected.

### Step 1: Create a Webhook in Microsoft Teams

1. Open Microsoft Teams and search for **Incoming Webhooks** in the top search bar
2. Select your team and click **Install**
3. Choose the channel that should receive notifications, then click **Setup**
4. Click **Configure** next to the Incoming Webhook connector
5. Copy the **webhook URL** from the dialog

The webhook URL will look something like this:

```
https://outlook.office.com/webhook/YOUR-TEAM-ID@YOUR-TENANT-ID/IncomingWebhook/UNIQUE-PATH
```

### Step 2: Add the Integration in DeployHQ

Navigate to **Integrations** → **New Integration** in your project and select **Microsoft Teams**.

Fill in the configuration:

- **Team Name** : Your Microsoft Teams team name
- **Webhook URL** : Paste the URL you copied from Teams

### Step 3: Configure Triggers

Just like Discord, you can choose whether to notify on all server deployments or only specific ones.

Click **Create Integration** to save.

### What It Looks Like

![Microsoft Teams deployment notification example](https://blog.deployhq.com/attachment/d46d98a4-43e5-475e-8fc4-605c66701729/QEw-DQNY.png)

Teams notifications appear as rich cards in your channel, providing a clear summary of each deployment event.

## Integration Execution Order

If you use multiple integrations (e.g., Discord + [Slack](https://deployhq.com/blog/receive-notifications-and-trigger-deployments-with-slack) + [Cloudflare cache purge](https://deployhq.com/blog/purge-your-cloudflare-cache-automatically-during-a-deployment)), they execute in the order they appear in your integrations list. You can reorder them by dragging to control the sequence.

```
sequenceDiagram
    participant D as DeployHQ
    participant S as Server
    participant DC as Discord
    participant T as Teams
    participant CF as Cloudflare

    D->>S: Deploy files
    S-->>D: Deployment complete
    D->>DC: Send notification
    D->>T: Send notification
    D->>CF: Purge cache
```

## Why Real-Time Deployment Notifications Matter

- **Incident response** : When something breaks after a deploy, your team can immediately see what changed and who deployed, cutting [troubleshooting time](https://deployhq.com/blog/troubleshooting-deployments-on-deployhq) significantly
- **Team visibility** : Remote and distributed teams stay aligned without having to ask did that deploy go out?
- **Audit trail** : A persistent log of deployment events in your chat history, complementing [DeployHQ's built-in deployment logs](https://deployhq.com/blog/deployment-log-enhancements)
- **Workflow automation** : Combine with [DeployHQ's API and webhooks](https://deployhq.com/blog/using-deployhq-s-api-automating-your-deployment-workflows-with-scripts-and-webhooks) for more advanced automation

## Other Notification Options

Discord and Teams are just two of the notification channels [DeployHQ](https://www.deployhq.com) supports. Depending on your workflow, you might also want to explore:

- **[Slack integration](https://deployhq.com/blog/deploy-web-applications-directly-from-slack-with-deployhq)**: Trigger deployments and receive notifications directly in Slack
- **[Email notifications](https://deployhq.com/blog/customise-your-notifications)**: Customizable email alerts for deployment events
- **[Browser notifications](https://deployhq.com/blog/notifications-in-your-browser)**: Desktop push notifications while you work
- **[Bugsnag, Honeybadger & Sentry](https://deployhq.com/blog/deployhq-integrations)**: Track deployments alongside error monitoring
- **[Rollbar](https://deployhq.com/blog/rollbar-notifications)**: Deployment tracking in your error management platform

For a full list, visit the [DeployHQ integrations documentation](https://deployhq.com/support/integrations).

## FAQ

### Can I send notifications to multiple channels?

Yes. Add a separate integration for each channel. For example, you could send production deployment alerts to a `#production-deploys` channel and staging alerts to a `#staging` channel by configuring different server triggers on each integration.

### What information is included in the notification?

Notifications include the project name, server name, deploying user, deployment status (success or failure), and a link back to the deployment in [DeployHQ](https://www.deployhq.com).

### Can I use this with automatic deployments?

Absolutely. Notifications fire regardless of how the deployment was triggered — manually, via [automatic hooks from GitHub or GitLab](https://deployhq.com/blog/streamlined-automatic-deployment-hooks), or through the [DeployHQ API](https://deployhq.com/blog/using-deployhq-s-api-automating-your-deployment-workflows-with-scripts-and-webhooks).

### Does Teams support Power Automate Workflows?

Yes. [DeployHQ](https://www.deployhq.com) automatically detects Power Automate Workflows URLs, so you can use either the classic Incoming Webhook connector or a Power Automate Workflows URL.

### Do notifications slow down my deployment?

No. Notifications are sent after the deployment completes, so they do not add any time to your deployment process.

* * *

Ready to keep your team in the loop? [Sign up for DeployHQ](https://deployhq.com/signup) and set up deployment notifications in minutes. If you have questions about the integrations or any other aspect of the service, reach out to [support@deployhq.com](mailto:support@deployhq.com) or find us on [X @deployhq](https://x.com/deployhq).