Connect / GetResponse and Salesforce
+
Connect GetResponse and Salesforce
OpenContact sits between GetResponse 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 |
|---|---|---|
| GetResponse | API key | Send, Import, Suppression |
| Salesforce | OAuth | Send, Import, Suppression |
Set it up
- Connect GetResponse. Use API key. Setup guide.
- Connect Salesforce. Use OAuth. Setup guide.
- Import your GetResponse contacts into OpenContact, so there is one record per person.
- Create a sync rule. Pick a trigger, add GetResponse 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
GetResponse
A GetResponse destination must target a campaign. GetResponse stores the standard name as one full-name value; OpenContact combines first and last name when sending and splits the value when importing.
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 GetResponse and Salesforce?
Yes. When GetResponse 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 GetResponse 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 GetResponse and Salesforce cost extra?
Both tools bill you separately. OpenContact plans are priced by limits, and every plan includes all integrations. See pricing.