We've spent the last few weeks closing the gap between the deploy finished
and the right people know it finished.
That gap is where production incidents hide: someone shipped a hotfix at 4pm, the chat channel was muted, the PR reviewer assumed it was still in staging, and the customer-facing status page never updated.
Five new integrations are now live, each filling a different version of that gap. One pushes status back into the place where engineers already review code. Three send alerts into the chat tools your team actually watches. The last one is a signed webhook for everything else — status pages, dashboards, CRMs, audit logs.
Deploy status, posted back to GitHub, GitLab, and Bitbucket
The new deployment notifications integration closes the most common visibility gap of all: a pull request shows the diff, the conversation, and the test results — but says nothing about whether the merge actually shipped, where it shipped to, or when. We covered why that gap matters in a comparison of how developers track pull requests, and the same logic applies after merge: reviewers shouldn't have to guess what happened to their code.
Once enabled, every DeployHQ deploy reports back to the originating Git provider. On GitHub, deploys appear under the Deployments tab and as commit statuses on PRs. On GitLab, they show up in the Environments view and on the merge request widget. On Bitbucket, they populate the native Deployments panel. You can map projects to environments — production, staging, QA, preview — so reviewers can see which commit landed where without leaving the code review.
There's no separate auth dance: the integration reuses the repository connection you already configured, and the audit trail of every deploy lives where the rest of your code history lives.
A Linear Release for every deploy, automatically
Release tracking is one of those tasks that sits between engineering and product, gets assigned to nobody, and quietly atrophies. The Linear integration takes it off the backlog: every time DeployHQ finishes a deploy, a Linear Release lands in your chosen pipeline — already linked to the issues that shipped, based on the issue IDs in the commit messages between this deploy and the last one.
The integration takes a single Linear API key and lets you route different environments to different release pipelines. Production deploys can populate your customer-visible release pipeline; staging deploys can populate an internal one. The integration only creates Releases — it doesn't move issues between states, so it composes cleanly with whatever workflow automation you already have. If you've thought about the difference between continuous delivery and continuous deployment, this is the seam where the two meet — automatic Releases let you keep continuous-delivery discipline without manual bookkeeping.
Card-formatted alerts in Google Chat spaces
For teams running on Google Workspace, the Google Chat integration drops deploy notifications straight into your existing spaces as native cards. Project name, branch, environment, deployer, and status are all visible at a glance — no plain-text wall.
Different projects can route to different spaces, or one project can broadcast to several. Useful pattern: send infra deploys to a quiet deploys-firehose
space and customer-facing app deploys to your main engineering space, so the noise lives somewhere you can mute and the signal stays where people are paying attention. This is the same pattern we recommended when we enhanced our Slack notifications, now extended to Google Workspace teams.
Telegram alerts for the on-call rotation
Slack and Discord aren't the right fit for everyone. International teams, contractor pools, and on-call rotations often live in Telegram, where notifications hit personal devices reliably without a paid seat or a workspace invite. (For teams already on Discord or Microsoft Teams, we have a separate guide for routing deployment notifications there.)
The new integration uses the Telegram Bot API to push deploy alerts to any chat, group, or channel. Setup is three steps: create a bot through @BotFather, add it to your destination, and paste the token plus chat ID into DeployHQ. There's no Telegram-side server to host — the bot infrastructure is Telegram's. A common deployment pattern: a private channel for production alerts that on-call engineers subscribe to, plus a group chat for the broader team.
Signed HTTP webhooks for everything else
Pre-built integrations cover the common destinations, but there's always a long tail: a customer-facing status page, an internal compliance log, a CRM that needs to know when a customer's tenant deployed, a custom dashboard the platform team built last quarter. The HTTP webhook integration handles those.
Every deploy event — start, success, failure — fires a signed POST to whatever URL you configure. Each request includes an X-DeployHQ-Signature header containing an HMAC-SHA256 of the raw body, keyed by your shared secret, so the receiving service can verify the request actually came from DeployHQ and wasn't replayed or forged. That matters as soon as the receiving endpoint is publicly reachable, which most webhook endpoints are.
If you'd rather poll than receive, the same data is available through the DeployHQ API for scripted deployment workflows. Common destinations we've seen people wire up: Statuspage and Atlassian Status, Datadog events, internal Postgres audit tables, ServiceNow tickets, custom Slack apps with richer formatting than the stock connector, and customer-success tools that surface deploy timing during support conversations.
Where this fits
Each of these reuses your existing DeployHQ project configuration — the same Git deployment automation you already have running picks up the new notification target on its next run. Multiple integrations can run in parallel: a single deploy can post a commit status to GitHub, create a Linear Release, drop a card into Google Chat, ping a Telegram channel, and fire a webhook to your status page.
For a wider tour of what plugs into DeployHQ — error trackers, monitoring tools, project management — the DeployHQ integrations roundup covers the broader picture, and the integrations index lists every pre-built connector. If your destination isn't there, the signed webhook covers it.
If you're not deploying with DeployHQ yet, start a free trial and wire up your first integration in the dashboard — most teams have deploy notifications flowing inside ten minutes.
Got questions or a destination you'd like us to integrate with natively? Reach us at support@deployhq.com or @deployhq on X.