operate
Slack & Webhook Alerts
The Deploy Events You Choose, Sent Where Your Team Already Works.
Updated
Share This With A Builder Who Needs It
Know someone shipping AI-written code? Send them this walkthrough.
At a glance
Send failed deploys, blocked deploys, rollbacks and new critical findings to a Slack channel or your own signed webhook — chosen event by event.
- Choose Event By Event
- Slack Or Your Own System
- Signed, So You Can Trust It
Why it matters
An alert that lands in an inbox nobody watches is the same as no alert. The events that matter should reach the channel or on-call tool your team already uses.
Owners and Admins add destinations in Settings and choose events one by one: failed or blocked deploys, rollbacks, reverted staged rollouts, new critical findings, private pages left open, decoy rows used, and packages newly exploited. Slack gets an incoming-webhook post. Your own endpoint gets a signed request it can verify. Send a test before you rely on it. A destination that keeps failing is switched off and says so, rather than failing silently forever.
What you get
Choose Event By Event
Tick only what each destination should hear: a failed deploy, a deploy blocked by a security check, a rollback, a reverted staged rollout, new critical findings, a private page left open, a decoy row being used, or a package you use being newly exploited.
Slack Or Your Own System
Paste a Slack incoming webhook to post to a channel, or point ZipLoom at your own endpoint to feed an on-call tool, a ticket queue or anything else.
Signed, So You Can Trust It
Requests to your own webhook carry a ZipLoom-Signature header made with a secret only you and ZipLoom hold, so your system can reject anything that did not come from ZipLoom.
Test Before You Rely On It
Send a test from the card and see it arrive before a real incident depends on it.
How It Works
- 1
An Owner or Admin opens Settings and adds a destination under Alerts.
- 2
Choose Slack or your own webhook, name it, and tick the events it should receive.
- 3
For your own webhook, copy the signing secret shown once and store it.
- 4
Send a test. From then on, each chosen event is delivered as it happens.
What this check inspects
Deploys that fail, are blocked by a check, roll back or have a staged rollout reverted.
New critical findings, private pages reachable without signing in, decoy rows being used, and packages newly listed as exploited.
What it means when this fails
A destination that keeps failing is switched off and the card says so, rather than failing silently forever. Webhook addresses on private or internal networks are refused.
What it does not do
Alerts name the event and the project and link back to ZipLoom. They never include code or finding details.
Webhook addresses on private or internal networks are refused.
Questions
- Does an alert include my code or finding details?
- No. An alert names the event and the project and links back to ZipLoom, where you see the details after signing in.
- Which plans include alerts?
- Every plan. Adding or changing a destination needs an Owner or Admin.
Related features
Private Pages Check & Decoy Rows
Know When A Private Page Is Open, And When Someone Is Inside.
Learn moreSelf-Healing Deploys
Checks Every 5 To 15 Minutes — Goes Dark, The Last Good Deploy Is Restored Automatically On A Managed Host.
Learn moreStaged / Canary Rollout
1% → 10% → 50% → 100% With An Automatic Error Gate — On Google Cloud Run.
Learn more