Skip to main content
Every webhook delivery shares an envelope:
id is unique per delivery and stable across retries — dedupe on it if you’re persisting events.

Event catalog

Fires when the recipient opens an email Vibefollow sent on your behalf.
Tracking pixels are stripped if the recipient’s mail client blocks them — do not assume a missing open means the email wasn’t read.
TypeScript shape
Example payload
Fires when the recipient clicks any tracked link in the email. One event per click — the same recipient clicking three links produces three events.TypeScript shape
Example payload
Fires when Postmark reports a bounce or spam complaint. bounceType distinguishes the kind so you can decide whether to suppress the address.TypeScript shape
Bounce type guide
Fires when the recipient replies to a Vibefollow-sent email. The full plain-text body is included, along with a tone classification used internally to auto-pause sends to users who reply negatively.TypeScript shape
Tone classifications
Vibefollow does not auto-reply on your behalf in v1. Inbound replies route to your project’s reply-to address; the webhook is a copy for your systems to react to.
Fires when the recipient unsubscribes — through the one-click List-Unsubscribe header (RFC 8058), through a reply that scored as unsubscribe_request, or through a manual flag in the dashboard.TypeScript shape
Source values
Unsubscribed users are excluded from every future trigger evaluation. You don’t need to do anything — this webhook is informational so your CRM can mirror the state.