Skip to content
Business productivity ⇄ CRM

Resend to Salesforce integration — real-time, two-way sync

Keep Resend and Salesforce in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Resend and Salesforce

Sync what happens in Resend with the customer records in Salesforce, in real time and in both directions.

The CRM is supposed to be the record of every customer relationship, but customer-relevant information also accumulates in the other tools a team runs. Whatever Resend holds or produces that touches a customer, whether conversations, payments, replies, enriched data, or notes, the CRM only benefits if it arrives without someone copying it over.

Stacksync connects Domains, Email events, API keys, Emails in Resend to Contacts, Leads, Opportunities, Cases in Salesforce with bi-directional, real-time sync. Activity and record changes in Resend update the matching contact or account in Salesforce, and CRM data flows the other way wherever Resend can store and use it.

Common use cases

  • 01 Sync CRM contact segments into Resend Audiences so lifecycle broadcasts target current data.
  • 02 Write delivery, bounce, and complaint events back to the CRM or a Postgres table for deliverability reporting.
  • 03 Trigger provisioning or billing changes in an operational database when an Opportunity moves to closed-won.
  • 04 Consolidate multiple Salesforce orgs into a single database for cross-org reporting after an acquisition.

Common sync patterns

Where Resend can store CRM context: fields kept current

Owner, lifecycle stage, or account details from Salesforce sync into Resend, so people working there have the context without switching tools.

Where Resend handles support or shared inboxes

Tickets and conversations attach to the right contact and account in Salesforce, so sales sees open issues before the next call.

Where Resend runs outreach

Prospects, sends, and replies sync into Salesforce, keeping lead status current without manual imports.

What you can sync between Resend and Salesforce

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Resend objects Salesforce objects How this pairing syncs
Contacts Recipient records with email, name, and subscription state, synced from CRMs or databases. Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Audiences Named contact lists that broadcasts target; typically mirrored from CRM segments. Campaigns Marketing membership data; read out for attribution analysis in the warehouse. Audiences is specific to Resend and Campaigns to Salesforce — each maps to any object or custom field on the other side.
Broadcasts One-to-many campaign sends addressed to an audience. Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. Broadcasts is specific to Resend and Tasks and Events to Salesforce — each maps to any object or custom field on the other side.
Domains Verified sending domains with DNS and DKIM status. Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. Domains is specific to Resend and Products and Price Books to Salesforce — each maps to any object or custom field on the other side.
Email events Delivered, bounced, complained, opened, and clicked events emitted via webhooks and written back to source systems. Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. Email events is specific to Resend and Custom Objects to Salesforce — each maps to any object or custom field on the other side.
API keys Scoped credentials managed per environment for send and read access. Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. API keys is specific to Resend and Accounts to Salesforce — each maps to any object or custom field on the other side.

How changes propagate between Resend and Salesforce

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Resend Salesforce Sub-second propagation

DetectionResend notifies Stacksync of record changes through webhook events. Webhooks for email lifecycle events.

DeliveryEach detected change is written to Salesforce through its API, with automatic retries and rate-limit backoff.

Salesforce Resend Sub-second propagation

DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).

DeliveryEach detected change is written to Resend through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Salesforce: Daily API request allocations vary by edition and license count.
What ships with Resend ⇄ Salesforce

Connect Resend and Salesforce for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Resend–Salesforce connection.

Real-time

Two-way sync

Changes in Resend or Salesforce instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Resend or Salesforce data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Resend or Salesforce record.

Observability

Monitoring

Track your Resend ⇄ Salesforce sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Resend and Salesforce.

How the Resend and Salesforce connectors work

Resend

Integration surface
REST API
Authentication
API key (Bearer token)
Change detection
Webhooks for email lifecycle events; polling for contact and audience state
Capabilities
read · write · webhooks

Salesforce

Integration surface
REST, SOAP, and Bulk APIs
Authentication
OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
Change detection
Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
Capabilities
read · write · CDC
Rate limits
Daily API request allocations vary by edition and license count.
Salesforce setup guide
How it works

How to connect Resend to Salesforce — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Resend and Salesforce with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Resend connected
    Salesforce connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Resend and Salesforce objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Resend ⇄ Salesforce
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Resend Salesforce
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Resend and Salesforce integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 426 integrations available for Resend and Salesforce.

Popular · 8 of 426
All Resend integrations All Salesforce integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own