Salesforce and Apollo.io integration
Prospects and enrichment from Apollo.io without blanked fields, wrong owners or “new” leads that are already customers.
Into SalesforceSalesforce and Apollo.io
What moves between them
- Into SalesforceProspects, contacts and enrichment data, checked against every known customer before they reach a rep’s list.
- Out of SalesforceThe list of existing customers and their domains, so prospecting excludes them.
How we build it
- Field mapping that fills, not overwritesApollo writes only to empty fields, or only to the fields it owns.
- A dedicated integration userRecords stop showing one salesperson as the creator of everything Apollo touched.
- Owner rules in SalesforceOwnership set by your routing rules, not by Apollo’s user mapping.
- An identity check before anything is called net-newEvery known customer across all their domains, with a guard that stops the run if that list ever loads empty.
What goes wrong, and the fix
Problems we have found and fixed in production.
- “Push to Salesforce” blanked an addressA push writes Apollo’s value even when it is empty. Restore from field history, then change the mapping before the next push.
- Every record shows the same creatorThe connected app was authorised as one person. Reconnect it as an integration user.
- Revealing an email in Apollo created a contact in SalesforceAutomatic contact push is on. Turn it off for lookups that should stay out of the CRM.
- Leads called new are existing customersMatching on one domain misses subsidiaries and regional sites. The identity check covers every domain a customer uses.
Questions
Can we enrich without overwriting good data?
Yes. Set the mapping to fill empty fields only, and test the push on one record before any bulk update.
Other Salesforce integrations
- Salesforce and SnowflakeWarehouse metrics on every Salesforce account, Salesforce data in the warehouse for reporting, and one definition both sides agree on.
- Salesforce and DocuSignAgreements go out from the deal with the right template and signers, and signed terms, dates and signers come back onto it every time.
- Salesforce and Adobe Commerce (Magento)Customers, orders and catalogue kept in step between Salesforce and the storefront, with one ID both sides trust and a switch in front of every write.
- Salesforce and commercetoolsA move to commercetools without splitting customers in two: the same account IDs on the new platform, orders from both platforms counted once, and the old platform retired in planned steps.
- Salesforce and Microsoft Dynamics 365Closed deals become billing records in Dynamics 365 with the right product codes and dates, and billing status comes back to the account.
- Salesforce and IntercomSupport chats logged on the right contact and account, credited to the person who answered, and the account owner and region visible to the support team.
Talk to us about Salesforce and Apollo.io.
Tell us which systems are involved and what is going wrong. We reply within one business day, and new engagements begin in January 2027.