Configuring the Salesforce Integration for your Organization

Salesforce integration is optimal for any organization relying on Salesforce as its CRM. All visitor and prospect data between Chili Piper and Salesforce needs to be synced in real time. 

In this article, we will quickly cover how to set up your integration, the minimum permission scope required for Global Sync users, and the OAuth error in Chili Piper's Demand Conversion Platform.

How to Setup?

To set up the integration and a Global Sync user, you will first need your Salesforce admin to connect Salesforce via the Integrations page in the Admin Center.

Once connected, you will notice a "Connected" flag, as shown in the screenshot below:

You can use the Reconnect button to reconnect the account for any reason or replace the current Global Sync user. 

Salesforce Scope and Minimum Permissions
 

Below are the minimum Permission Sets (from a user profile level) for a User to Create the Chili Piper Account via Salesforce or for a User to become a Global Sync user:

Administrative Permissions

• API Enabled
  • To connect and interact with Chili Piper
• View Setup and Configuration
  • Required to view individual field accessibility permissions
  • View app setup
• View Roles and Role Hierarchy
  • View role details for user lookup and profile data
• View All Users
  • For user sync
• Approve Uninstalled Connected Apps OR Use Any API Client
  • If applicable: Salesforce will begin restricting Connected App access. These permissions will allow an admin user to continue using an "uninstalled" connected app. Alternatively, an admin can click "Install" beside the Chili Piper connected app, and this permission is not needed. 

Standard Object Permissions 

• Accounts: Read/Edit/View All
• Contacts: Read/Edit/View All/Create
  • Create is required if Chili Piper creates Contacts in your Salesforce instance.
• Leads: Read/Edit/View All/Create
  • Create is required if Chili Piper creates Leads in your Salesforce instance. Read/View is required for prospect lookups in Chili Piper, even if you are not using the Lead object in your workflows.
• Opportunities: Read* 
• Cases: Read* 
• Campaigns: Read/Edit/View All*^
• PushTopic: Create/Read/Edit
  • This permission is only needed for Distro

*Only required if you are making use of this object type in Chili Piper (Cases, Opportunities, or Campaigns)

^ - The following fields need, at least, read access as they are queried while looking for active Campaigns in Salesforce: Id, Name, StartDate, EndDate, Status, IsActive

Events

The related object inherits access to Events (Activities).

The connection user should have either "View All / Modify All" or "Modify All Data" for the related object to ensure the creation, editing, and deletion of Events is possible.

Given the implications for security, we recommend using delegated object permissions with View / Modify on the object itself rather than Modify All Data.

Distro-only, Streaming API

If you are planning to use Distro product, you will need to ensure you have "Streaming API" enabled for the integration user. 

Setup -> User Interface -> Scroll down to the "Setup" section -> "Enable Streaming API".

This only needs to be done to the user who is performing as your integration user as configured in Chili Piper. 
 

OAuth Error - OAUTH_APPROVAL_GENERIC Troubleshooting

Starting in September 2025, Salesforce restricted the use of uninstalled connected apps. This usage restriction blocks end users from using uninstalled connected apps, which can impact your initial integration with Chili Piper's app.

If that's the case, you likely will see the error below after trying to integrate Salesforce via Admin Center:

To mitigate the error, you can follow the steps below:

1. Navigate to Setup
2. Search Connected apps Oauth Usage
3. Find Chili Piper
4. Click Install
   
    

Optionally, you can give the integration user permission to use uninstalled apps via profile permissions:

1. Click the gear icon → Setup.
2. In Quick Find, type Profiles → click Profiles.
3. Find and click the Profile used by your integration user (the profile label).
4. On the profile page, either:
   1. Click the System Permissions link, then click Edit, or
   2. Click Edit at the top of the profile and scroll to the System Permissions / Administrative Permissions area.
      (UI varies slightly by org; both get you to the same permission list). 
      Salesforce
5. In the list, locate and check the permission(s) you want to grant:
   1. Approve Uninstalled Connected Apps — let this user self-authorize/use an uninstalled connected app.

Connecting Your Salesforce Sandbox to a Chili Piper Sandbox

Salesforce sandbox support allows your team to test Chili Piper changes (routing rules, workflows, mappings, etc.) in a safe staging environment before deploying to production. These steps outline how to connect your Salesforce Sandbox environment to a Chili Piper sandbox tenant.

Available to Admins with access to both:

• A Salesforce Sandbox org

• A Chili Piper sandbox tenant

How to Connect Your Salesforce Sandbox

1. Log in to Your Chili Piper Sandbox Tenant - Navigate to your Chili Piper sandbox login URL and sign in. 
   If you’re signed in to another Chili Piper tenant, log out before proceeding.
2. Open the Integrations Page in Sandbox Mode. In your browser, go to:

https://<your-sandbox-subdomain>.chilipiper.com/fire/admin/integrations?isSandbox=true

Adding ?isSandbox=true ensures that the Salesforce OAuth flow will use the Salesforce sandbox login endpoint (test.salesforce.com), not production.

3. Connect Salesforce - On the Integrations page, locate Salesforce and click Connect
4. Authorize with Salesforce Sandbox Credentials - On the Salesforce login page. Enter your Salesforce Sandbox username and password and  approve the OAuth access request
5. Verify Connection After authorization - The Salesforce integration will show a Connected status.