Slack and Zapier notifications: every audit, where your team already looks
AuditZap now posts to Slack and signed webhooks. Here is what fires, how to set it up in two minutes, and why the emails can finally be switched off.
- Pro and Agency accounts can add Slack and webhook destinations from Settings, Integrations.
- Six events can be routed: audit complete, monitored site changed, critical issues found, fix verified, report ready, audit failed.
- Zapier, Make and n8n work today through their catch-hook triggers. No app to install.
- Webhook deliveries are signed with HMAC-SHA256 and retried three times; a dead endpoint is paused after ten failures and you get one email.
- Once a destination carries the audit-complete event, you can switch that email off. If the destination ever goes away, the email comes back on by itself.
Most of what AuditZap tells you arrives by email. That is fine for the first audit and wrong for the twentieth. A weekly re-audit of five client sites is five emails nobody on the team opens, and the one that mattered, a homepage that lost its H1 after a theme update, sits unread between them.
From today, Pro and Agency accounts can send those events to Slack, or to Zapier, Make, n8n or any endpoint you run, and choose per event whether the email still goes out. It is in Settings under a new Integrations tab, and it takes about two minutes to wire up.
What fires
Six events can be routed, and each destination picks its own set:
- Audit complete. Every audit you or your API start, with the score, the change against the previous run of that site, and the top issues.
- Monitored site changed. The weekly or monthly re-audit, with what is new, what got fixed and what is still open.
- Critical issues found. When a run finds failures in the Critical category.
- Fix verified. When you press "I've fixed this, check it" and the check passes.
- Report ready. When a paid one-off report has been delivered.
- Audit failed. When a run could not complete, with the reason, so a firewall block on a client site does not go unnoticed until Monday.
Slack gets a short message: host and score, the delta in words, up to three top issues, and one button to the report. Webhooks get a JSON body with the same facts plus the full change list, in a shape that only ever gains fields. Nothing here surfaces an internal category name; the AI Visibility checks arrive labelled as such.
Slack
Create an incoming webhook in your Slack workspace (Slack's own guide takes a minute), paste the hooks.slack.com URL into Settings, Integrations, Slack, tick the events you want, and press Send test. A sample audit lands in the channel within a few seconds. That is the whole setup. An agency can point one destination at a client channel and another at an internal one, each with its own events.
Zapier, Make, n8n and your own code
A webhook destination is any HTTPS URL. In Zapier, start a Zap with the "Webhooks by Zapier" trigger, choose Catch Hook, copy the URL it gives you, and paste it in as a webhook destination. Press Send test, and Zapier sees a real sample to build the rest of the Zap from: a row in a sheet, a card in Trello, a message in Teams, whatever your stack is. Make and n8n work the same way through their webhook triggers.
If you write your own receiver, every delivery carries an X-AuditZap-Signature header: an HMAC-SHA256 over the timestamp and the raw body, with a secret we show you once when you create the destination. The webhook documentation has the payload, the headers, and verification samples in Node and Python.
Reliable, and safe when it is not
Deliveries go out from a queue, not from the page you were looking at, and a failed delivery is retried three times with increasing waits. We never follow redirects, because the destination chooses where a redirect goes and we are not going to follow it somewhere private. If an endpoint fails ten times in a row we pause the destination and send you one email saying so; switch it back on from Settings when it is fixed, or press Send test, which re-enables it for you.
Every URL is checked when you save it and again when we send: public address, HTTPS only, and for Slack specifically the real hooks.slack.com host, not a lookalike.
Turning the emails off
This is the part that makes the feature worth having. The Notifications tab is now a grid: the six events down the side, Email, Slack and Webhook across the top. Once an enabled destination carries the audit-complete event, the switch to turn off that email unlocks. The same goes for the monitored-site and critical-issue emails.
There is one rule behind it, and it is deliberately strict: nobody can end up with an audit announced nowhere. If you delete or pause the last destination that carries audit complete, if we pause it for failures, or if your plan lapses, the email switches itself back on. You will never discover in week three that results stopped arriving anywhere.
Who this is for
If you are a solo owner with one site, the completion email is probably still the right channel and you can ignore all of this. If you look after several sites, or anyone else on your team needs to see results, Slack is the difference between a report that gets read and one that does not. If you are an agency already using the REST API to run audits, webhooks close the loop: start the audit from your system and have the result pushed back into it.
Slack and Zapier notifications are part of the Pro plan. See pricing for what else Pro includes.
What is next
Three things did not make this round and are on the list, roughly in this order: an "Add to Slack" button so you do not have to create the webhook yourself, a listed Zapier app with named triggers, and per-site routing so an agency can send each client's events to a different place without filtering downstream. If one of those would change how you use AuditZap, reply to any of our emails and say so; that is how the order gets decided.
Get one AI fix instruction tailored to your platform, free. 3 audits a month, no card. Pro unlocks fixes for every issue.