Skip to content
SuperSend logo
Salesforce logo

SuperSend → Salesforce

SuperSend + Salesforce integration

SuperSend has no Salesforce connector of its own. OutboundSync logs every SuperSend email event on the matching Lead or Contact, ready for reports and Flows.

BetaOne-way syncEmail

SuperSend + Salesforce at a glance

SuperSend connects to Salesforce through OutboundSync. SuperSend email sends, opens, link clicks, replies, bounces, unsubscribes, and interested leads are logged on the matching Lead or Contact as Tasks or EmailMessage records. OutboundSync works with every SuperSend plan, and the OutboundSync team sets up the source with you.

SuperSend + Salesforce integration facts
StatusBeta (SuperSend setup is guided by the OutboundSync team)
ChannelsEmail
DirectionOne-way, SuperSend → Salesforce
Salesforce recordsLeads, or Contacts and Accounts
Block listsNot available for this pairing
SuperSend planAny plan
SetupSelf-serve: create an External Client App, then connect it in OutboundSync; SuperSend source set up with our team

Without a native connector, SuperSend activity usually reaches Salesforce through CSV uploads, if at all. OutboundSync replaces that with an event stream: each SuperSend webhook becomes Salesforce activity on the Lead or Contact, labeled with the campaign and event type through the Task subject template you set.

That's enough to build real reporting. Group Tasks by SuperSend campaign to compare reply rates, use the interested event to drive a Flow, and use bounce and unsubscribe events to keep Salesforce contact data honest for every team that relies on it.

What syncs from SuperSend to Salesforce

Every event below arrives in near-real time and lands on the matched Salesforce record. Pick the ones you want per source.

SuperSend events OutboundSync syncs to Salesforce
EventChannelWhere it lands in Salesforce
Email sentEmailTask or EmailMessage on the Lead or Contact
Email openedEmailTask on the Lead or Contact, plus optional OutboundSync fields
Link clickedEmailTask on the Lead or Contact, plus optional OutboundSync fields
Reply receivedEmailTask or EmailMessage on the Lead or Contact
Email bouncedEmailTask on the Lead or Contact, plus optional OutboundSync fields
Lead unsubscribedEmailTask on the Lead or Contact, plus optional OutboundSync fields
Lead marked interestedEmailTask plus optional OutboundSync fields on the Lead or Contact

Event names come from the SuperSend webhooks OutboundSync receives. See the SuperSend event reference.

What teams do with SuperSend + Salesforce

  • Flow on interested leads

    Trigger a Salesforce Flow when SuperSend marks a Lead interested and assign it fast.

  • Compare campaigns

    Report replies and clicks by SuperSend campaign using templated Task subjects.

  • Protect data quality

    Bounce and unsubscribe Tasks flag records other teams should stop emailing.

Ways to connect SuperSend and Salesforce

The options teams weigh before they commit a production sync.

Ways to connect SuperSend and Salesforce, compared
OptionWhat it doesTrade-off
Zapier, Make, or n8nCompare integration platformsCatch SuperSend webhooks and write each event to Salesforce with a workflow you build.Every event type, retry, and field change is a workflow you maintain, billed per task or step.
Custom buildBuild vs buyWrite your own service against the SuperSend and Salesforce APIs.You own matching, deduplication, API limits, and every upstream schema change.
OutboundSyncPre-built email activity sync into Salesforce Leads and Contacts.Self-serve setup, searchable event logs, and support from the team that maintains the connector.

How to set up SuperSend + Salesforce

  1. Step 1: Connect Salesforce

    A Salesforce admin creates an External Client App, then connects it in OutboundSync and picks Task or EmailMessage logging.

  2. Step 2: Connect SuperSend

    The OutboundSync team creates your SuperSend source with you and points SuperSend's webhooks at it.

  3. Step 3: Choose events and fields

    Pick which SuperSend events to log, whether they write Tasks or EmailMessage records, and which OutboundSync fields to fill.

  4. Step 4: Send a test event

    Trigger one SuperSend event and confirm it on a real Lead or Contact.

  5. Step 5: Go live

    Turn on the source and start building Salesforce reports, dashboards, and Flows on real SuperSend data.

Plan requirements

SuperSend plan

Any plan

OutboundSync works with every SuperSend plan. The webhook and API features it relies on are included on all of them.

Salesforce

OutboundSync works across Salesforce editions. The difference is API capacity: plan for roughly 6 API calls per sent email once replies and status events are counted.

Which Salesforce edition you need

Which Salesforce edition you need
EditionFitWhat to know
ProfessionalLimited support - API limits may restrict ongoing sync.
  • Requires add-on for sufficient API capacity
  • Base API varies (add-on may be required)
  • 1,000 API calls per user license
  • Best for very small teams (fewer than 5 reps)
  • Requires close API usage monitoring
  • Admin available during setup recommended
EnterpriseMost commonRecommended - Best balance of capability, API capacity, and cost.
  • 100,000 base API calls per 24 hours
  • Example: 25 users ≈ 125,000 calls/day
  • Reliable for scaled outbound with multiple sequences
  • Activity logging for attribution and reporting
  • Low-risk setup experience
UnlimitedIdeal - Best for scale and high activity volume.
  • 5,000 API calls per user license
  • Example: 25 users ≈ 225,000 calls/day
  • Built for high-volume outbound teams
  • Maximum API headroom for growth
  • Enterprise-grade features and support

Millions of activities synced every month

EliseAI
Yotpo
Ona
HG Insights
Finout
Hologram

SuperSend + Salesforce FAQ

  • What SuperSend activity does OutboundSync sync to Salesforce?
    Email sent, email opened, link clicked, reply received, email bounced, lead unsubscribed, and lead marked interested.
  • Which Salesforce records does it write to?
    OutboundSync matches or creates Salesforce Leads and Contacts. SuperSend events land as task or EmailMessage on the Lead or Contact; or task on the Lead or Contact, plus optional OutboundSync fields; or task plus optional OutboundSync fields on the Lead or Contact. See the Salesforce data model docs for details.
  • Which SuperSend plan do I need for Salesforce sync?
    Any plan. The webhook and API features OutboundSync relies on are included on every SuperSend plan.
  • Is the integration one-way or two-way?
    One-way. Activity flows from SuperSend into Salesforce, and nothing is written back to SuperSend.
  • Do I need admin access to set it up?
    A Salesforce System Administrator creates the External Client App and authorizes OAuth.
  • Which SuperSend plan do I need?
    OutboundSync works with every SuperSend plan. The webhook and API features it relies on are included on all of them.
  • How is SuperSend + Salesforce priced?
    OutboundSync bills on sent messages per month. Replies, opens, clicks, and lead-category updates are not billed. Plan details are on the pricing page.
  • Can I do this with Zapier, Make, or n8n?
    Yes, for lightweight automation. Zapier, Make, and n8n are good for prototypes and simple routing, but they need ongoing maintenance and bill by task or step. OutboundSync is pre-built for outbound CRM sync, keeps searchable event logs beyond 30 days, and prices by outbound volume.
  • What breaks first when this scales?
    Data quality and reliability break first: duplicate events, retries, out-of-order webhooks, and bursts during big sends. OutboundSync handles idempotency, timing buffers, and queue recovery, and flags suspicious or mismapped payloads instead of writing them.

SuperSend resources

Tutorials, case studies, and updates related to SuperSend.

See SuperSend activity in Salesforce

A quick walkthrough with your own stack. Setup takes minutes, with no long-term contract.