Webhooks vs the API
The API pulls data when you ask. Webhooks push data the moment something happens. Real-time systems need both: webhooks for immediacy, API for full state.
Event categories
The events worth wiring up mirror the prospect lifecycle:
- Replied — the highest-value event; route to Slack and the account owner.
- Opted out — propagate the unsubscribe everywhere it matters.
- Bounced — clean the address in downstream systems too.
- Auto-reply — schedule follow-up for when the prospect returns.
- Completed with no reply — trigger post-sequence workflow.
Building a receiver
- Expose an HTTPS endpoint.
- Register it via the Integrations page / API documentation.
- Acknowledge receipt fast (2xx) and queue processing.
- Handle duplicates idempotently — retries are part of the deal.
- Log raw payloads; you'll need them the first time an event "didn't arrive".
[CONFIRM: exact event names, payload schema, and signature/verification scheme from the current API docs]