webhooks

Send campaign events wherever you need them

Trigger a webhook whenever a lead is created or added, replies, or bounces, or when an email sends or gets opened. Configure it per campaign, and verify every payload came from Sendbox using a secret-key signature.

Set up in under 15 minutes
sendbox / outreach / webhooks

Webhooks

Outreach

Live

Point it at an endpoint

Send webhooks to any HTTP endpoint, your CRM, Zapier, Make, n8n, or something you built yourself. Each campaign carries its own webhook configuration.

  • Configured per campaign
  • Signed payloads
  • Six event types
  • Plain HTTP delivery
Webhooks you can verify, not just receive
webhook features

Live events, no polling required

Start sending

Configured per campaign

Each campaign keeps its own webhook endpoints and event subscriptions, so things stay organized.

Signed payloads

Every webhook ships with a signature generated from your secret key, letting you confirm it genuinely came from Sendbox.

6

Six event types

lead.created, lead.added, lead.replied, lead.bounced, email.sent, and email.opened, subscribe to exactly the ones you need.

Plain HTTP delivery

Webhooks reach any HTTP endpoint, which means they work with CRMs, automation tools, and backends you built yourself.

integration flow

The moment it happens, your stack knows

Start sending
  1. Step 1

    Point it at an endpoint

    Send webhooks to any HTTP endpoint, your CRM, Zapier, Make, n8n, or something you built yourself. Each campaign carries its own webhook configuration.

  2. Step 2

    Choose what fires it

    Subscribe to whichever events matter: lead.created, lead.added, lead.replied, lead.bounced, email.sent, or email.opened.

  3. Step 3

    Confirm it's really Sendbox

    Each payload arrives with a signature you can check against your secret key, so you know the request is genuine.

Where it fits

CRM sync

Push replies and bounces into your CRM the instant they happen, so your pipeline is never out of date.

Building your own automations

Kick off n8n or Make workflows whenever a lead replies or bounces, build whatever post-engagement automation your process needs.

Feeding a data warehouse

Stream campaign events straight into your warehouse for reporting or attribution work you'd rather run yourself.

vs polling

Delivered instantly, never batched

Why teams switch

Webhooks you can verify, not just receive

Sendbox sets webhooks up per campaign instead of one blanket setting for the whole account. Each endpoint gets its own secret key so you can check a payload's signature before trusting it, across six event types that track a lead from first send to final outcome.

  • Beats Smartlead
  • Beats Lemlist
6

Six events, the full lifecycle covered

Subscribe to lead.created, lead.added, lead.replied, lead.bounced, email.sent, and email.opened, configured however you like per campaign.

  • Every payload carries a signature from your secret key so you can verify it on your end.
faq

Got questions? We've got answers.

Six: lead.created, lead.added, lead.replied, lead.bounced, email.sent, and email.opened, each configurable independently per campaign.

Ready to land in primary?

Get your own isolated Sendbox setup running and start sending inside 15 minutes.

Every plan includes a dedicated IP. Cancel whenever you want.