Connect / MailerLite and Salesforce
+
MailerLite and Salesforce integration
OpenContact sits between MailerLite 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 |
|---|---|---|
| MailerLite | API key | Send, Import, Suppression events |
| Salesforce | OAuth | Send, Import, Suppression |
Set it up
- Connect MailerLite. Use API key. Setup guide.
- Connect Salesforce. Use OAuth. Setup guide.
- Import your MailerLite contacts into OpenContact, so there is one record per person.
- Create a sync rule. Pick a trigger, add MailerLite 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
MailerLite
When you generate a webhook, OpenContact registers it with MailerLite automatically and stores its signing secret. Every incoming event is verified with an HMAC signature, so only genuine MailerLite requests are honored.
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 MailerLite and Salesforce?
Yes. When MailerLite 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 MailerLite 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 MailerLite and Salesforce cost extra?
Both tools bill you separately. OpenContact plans are priced by limits, and every plan includes all integrations. See pricing.