Zinn® Ads can send its events to your own webhook endpoints, so Zapier, Make or your own system can act on them the moment they happen. The events are ads.finding.opened, ads.change.applied, ads.alert.started.
Set it up
- In the dashboard open Notification channels and add a webhook endpoint. It must be an HTTPS address. We create a signing secret for it and show it to you once.
- Verify the endpoint: we send it one test request, and it must answer with a 2xx status.
- Open Zinn® Ads, find Webhooks for Zapier, Make and your own systems, tick the events that endpoint should receive and choose Save events. Send a test sends one example.
What arrives
Every delivery is a JSON POST. The headers X-Zinn-Event (the event name) and X-Zinn-Delivery (one id per delivery: drop a delivery you have already handled) come with it, and so does X-Zinn-Signature: sha256=<hex>, an HMAC-SHA256 of <X-Zinn-Timestamp>.<raw body> made with your endpoint's secret. Check the signature, and reject an old timestamp, before you trust the body. The shape of each event is published in our OpenAPI spec under webhooks.
When your endpoint is down
A failed delivery is retried 5 more times, after 1, 5, 25, 125, 625 minutes, and each try is listed in the endpoint's delivery log. Nothing goes to an endpoint that is not verified, and an empty set of events turns Zinn® Ads off for that endpoint.
Step-by-step guide
Control Zinn® Ads from MCP and AI assistants on zinnads.com walks through it with screenshots of the real screens. Every Zinn® Ads guide: zinnads.com/kb.