Skip to content
ReachPods

Integrations

CRM integrations and webhooks to connect your stack

Your outreach shouldn’t be a silo. Sync contacts, activities and deals to HubSpot, Salesforce, Pipedrive or GoHighLevel, and send signed webhooks on every reply, open, click and opportunity to anything else — Zapier, your data warehouse, your own code.

An event in ReachPods — a reply, an opportunity won — fans out to a signed outbound webhook and to connected CRMs like HubSpot, Salesforce, Pipedrive and GoHighLevel.EVENTlead.interestedSofia B. · Northwindone event · many destinationsLIVEYOUR ENDPOINTPOST /oir/hook200X-OIR-Signature ✓CONNECTED CRMsHHubSpotSSalesforcePPipedriveGGoHighLevel
HubSpot, Salesforce, Pipedrive, GHL
4 CRMs
HMAC-SHA256 webhooks
Signed
to subscribe to
14 events
6 attempts with backoff
Retried

Overview

One event, every destination

When a lead replies, opens, clicks or becomes an opportunity, something in your stack usually needs to know — your CRM, your reporting, a Slack channel, an automation in Zapier. Copying that by hand is how data goes stale and deals get double-worked.

Integrations send those moments out the instant they happen. Native CRM sync keeps HubSpot, Salesforce, Pipedrive or GoHighLevel up to date with your contacts, activities and deals; outbound webhooks push the raw events, signed, to any URL you own. Same events, as many destinations as you need.

Native CRM sync

Keep your CRM up to date on its own

Connect HubSpot, Salesforce, Pipedrive or GoHighLevel and ReachPods keeps the records in step. It finds or creates the contact, fills in the blanks it has, logs sent emails and replies as activities on the person, and pushes opportunities as deals — creating them and moving their stage as they move on your board.

You decide how eager it is: create contacts in the CRM once they’re emailed, once they reply, or only when they’re interested. Your pipeline stages map to the CRM’s own stages, so a deal that reaches “Proposal” here lands in the right stage there.

  • HubSpot, Salesforce, Pipedrive, GoHighLevel
  • Contacts created or updated
  • Sent emails and replies logged as activities
  • Opportunities pushed and moved as deals
  • Your stages mapped to theirs
  • Create contacts when emailed, replied or interested
CRM sync creates or updates the contact, logs sent emails and replies as activities, and pushes opportunities as deals, mapping your stages to the CRM's.IN REACHPODSSBSofia B.[email protected]Email sentReply · interestedOpportunity · $20kHIN HUBSPOTCONTACTSofia B. · NorthwindACTIVITY• Email sent• Reply loggedDEAL$20,000stage: Qualified →mapped to “SQL”

Webhooks

Signed events to any URL you own

Subscribe a URL to the events you care about and every one is POSTed to it as JSON, carrying the lead and the campaign it belongs to. Each delivery is signed with your subscription’s secret as an X-OIR-Signature header (an HMAC-SHA256 over the timestamp and body), so your endpoint can verify it really came from us.

Deliveries are reliable: a non-2xx answer is retried with exponential backoff — six attempts over about thirty minutes — and the delivery id stays the same across retries so your receiver can dedupe. A deliveries log shows every attempt, its response and its payload, and you can resend any one by hand.

  • Subscribe any URL
  • HMAC-SHA256 signature per delivery
  • Per-subscription secret
  • Retried 6 times with backoff
  • Stable delivery id for dedupe
  • Full deliveries log with resend
Every subscribed event is POSTed as signed JSON to your URL with an HMAC-SHA256 signature; non-2xx answers are retried with backoff and every attempt is logged.POST /your-endpointX-OIR-Event: lead.interestedX-OIR-Delivery: 3f9c… (stable)X-OIR-Signature: t=…,v1=HMAC{ "event": "lead.interested", "lead": { "name": "Sofia B."…}, "campaign": { "name": "SaaS…"}}verify: sha256(secret, t.body) ✓RETRIESAttempt 1Attempt 2 · +30sAttempt 3 · ok6 attempts over ~30 minDELIVERIES LOGlead.replied · 200email.opened · 200task.created · 200SUBSCRIBE TO WHAT YOU NEEDRepliesOpensClicksBouncesOpportunitiesTasksPer-subscription secret · scope to one campaign or all of them

The events

From first send to closed deal

The same catalogue drives both webhooks and CRM sync: email sent, opened, clicked and bounced; a lead replied, got a category, turned interested or unsubscribed; an opportunity created, moved, won or lost; and a task created or completed. Scope a webhook to one campaign or to the whole workspace.

Because the events carry the lead and campaign, your analytics in a BI tool, your lifecycle automations and your CRM all see the same source of truth — the moment it happens, not the next morning’s export.

  • Email sent, opened, clicked, bounced
  • Replied, categorised, interested, unsubscribed
  • Opportunity created, stage changed, won, lost
  • Task created and completed
  • Scope to one campaign or all
The public event catalogue that drives both webhooks and CRM sync: email sent, opened, clicked and bounced, replies and categories, opportunities and tasks.EVENTS YOU CAN SUBSCRIBE TOlead.repliedA lead replied (any channel)lead.interestedReply categorised interestedemail.openedA lead opened an emailemail.clickedA lead clicked a linkopportunity.wonAn opportunity was wontask.completedA task was completed

How it works

CRM integrations and webhooks: how it works in four steps

  1. 1

    Connect a CRM

    Link HubSpot, Salesforce, Pipedrive or GoHighLevel and choose when contacts are created.

  2. 2

    Map your stages

    Line up your pipeline stages with the CRM’s so deals land in the right place.

  3. 3

    Add a webhook

    Point a URL at the events you want; copy the signing secret to verify deliveries.

  4. 4

    Watch it flow

    Replies, opens, opportunities and tasks sync out live, with a log of every delivery.

Who it’s for

CRM integrations and webhooks: who it’s for

RevOps

Keep the CRM as the source of truth while outreach runs, with activities and deals synced automatically.

Agencies

Push each client’s replies and opportunities straight into the CRM they already use.

Builders

Trigger your own code or a Zapier flow the instant a lead replies, with a signed, retried webhook.

FAQ

CRM integrations and webhooks: questions and answers

Something else on your mind? Get started and try it on your own accounts.

Which CRMs are supported?

HubSpot, Salesforce, Pipedrive and GoHighLevel, with contacts, activities and deals kept in sync.

How are webhooks secured?

Each delivery carries an X-OIR-Signature header — an HMAC-SHA256 of the timestamp and body using your subscription’s secret — so you can verify it.

What happens if my endpoint is down?

The delivery is retried with exponential backoff, six attempts over about thirty minutes, with a stable id so you can dedupe. Every attempt is logged.

Can I use Zapier or n8n?

Yes. Point a webhook at a Zapier or n8n catch hook and build whatever you need on top of the events.

When are contacts created in the CRM?

Your choice per connection: once a lead is emailed, once they reply, or only when they’re interested.

Start your first multichannel campaign today

$39 per connected account, every feature, every channel. Add accounts as you grow.