04 · Webhooks
Two directions of webhooks, the four outbound events Hyros emits, and the analyst/dev boundary.
Two directions — don't confuse them
There are two directions to keep straight. (1) INBOUND — sending data INTO Hyros: Zapier and Make have their own native Hyros connector, so you pick Hyros as the app and choose an action (Create Lead, Track Sale, etc.). You do NOT create or paste a webhook URL, and Hyros does not hand one out — the connector does the same job as the API, no code. (2) OUTBOUND — Hyros emits events to a URL you configure, so another system can react. "Getting data out" of Hyros means consuming an outbound event, not calling the read API.
The four outbound events Hyros emits
Hyros dispatches four webhook events: sale.attributed (a sale was attributed to a lead), lead.opted.in (a lead opted in), lead.origin.assigned (a lead was linked as the origin of another), and call.attributed (a call was attributed). Each payload carries an eventId for de-duplication plus the lead, attribution chain, and entity details.
The analyst / dev boundary
Analysts scope and configure the integration — they decide the event, the destination, and the field mapping (e.g. in the Zapier/Make Hyros connector). Developers build the receiver that accepts an OUTBOUND payload. Analysts do NOT build receivers; knowing where that line is keeps requests realistic.