How it connects
Revnox sends an event to an address you give it, the moment something happens. Zapier and Make both give you such an address, so no special app is needed.
In Zapier, start a Zap with Webhooks by Zapier, choose Catch Hook and copy the address. In Make, start a scenario with Webhooks, choose Custom webhook and copy the address.
In Revnox, an owner or admin opens Settings > Webhooks, adds an endpoint with that address and picks the events.
Press Send test event. Zapier or Make now knows what the data looks like, and you can map it into the next step.The events
- account.hot: an account turned hot. It carries the account's name, domain, industry and score, and the signal behind it.
- signal.created: a new signal was found for an account, with its category, title, link and when it was detected.
- reply.received: someone replied to a campaign message, with the contact and the campaign.
Checking that it came from Revnox
Every event carries a Revnox-Signature header: an HMAC-SHA256 of the Revnox-Timestamp header, a full stop and the raw body, keyed by the endpoint's signing secret. A step that checks it can refuse anything else. The Revnox-Event-Id header lets a receiver ignore a repeat.
When the receiver is down
A failed delivery is tried again, over about eight and a half hours. The webhooks screen shows every attempt and its answer.