Connect / Kit and Salesforce
+
Kit and Salesforce integration
OpenContact sits between Kit 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 |
|---|---|---|
| Kit | API v4 key | Send, Import, Suppression |
| Salesforce | OAuth | Send, Import, Suppression |
Set it up
- Connect Kit. Use API v4 key. Setup guide.
- Connect Salesforce. Use OAuth. Setup guide.
- Import your Kit contacts into OpenContact, so there is one record per person.
- Create a sync rule. Pick a trigger, add Kit 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
Kit
Kit supports first_name as a standard subscriber field. Last name, company, country, phone, and other mapped values are sent only when matching custom fields exist in Kit. UTM values captured by OpenContact are also included as the form-subscription referrer when available.
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 Kit and Salesforce?
Yes. When Kit 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 Kit 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 Kit and Salesforce cost extra?
Both tools bill you separately. OpenContact plans are priced by limits, and every plan includes all integrations. See pricing.
Related
Kit integration · Salesforce integration · Sync rules · Suppression sync · All pairings