How to Connect Apollo.io with Salesforce (2026)

Why Connect Apollo.io and Salesforce

Apollo.io is one of the most powerful B2B prospecting and sales intelligence platforms available, with a database of over 270 million contacts. Salesforce is the world's leading CRM. Together, they create a seamless pipeline from prospecting to closed-won — Apollo handles lead discovery, enrichment, and outbound sequencing, while Salesforce manages the deal cycle, reporting, and customer relationships.

This integration is essential for SDR/BDR teams, sales managers, and revenue operations professionals who need to ensure that prospecting activity in Apollo flows cleanly into Salesforce without duplicate records or lost data. If your team is running outbound campaigns in Apollo but managing pipeline in Salesforce, this integration eliminates the manual data entry that slows reps down and creates CRM hygiene issues.

What This Integration Does

The Apollo.io-Salesforce integration creates a bidirectional data bridge between your prospecting engine and your CRM. Here is what it enables:

• Contact and lead sync: Push contacts from Apollo directly into Salesforce as leads or contacts, with all enriched data fields (title, company, phone, email, industry, employee count) mapped automatically.
• Account sync: Apollo company records can be synced to Salesforce account records, including firmographic data like revenue, headcount, industry, and technology stack.
• Activity logging: Emails sent through Apollo sequences, calls made, and tasks completed are logged as activities on the corresponding Salesforce lead, contact, or opportunity record.
• CRM data pull: Apollo pulls existing Salesforce data to show reps which prospects are already in the CRM, preventing duplicate outreach and wasted effort.
• Stage and status sync: When a lead's status or opportunity stage changes in Salesforce, Apollo can reflect that change to stop sequences or update contact dispositions automatically.

Native Integration vs Third-Party

Apollo.io offers a native, first-party Salesforce integration that is available on Apollo's Basic plan and above. This is the recommended approach for most teams. Here is how the options compare:

For the vast majority of use cases, the native integration is the right choice. It handles duplicate detection, field mapping, and activity logging out of the box.

Step-by-Step Setup

Step 1: Verify Prerequisites

Before connecting, make sure you have:

1. An Apollo.io account on the Basic plan or higher (the free plan does not support CRM integrations)
2. Admin access to your Apollo.io workspace
3. A Salesforce org with API access enabled (Enterprise, Unlimited, or Performance edition; Professional edition requires the API add-on)
4. Salesforce admin credentials or a dedicated integration user with appropriate permissions

Step 2: Connect Salesforce in Apollo

Log in to Apollo.io. Navigate to Settings (gear icon) and then select Integrations from the left sidebar. Find Salesforce in the CRM section and click Connect. Apollo will redirect you to Salesforce's OAuth authorization screen. Sign in with your Salesforce credentials and click Allow to grant Apollo the required permissions.

It is best practice to create a dedicated Salesforce integration user for this connection. This avoids disruption if a team member's account is deactivated, and it makes it easier to track API usage and audit integration activity.

Step 3: Configure Sync Settings

After authorization, Apollo displays the sync configuration panel. You need to configure several key settings:

• Sync direction: Choose bidirectional sync (recommended), Apollo-to-Salesforce only, or Salesforce-to-Apollo only.
• Record types: Select whether Apollo contacts should be pushed as Salesforce Leads, Contacts, or both (based on rules you define).
• Duplicate handling: Apollo can check for existing Salesforce records by email address before creating new ones. Enable this to prevent duplicates. You can set the behavior to update existing records, skip duplicates, or flag them for review.
• Auto-sync vs manual push: Decide whether contacts should sync automatically when added to sequences, or only when reps manually push them via the Apollo interface.

Step 4: Map Fields

Navigate to the Field Mapping tab within the Salesforce integration settings. Apollo pre-maps common fields (First Name, Last Name, Email, Phone, Title, Company). Review these mappings and add any custom fields you need. For example:

• Map Apollo's Technologies field to a custom Salesforce field for tech stack data
• Map Apollo's Employee Count to Salesforce's NumberOfEmployees field on the Account object
• Map Apollo's Lead Source tag to Salesforce's Lead Source picklist

Ensure that picklist values in Salesforce match the values Apollo sends, or set up default mappings for mismatches.

Step 5: Enable Activity Logging

In the integration settings, enable Log Activities to Salesforce. Configure which activities to log:

• Emails: All emails sent from Apollo sequences are logged as completed tasks on the Salesforce record
• Calls: Calls made through Apollo's dialer are logged with call duration and disposition
• Tasks: Manual tasks completed in Apollo (LinkedIn connection requests, custom steps) can also be logged

Step 6: Test the Connection

