SuperSend integration is live!
OutboundSync now supports SuperSend for one-way sync of email engagement data into HubSpot and Salesforce.
Harris Kenny


SuperSend → Salesforce
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.
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.
| Status | Beta (SuperSend setup is guided by the OutboundSync team) |
|---|---|
| Channels | |
| Direction | One-way, SuperSend → Salesforce |
| Salesforce records | Leads, or Contacts and Accounts |
| Block lists | Not available for this pairing |
| SuperSend plan | Any plan |
| Setup | Self-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.
Every event below arrives in near-real time and lands on the matched Salesforce record. Pick the ones you want per source.
| Event | Channel | Where it lands in Salesforce |
|---|---|---|
| Email sent | Task or EmailMessage on the Lead or Contact | |
| Email opened | Task on the Lead or Contact, plus optional OutboundSync fields | |
| Link clicked | Task on the Lead or Contact, plus optional OutboundSync fields | |
| Reply received | Task or EmailMessage on the Lead or Contact | |
| Email bounced | Task on the Lead or Contact, plus optional OutboundSync fields | |
| Lead unsubscribed | Task on the Lead or Contact, plus optional OutboundSync fields | |
| Lead marked interested | Task plus optional OutboundSync fields on the Lead or Contact |
Event names come from the SuperSend webhooks OutboundSync receives. See the SuperSend event reference.
Trigger a Salesforce Flow when SuperSend marks a Lead interested and assign it fast.
Report replies and clicks by SuperSend campaign using templated Task subjects.
Bounce and unsubscribe Tasks flag records other teams should stop emailing.
The options teams weigh before they commit a production sync.
| Option | What it does | Trade-off |
|---|---|---|
| Zapier, Make, or n8nCompare integration platforms | Catch 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 buy | Write your own service against the SuperSend and Salesforce APIs. | You own matching, deduplication, API limits, and every upstream schema change. |
| OutboundSync | Pre-built email activity sync into Salesforce Leads and Contacts. | Self-serve setup, searchable event logs, and support from the team that maintains the connector. |
A Salesforce admin creates an External Client App, then connects it in OutboundSync and picks Task or EmailMessage logging.
The OutboundSync team creates your SuperSend source with you and points SuperSend's webhooks at it.
Pick which SuperSend events to log, whether they write Tasks or EmailMessage records, and which OutboundSync fields to fill.
Trigger one SuperSend event and confirm it on a real Lead or Contact.
Turn on the source and start building Salesforce reports, dashboards, and Flows on real SuperSend data.
Any plan
OutboundSync works with every SuperSend plan. The webhook and API features it relies on are included on all of them.
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.
| Edition | Fit | What to know |
|---|---|---|
| Professional | Limited support - API limits may restrict ongoing sync. |
|
| EnterpriseMost common | Recommended - Best balance of capability, API capacity, and cost. |
|
| Unlimited | Ideal - Best for scale and high activity volume. |
|
Millions of activities synced every month
EliseAI
Yotpo
Ona
HG Insights
Finout
HologramTutorials, case studies, and updates related to SuperSend.
OutboundSync now supports SuperSend for one-way sync of email engagement data into HubSpot and Salesforce.
Harris Kenny
A quick walkthrough with your own stack. Setup takes minutes, with no long-term contract.
