How to Connect Outreach.io with Salesforce (2026)

Integration Overview

Outreach and Salesforce have a deep, native bi-directional integration that is central to how most Outreach customers operate. This is not a lightweight connector — Outreach installs a Salesforce managed package into your org and maintains continuous two-way data sync between the platforms. For most sales teams, this integration is configured during initial Outreach deployment and runs continuously from that point forward.

The integration ensures that reps can work in Outreach for sequencing and engagement while managers and leadership rely on Salesforce as the system of record. Activities, contacts, and opportunity data flow between both systems without manual entry.

What This Integration Does

• Bi-directional contact and account sync: Contacts and accounts created or updated in either system are reflected in the other, based on your sync rules.
• Opportunity sync: Outreach reads Salesforce opportunity data to provide deal context within sequences and prospect views.
• Activity logging: All Outreach engagement activities (emails sent, calls made, tasks completed) are automatically logged to the corresponding Salesforce records.
• Outreach Everywhere sidebar: A sidebar panel that surfaces Outreach prospect data and sequence information directly within the Salesforce interface.

Prerequisites

1. An Outreach account with admin permissions
2. A Salesforce org — Enterprise, Unlimited, or Performance edition (Professional edition has limitations with API access)
3. Salesforce admin credentials to install the managed package and authorize the API connection
4. Outreach recommends a dedicated Salesforce integration user with a full Salesforce license (not a Platform license)

Step-by-Step Setup

Step 1: Install the Outreach Salesforce Managed Package

Before connecting the integration, install Outreach's Salesforce managed package. This package adds custom components to your Salesforce org, including custom fields on Contact and Lead objects that store Outreach-specific data, and the Outreach sidebar component for Lightning pages.

To install, go to Outreach's admin documentation or the Salesforce AppExchange listing for the Outreach package. Follow the installation wizard, choosing to install for all users or specific profiles based on your needs. The installation requires Salesforce system administrator privileges.

Step 2: Connect Outreach to Salesforce

In Outreach, navigate to Settings (gear icon), then Integrations from the admin menu. Select Salesforce and click Connect. You will be prompted to log in to Salesforce and authorize the connection via OAuth. Use the dedicated integration user account if you have set one up.

After authorization, Outreach will verify the connection and display your Salesforce org ID and the connected user.

Step 3: Configure Sync Settings

This is the most important step and deserves careful attention. In Outreach under Settings, then Integrations, then Salesforce, configure the following sync categories:

Contact and Lead Sync

Define how Outreach prospects map to Salesforce contacts and leads:

• Sync direction: Choose bi-directional, Outreach-to-Salesforce only, or Salesforce-to-Outreach only. Bi-directional is the most common configuration.
• Field mappings: Map Outreach prospect fields to Salesforce contact/lead fields. Standard fields like name, email, phone, and title map automatically. Custom fields require manual mapping.
• Conflict resolution: When a field is updated in both systems, decide which system wins. Common practice is to let Salesforce win for data fields (title, phone) and let Outreach win for engagement-related fields.
• Create vs. update rules: Decide whether Outreach can create new contacts/leads in Salesforce, or only update existing ones. Many organizations restrict creation to prevent duplicate records.

Account Sync

Account sync works similarly to contact sync. Outreach accounts map to Salesforce accounts, with configurable field mappings and sync direction. Most teams sync accounts from Salesforce to Outreach (one-way) since Salesforce typically serves as the account system of record.

Opportunity Sync

Outreach reads Salesforce opportunity data to provide reps with deal context. This is typically configured as a one-way sync from Salesforce to Outreach. Outreach displays opportunity information (stage, amount, close date) alongside prospect records so reps have full context when engaging.

Step 4: Configure Activity Logging

Under the Salesforce integration settings in Outreach, configure how engagement activities are logged to Salesforce:

• Email activities: Emails sent through Outreach sequences are logged as completed Tasks (or optionally EmailMessage records) on the corresponding Salesforce contact or lead.
• Call activities: Calls made through Outreach's dialer are logged as Tasks with call duration and disposition.
• Task activities: Manual tasks completed in Outreach are logged to Salesforce.
• Activity field mapping: Configure which Salesforce Task fields to populate (Subject, Description, Type, Priority, etc.).

Activity logging is typically one-way from Outreach to Salesforce. Outreach does not pull Salesforce activities back in.

Step 5: Set Up the Outreach Sidebar in Salesforce

If you installed the managed package, you can add the Outreach Everywhere sidebar to Salesforce Lightning record pages. This sidebar shows:

• The prospect's current sequence status in Outreach
• Recent Outreach engagement activity
• The ability to add a contact to an Outreach sequence directly from Salesforce

To add the sidebar, edit the Lightning record page for Contacts or Leads in Salesforce Setup (under Lightning App Builder), and drag the Outreach component onto the page layout.

Data Flow Summary

Limitations and Considerations

• Salesforce API limits: The bi-directional sync is API-intensive. Large teams with thousands of prospects should monitor Salesforce API consumption. Outreach provides guidance on expected API usage based on team size.
• Duplicate management: If Outreach is allowed to create new contacts in Salesforce, you need strong deduplication rules in Salesforce to prevent duplicates. Consider restricting Outreach to update-only mode and handling record creation in Salesforce.
• Salesforce Professional Edition: Professional edition has limited API access, which can restrict the integration's functionality. Enterprise edition or above is strongly recommended.
• Custom object sync is not standard: The native integration syncs standard Salesforce objects. If you use custom objects extensively, you may need Outreach's API or a middleware tool to bridge the gap.
• Initial sync can be slow: When first connecting a large Salesforce org, the initial data sync can take hours or even days depending on record volume. Plan accordingly and do not expect instant results.
• Person accounts: If your Salesforce org uses Person Accounts instead of the standard Contact/Account model, additional configuration is required. Check Outreach's documentation for Person Account compatibility.

Troubleshooting Common Issues

Activities not logging to Salesforce

Verify that the integration user has write access to Task records in Salesforce. Check Outreach's sync logs under Settings, then Integrations, then Salesforce, then Sync Logs for specific error messages. Common causes include field validation rules in Salesforce blocking the activity creation.

Contacts not syncing

Check your sync direction and filter settings. If you have configured filters (for example, only sync contacts owned by certain users), contacts outside those filters will not sync. Also verify that required fields in Salesforce are populated — if a contact in Outreach lacks a required Salesforce field, the sync will fail for that record.

Sidebar not appearing in Salesforce

Ensure the managed package is installed and that the Outreach Lightning component has been added to the relevant record page layouts via Salesforce's Lightning App Builder. Users also need to be logged into Outreach in the same browser for the sidebar to authenticate.