Objective
Install the Outreach managed package in Salesforce and reconnect the Outreach Salesforce sync plugin to ensure continued, uninterrupted sync between Outreach and Salesforce.
Applies To
- Outreach Admins
- Salesforce Admins/Owners
Overview
Outreach is listed on Salesforce AppExchange as an officially validated, secure, and admin-approved managed package. Installing the Outreach managed package ensures your organization's Salesforce integration meets Salesforce's current security and compliance standards, and allows Outreach to push future security updates to your org without requiring additional admin intervention.
The package contains only the connected app your organization has always used to authenticate the Outreach-Salesforce sync. No new permissions, data access, or functionality is introduced.
Before You Begin
This process requires action from two admins, who may or may not be the same person at your organization:
- Salesforce Admin: Must have admin or owner access in Salesforce to install the managed package.
- Outreach Admin: Must have admin access in Outreach to reconnect the sync plugin.
Coordinate with the appropriate people at your organization before beginning.
Procedure
Part 1: Install the Outreach Managed Package (Salesforce Admin)
- Log in to Salesforce as an admin or owner.
- Open the Outreach listing on Salesforce AppExchange and click Get It Now.
- When prompted, select Install for All Users to ensure the package is available across your organization.
- Review the permissions requested and click Install.
- Salesforce will process the installation. You may receive a confirmation email when the install is complete.
Part 2: Reconnect the Salesforce Plugin in Outreach (Outreach Admin)
Note: Reconnecting the plugin will generate new authentication tokens. Your sync configuration and field mappings will not be affected.
- Log in to Outreach as an Admin.
- Navigate to Administration > Integrations > CRM.
- Click the ... menu in the top right and select Reconnect.
- Enter the applicable Salesforce login credentials when prompted.
- Test the connection to confirm syncing is active.
For additional guidance on reconnecting, see How To Reconnect and Update User Authorization for CRM Plugins.
Frequently Asked Questions
Why is this required?
Salesforce recently updated their security policy, requiring all connected applications to use a managed package. Installing the Outreach managed package brings your organization's Salesforce integration in line with Salesforce's security standards and allows Outreach to push future security updates to your org without requiring additional admin intervention each time.
What if I don't take action?
If the managed package is not installed and the plugin is not reconnected, your organization's Salesforce sync will disconnect when Outreach applies the security update Salesforce is requiring. Outreach itself will continue to function normally — sequences, AI features, and Kaia call transcription are unaffected. But while disconnected, no new or updated records will import from Salesforce into Outreach, and nothing done in Outreach will sync back to Salesforce.
If your sync disconnects, restoring it means installing the package, reconnecting the plugin, and running a Historical Data Load for every object you sync between the two platforms to backfill everything missed while disconnected. Depending on your data volume, this can run into Salesforce API limits, which may require coordinating with your Salesforce admin to manage.
Do I need to do this if I don't use the Salesforce sync?
If your organization does not use the Outreach-Salesforce sync integration, no action is needed. This update only applies to customers with an active CRM sync with Salesforce.
If you are unsure, check Administration > Integrations > CRM in your Outreach org. If there is no Salesforce connection listed there, no action is required.
Is this package related to AI in any way?
No. This package has nothing to do with AI. The name on the AppExchange listing reflects Outreach's overall product branding, not what this specific package does. This package only contains the Connected App used to authenticate the existing Salesforce sync your organization already has. Installing it does not add AI features, enable any AI functionality, or require any reconfiguration beyond the standard install and reconnect steps.
We don't use Outreach's AI features. Do we still need to install this?
Yes. This package is required for any organization with an active Salesforce sync, regardless of whether you use AI features in Outreach. It is the connected app that authenticates your existing CRM sync, and Salesforce's security requirements apply to that sync whether or not AI capabilities are in use.
Is this the same thing as Outreach's "Last Touch Sequence Attribution" unmanaged package?
No. These are two different things and entirely unrelated:
- The Outreach managed package (what this update is about) replaces the legacy version of the Salesforce Connected App your organization already uses for the core Outreach-Salesforce sync. This is required for all customers, in both Sandbox and Production.
- The "Last Touch Sequence Attribution" unmanaged package is a separate, optional package some customers have installed for sequence-based reporting in Salesforce. It is unrelated to this update and should stay installed as-is. Removing it would break existing reports and flows and could result in loss of historical attribution data.
If you are unsure which one your organization has installed, check Setup > Installed Packages in Salesforce, or contact Support for confirmation.
Will this change my existing field mappings, sync rules, or automations?
No. This update only changes how the integration authenticates with Salesforce. Your existing field mappings, sync conditions, and automations will continue to work exactly as they do today.
Will this affect my sellers?
No. This change is limited to the admin install and reconnect process. Sellers will not experience any changes to how they use Outreach.
Will installing the package cause any downtime?
No meaningful downtime is expected. Reconnecting the plugin after install takes a moment, and any activity that happens during that brief window is minor enough that it typically does not need any manual work. If you want to be certain nothing was missed, you can run a Historical Data Load for the affected day to backfill anything from that window.
The AppExchange listing says this package costs $1/month. Is that true?
No. The Outreach managed package is included with your Outreach subscription. Salesforce requires a dollar amount for packages categorized as Paid, with a minimum of $1. This is a limitation in how AppExchange listings can be configured — it is not actually charged to Outreach customers.
What does the package do?
Salesforce requires four security controls to be enabled on all Connected Apps, including the one Outreach uses to sync with your org:
- PKCE — An added login safeguard that ensures only the real Outreach app can complete authentication, closing off a common interception attack.
- Refresh token rotation — Each time the integration renews access, it gets a new token, and only one refresh can happen at a time. This limits how long a leaked token would work and makes suspicious activity easier to catch.
- Idle token invalidation — Tokens that go unused for 30 days are automatically invalidated. Outreach keeps active integrations refreshed in the background, so this only affects connections that have genuinely gone idle.
- IP allowlist for token refresh — Refresh requests are only accepted from Outreach's network, so a stolen credential cannot be used from somewhere else.
This update also includes reduced OAuth scopes. The previous version of the Connected App requested admin-level access. The updated package narrows this to API access only, which is all the integration actually needs. The only permission still required is API Enabled.
The package contains only the Connected App used to authenticate the sync between Outreach and Salesforce. It does not include any other objects, fields, triggers, Apex classes, or automation. This is a one-time update — Outreach has committed these controls as permanent, so there is nothing further for you to configure or revisit later.
How do I confirm the install and reconnect were successful?
After reconnecting in Outreach, use the Test Connection option under Administration > Integrations > CRM to confirm the sync is active. You can also check that recent Salesforce activity is appearing in Outreach and vice versa as a real-world confirmation that data is flowing both ways.
Your Salesforce admin can confirm the correct package is installed by going to Setup > Installed Packages and looking for a row with these details:
- Package Name: Outreach
- Publisher: getoutreach.com
- Namespace Prefix: Outreach
The package detail page will also show Package Type: Managed and Version Name: ReducedScopes. This is separate from the "Engagement Panel & Sequence Attribution" package some organizations also have installed, which shows as Package Type: Unmanaged and has a blank Namespace Prefix.
The managed package replaced my original connected app instead of adding a new one. Is that expected?
Yes. The managed package upgrades your existing Outreach Connected App in place to a newer version with reduced OAuth scopes and updated security controls. It does not add a second, separate connected app. As long as you have reconnected the plugin in Outreach and the sync is working, everything is functioning as intended.
Does the package need to be maintained or updated going forward?
No. This is a one-time install and reconnect. You will not need to take further action to keep these security controls in place, and Outreach will handle any future package updates without requiring you to reinstall anything.
Is there a different install link for Sandbox vs. Production?
No. The same package and install link work for both Sandbox and Production Salesforce instances.
Please contact Support if you need further assistance.
I am getting a duplicate error when I try to install. How do I fix this?
The duplicate error ConnectedApp(Outreach) duplicate value found is due to already having a Connected App with the name Outreach. To resolve, located the current Connected App and rename it, then try the AppExchange install again.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article