Webhooks allow you to receive real-time notifications when key activities happen inside Outboundry. Instead of manually checking updates, you can automatically send event data to your own systems, CRMs, or workflows.
This makes it easy to:
Trigger automations
Sync data with external tools
Build custom workflows
Monitor campaign performance in real-time
A webhook is an HTTP callback that sends a POST request to your configured URL whenever a specific event occurs.
For example:
A prospect accepts your LinkedIn invite → notify your CRM
A lead replies to an email → trigger a Slack alert
A link is clicked → update lead scoring system
Outboundry currently supports webhook notifications for both LinkedIn and Email activities.
Event Description | |
| Connection request has been sent |
| Prospect accepted your connection request |
| Direct message sent after connection |
| Prospect replied to your message |
| InMail sent without connection |
| Prospect replied to your InMail |
Event Description | |
| Outbound email successfully delivered |
| Recipient opened the email |
| Recipient clicked a link |
| Recipient replied to the email |
You configure a webhook URL in Outboundry
Select the events you want to subscribe to
When an event occurs, Outboundry sends a POST request to your endpoint
Your system processes the data and triggers actions
Follow these steps to create a webhook:
Go to Settings → Webhooks
Click Add Webhook
Enter your Webhook URL
Select the events you want to receive
Save the webhook
Once saved, Outboundry will start sending event notifications instantly. While creating webhook, you can click Test Data button to send sample payload data to added endpoint
Each webhook contains structured JSON data describing the event.
👉 A detailed list of payload structures for each event is available here
Here’s how teams typically use webhooks:
Push leads into HubSpot/Salesforce when:
Invite accepted
Email replied
Send Slack notifications when:
High-intent lead replies
Link is clicked
Increase score when:
Email opened or clicked
LinkedIn message replied
Trigger sequences in tools like Zapier, Make, or custom backend systems
✅ Ensure your endpoint responds with 200 OK quickly
✅ Handle duplicate events (idempotency recommended)
✅ Log incoming webhook requests for debugging
✅ Secure your endpoint (IP allowlisting or signature validation if supported)
✅ Retry logic: be prepared for re-delivery if your endpoint fails
If your endpoint fails to respond successfully:
Outboundry may retry the webhook delivery
Ensure your system can safely handle duplicate requests
To keep your data secure:
Use HTTPS endpoints only
Validate incoming requests
Avoid exposing sensitive endpoints publicly without verification
Historical events are not sent (only real-time)
Webhook delivery depends on endpoint availability
Certain events (like opens) may be affected by tracking limitations
If you need assistance setting up webhooks or debugging issues, reach out to our support team.
