Webhooks in Outboundry

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


What is a Webhook?

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


Supported Events

Outboundry currently supports webhook notifications for both LinkedIn and Email activities.

LinkedIn Events

Event

Description

invite-sent

Connection request has been sent

invite-accepted

Prospect accepted your connection request

message-sent

Direct message sent after connection

message-replied

Prospect replied to your message

inmail-sent

InMail sent without connection

inmail-replied

Prospect replied to your InMail


Email Events

Event

Description

email-sent

Outbound email successfully delivered

email-opened

Recipient opened the email

email-clicked

Recipient clicked a link

email-replied

Recipient replied to the email


How Webhooks Work

  1. You configure a webhook URL in Outboundry

  2. Select the events you want to subscribe to

  3. When an event occurs, Outboundry sends a POST request to your endpoint

  4. Your system processes the data and triggers actions


Setting Up a Webhook

Follow these steps to create a webhook:

  1. Go to Settings → Webhooks

  2. Click Add Webhook

  3. Enter your Webhook URL

  4. Select the events you want to receive

  5. 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


Webhook Payload

Each webhook contains structured JSON data describing the event.

👉 A detailed list of payload structures for each event is available here


Example Use Cases

Here’s how teams typically use webhooks:

1. CRM Sync

  • Push leads into HubSpot/Salesforce when:

    • Invite accepted

    • Email replied

2. Real-Time Alerts

  • Send Slack notifications when:

    • High-intent lead replies

    • Link is clicked

3. Lead Scoring

  • Increase score when:

    • Email opened or clicked

    • LinkedIn message replied

4. Workflow Automation

  • Trigger sequences in tools like Zapier, Make, or custom backend systems


Best Practices

  • ✅ 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


Error Handling & Retries

If your endpoint fails to respond successfully:

  • Outboundry may retry the webhook delivery

  • Ensure your system can safely handle duplicate requests


Security Considerations

To keep your data secure:

  • Use HTTPS endpoints only

  • Validate incoming requests

  • Avoid exposing sensitive endpoints publicly without verification


Limitations (if applicable — adjust based on your product)

  • Historical events are not sent (only real-time)

  • Webhook delivery depends on endpoint availability

  • Certain events (like opens) may be affected by tracking limitations


Need Help?

If you need assistance setting up webhooks or debugging issues, reach out to our support team.