Wire DeployHQ Into
Anything You Build
Receive a signed HTTP POST whenever a deploy starts, succeeds, or fails. Build custom dashboards, light up status pages, ping your CRM — anything you can write code for.
Last updated on 8th May 2026
Off-The-Shelf Integrations Don't Cover Everything
Your in-house dashboard, status page, or CRM doesn't have a Slack-style listing. So how does it know when you ship?
No integration listing covers every tool you build internally — yet those are the ones that need deploy data the most.
One Webhook, Any Endpoint
DeployHQ POSTs a signed JSON payload to any URL you give it. Receive it on a Lambda, a Rails route, a Cloudflare Worker — wherever your code lives.
How It Works
Plug in a URL and a secret — that's the whole setup.
Build an Endpoint
Write a route in your application that accepts POST requests and verifies the signature header against a shared secret.
Add to DeployHQ
Drop the URL and secret into your DeployHQ project's HTTP integration. Pick which deploy events should fire the webhook.
Process the Payload
Verify the HMAC, parse the JSON, and do whatever your business logic needs — update a row, fan out to other systems, anything.
Why Use HTTP Webhooks
When the integration list doesn't cover your case, the HTTP webhook does.
Real-Time Delivery
Each deploy event POSTs immediately. Your endpoint receives JSON within milliseconds of the event firing.
Signed Payloads
Every request includes an HMAC signature. Verify the body against your shared secret to be certain it's from DeployHQ.
Structured JSON
Stable JSON schema with project, environment, status, revision, and timestamps. Sample payloads live in the docs for testing.
Build Anything
Update a custom dashboard, broadcast to customer-facing status pages, write to an audit log, kick off downstream workflows — your call.
Wire up your endpoint in minutes
Build the Receiver
Stand up a POST endpoint that reads the body, verifies the X-DeployHQ-Signature header, and returns 200 quickly.
Configure DeployHQ
Add an HTTP integration with your URL and a shared secret. Pick which events (start, success, failure) should fire it.
Trigger and Confirm
Run a deployment. Check your endpoint's logs to confirm the request landed, the signature verified, and your handler did its thing.
Frequently Asked Questions
What does the HTTP integration send?
DeployHQ POSTs a JSON payload containing the project, environment, deployment status (started, completed, or failed), revision, branch, timestamps, and a few related fields. The body is signed with HMAC using a shared secret so you can verify it really came from DeployHQ. A sample payload lives in the support docs.
How do I verify the signature?
Each request carries an X-DeployHQ-Signature header containing an HMAC-SHA256 of the raw request body, keyed by the secret you set when configuring the integration. Compute the HMAC of the body using the same secret on your side and compare — examples in Ruby, Python, Node, and PHP are in the docs.
What happens if my endpoint is down?
DeployHQ retries failed deliveries with exponential backoff. A deployment never blocks on a webhook — your release ships either way — but the integration logs failed deliveries so you can investigate or replay them when the receiver comes back online.
Ready to wire deploys into your own systems?
Stand up an HTTP webhook and let DeployHQ feed your custom dashboards, status pages, and internal tooling automatically.
10-day free trial • No setup fees • Cancel anytime
Explore More Features
Discover all the tools that make DeployHQ the easiest way to deploy your code.
Get started today for just $9/month
That's unlimited deployments and 3 projects.