PlusVibe Webhooks#
Webhooks allow external systems to receive real-time event notifications from PlusVibe. You can use webhooks to integrate PlusVibe with your own applications, CRMs, or automation tools like Zapier and Make.com.Supported Webhook Event Types#
First Email Replies (FIRST_EMAIL_REPLIES)
Triggered whenever a lead replies for the first time (excluding Out of Office and Automatic Replies).
All Email Replies (ALL_EMAIL_REPLIES)
Triggered whenever a lead replies (including the first reply and all subsequent replies).
All Positive Replies (ALL_POSITIVE_REPLIES)
Triggered whenever a lead replies and is detected as having a positive sentiment (includes both first and subsequent replies).
Campaign Emails Sent (EMAIL_SENT)
Triggered whenever a campaign email is sent.
**All Bounced Emails ** (BOUNCED_EMAIL)
Triggered whenever a email is bounced
Unibox Emails Sent (UNIBOX_EMAIL_SENT)
Triggered whenever an email is sent from the Unibox: manual reply or compose, scheduled messages (at actual send time), AI-triggered replies, and automated follow-ups. Forwarded messages are excluded.
LEAD_MARKED_AS_{{LABELNAME}}
Triggered when a label is applied to a lead, either by our AI or manually by a user inside the app.
Note: Label Name has to be in all uppercase.
Webhook_event Example:LEAD_MARKED_AS_INTERESTED
LEAD_MARKED_AS_NOT_INTERESTED
System Alert (SYSTEM_ALERT)
Triggered when something in the workspace needs attention — an email account disconnecting, forwarded replies bouncing, billing problems and more. When subscribing you also choose which alerts to receive; see the "Webhooks - Payload - System Alert" page for details and samples.
Webhook Secret (optional)#
The secret is entirely optional — skip it unless you specifically need to verify that requests come from PlusVibe. Webhooks work exactly the same without one (e.g. Zapier and Make.com don't need it). Leave the secret field empty and ignore this section.
1.
We compute an HMAC-SHA256 of the raw JSON request body, using your secret as the key.
2.
The hex-encoded result is sent in the Signature header of the POST request.
3.
On your server, compute the same HMAC-SHA256 over the raw request body with your secret and compare it to the Signature header (use a constant-time comparison). If they don't match, reject the request.
Signature = hex( HMAC_SHA256( key: your_secret, message: raw_request_body ) )Important: always hash the raw request body exactly as received, before any JSON parsing or re-serialization — re-stringifying the parsed JSON can reorder or reformat it and produce a different signature.Check your implementation — run your verification code on this example. With the secret my_webhook_secret and this exact raw body:{"webhook_event":"SYSTEM_ALERT","alert":"EMAIL_ACCOUNT_DISCONNECTED"}
a927cde9781124cf8e28e8e5886e4dff6bf7c792877211fd2a3d6e9d0cc95097
Testing with Sample Payloads#
From the webhook settings page in the web app you can send a sample payload for any event type you've subscribed to. This delivers a realistic test payload to your webhook URL — signed with your secret if one is set — so you can build and test your handler end to end before real events occur. For the System Alert event, one sample delivery is sent per alert type you can receive.How to Integrate PlusVibe Webhooks with Zapier or Make.com#
1.
Create a Webhook Trigger in Zapier or MakeIn Zapier, create a new Zap and choose Webhooks by Zapier as the trigger. Select Catch Hook.
In Make.com, create a new Scenario and add the Webhooks module. Select Custom Webhook.
Both platforms will give you a unique webhook URL.
2.
Add the Webhook URL to PlusVibePaste your webhook URL into the appropriate field.
Choose the event types you want to subscribe to, and save your changes.
3.
When the selected event occurs in PlusVibe, a POST request will be sent to your webhook URL.
Zapier or Make.com will receive the data and forward it to your connected system.
