Connect / beehiiv and Salesforce
+
beehiiv and Salesforce integration
OpenContact sits between beehiiv and Salesforce. Capture a contact once, send it to either or both, and keep opt-outs in step.
What each tool can do
| Tool | Connect with | Capabilities |
|---|---|---|
| beehiiv | API key + publication ID | Send, Import, Suppression |
| Salesforce | OAuth | Send, Import, Suppression |
Set it up
- Connect beehiiv. Use API key + publication ID. Setup guide.
- Connect Salesforce. Use OAuth. Setup guide.
- Import your beehiiv contacts into OpenContact, so there is one record per person.
- Create a sync rule. Pick a trigger, add beehiiv and Salesforce as destinations, and map the fields.
- Dry-run it. See which destinations match and which fields would be sent, then switch the rule on.
Good to know
beehiiv
A beehiiv connection belongs to the publication ID saved with its credentials. Update the connection credentials if you need to point it at a different publication. Select a newsletter list when using beehiiv as a sync or migration destination.
Salesforce
Salesforce requires a Last Name on new Contacts; if a contact has none, OpenContact uses the email so the record still saves. Imports read the standard Contact object.
Questions
Does OpenContact sync unsubscribes between beehiiv and Salesforce?
Yes. When beehiiv or Salesforce reports an unsubscribe, bounce or spam complaint, OpenContact records it and passes it to the destinations your rules select.
Do I need a CSV to move contacts between beehiiv and Salesforce?
No. Import contacts from one tool into OpenContact, then send them to the other with a sync rule. To move a whole list, use list migration.
Does connecting beehiiv and Salesforce cost extra?
Both tools bill you separately. OpenContact plans are priced by limits, and every plan includes all integrations. See pricing.
Related
beehiiv integration · Salesforce integration · Sync rules · Suppression sync · All pairings