Loading…
For any client ask, find the answer fast: can we, can't we, and how.
| Action | Hyros API | CRM Trigger | Real-time | Identity key | Attribution |
|---|---|---|---|---|---|
| Create lead | Yes | Yes | Yes | email/phone | High |
| Update lead | Yes | Yes | Yes | email/phone | Medium |
| Add tag (append) | Yes | Yes | Yes | email/phone | Low |
| Send lead stage | Yes | Yes | Yes | email/phone | Medium |
| Track call | Yes | Yes | Yes | email/phone | High |
| Track sale | Yes | Yes | Yes | email/phone | Critical |
| Subscriptions | Yes | Partial | Yes | email/phone | High |
| Read / list records | Yes | — | Yes | filters | None |
Partialmeans it's doable but with a caveat (e.g. tag append-vs-replace behavior, or only via a CRM trigger rather than a direct API field).
You can read data outof Hyros via the GET endpoints (leads, sales, calls, subscriptions, tags) — that's why "Read / list records" is Yes. For real-time push of events to another system, use the four outbound webhooks (sale.attributed, lead.opted.in, lead.origin.assigned, call.attributed).