Push a single test contact from Apollo to Salesforce. Verify that the record appears in Salesforce with the correct field values. Send a test email from an Apollo sequence and confirm that the activity is logged on the Salesforce record. Check bidirectional sync by updating a field in Salesforce and verifying the change appears in Apollo.

Best Automation Workflows

1. Automated Lead Routing from Prospecting to Pipeline

When an Apollo sequence prospect replies with interest (positive reply detected), automatically push them to Salesforce as a Lead with the source set to "Outbound - Apollo" and assign them to the appropriate sales rep based on territory rules in Salesforce. This eliminates the manual handoff between SDR prospecting and AE pipeline management.

2. CRM-Aware Prospecting

Configure Apollo to pull Salesforce data nightly so that reps see a CRM badge on any Apollo contact that already exists in Salesforce. Set rules to block reps from adding contacts to sequences if they have an open opportunity in Salesforce, preventing awkward outreach to existing customers or active prospects owned by another rep.

3. Enrichment-on-Create Workflow

When a new lead is created in Salesforce from any source (web form, event, referral), use the bidirectional sync to pull that record into Apollo. Apollo enriches the record with firmographic and contact data, then pushes the enriched fields back to Salesforce. This keeps your CRM data fresh regardless of where leads originate.

4. Sequence-to-Opportunity Handoff

When a rep converts a Lead to a Contact and creates an Opportunity in Salesforce, automatically stop all active Apollo sequences for that contact. This prevents continued prospecting emails from being sent to someone who is already in an active sales cycle.

5. Re-engagement Campaigns for Closed-Lost Deals

Set up a Salesforce report that identifies Closed-Lost opportunities older than 90 days. Sync these contacts back to Apollo and automatically enroll them in a re-engagement sequence. This creates a systematic way to revisit lost deals without manual list building.

Data Sync Details

Conflict handling: When the same field is updated in both systems between sync cycles, Apollo defaults to a "last write wins" approach. You can configure specific fields to always defer to Salesforce as the system of record, which is recommended for fields like Lead Owner, Opportunity Stage, and Account details.

Common Issues and Troubleshooting

1. Duplicate Records in Salesforce

The most common issue. This typically happens when duplicate detection is not enabled, or when Apollo contacts are pushed before the initial Salesforce data pull completes. Fix: Ensure you run a full Salesforce sync before enabling auto-push. Enable Apollo's duplicate detection and set it to "Update existing" rather than "Create new." Also verify that Salesforce duplicate rules are not blocking Apollo's updates.

2. Activities Not Logging

Sequence emails are sending but not appearing in Salesforce. This is usually caused by the contact not being matched to a Salesforce record (they were never pushed to Salesforce), or by Salesforce validation rules blocking the activity creation. Fix: Confirm the contact exists in Salesforce. Check Salesforce validation rules on the Task/Event object that might reject records missing required fields. Review Apollo's sync log (Settings > Integrations > Salesforce > Sync Log) for specific error messages.

3. OAuth Disconnection

The Salesforce connection drops, usually because the connecting user's password changed, their account was deactivated, or the Salesforce refresh token expired. Fix: Use a dedicated integration user account with a stable password policy. If disconnected, go to Apollo Settings > Integrations > Salesforce and re-authenticate. No data is lost; the sync will resume and process any queued changes.

4. Field Mapping Errors

Fields are not populating correctly in Salesforce, or sync errors appear in the log related to field types. This happens when Apollo sends a text value to a picklist field that does not contain that value, or when number fields receive text data. Fix: Review field mappings and ensure data types match. For picklist fields, add the necessary values in Salesforce or create a default mapping in Apollo for unmatched values.

Alternatives

If the native Apollo.io-Salesforce integration does not meet your needs, consider these alternative approaches:

• Zapier: Useful for simple triggers like "When a contact is added to an Apollo list, create a Lead in Salesforce." Limited to one-directional workflows and lacks the duplicate detection and field mapping depth of the native integration. Pricing can escalate with volume.
• Make (formerly Integromat): Better for multi-step workflows, such as enriching data through a third tool before pushing to Salesforce. More affordable than Zapier at scale but requires more technical setup.
• Apollo API + Salesforce API (custom build): Maximum flexibility for organizations with developer resources. Apollo's REST API provides access to contact search, enrichment, and sequence management. Pair it with Salesforce's REST or Bulk API for high-volume data operations.
• Workato or Tray.io: Enterprise-grade iPaaS platforms that can handle complex data transformations, multi-system workflows, and high-volume syncs. Best for large organizations with RevOps teams managing multiple data sources beyond just Apollo and Salesforce.
• CSV export/import: The simplest fallback. Export contacts from Apollo as CSV and use Salesforce Data Import Wizard or Data Loader to import them. This is manual and not scalable, but works for one-time migrations or small teams on Apollo's free plan.