Chili Piper operates as a workflow tool between Google Apps/Microsoft 365 calendars and Salesforce via API access only. Access to the API is granted via OAuth 2.0, a three-click process that takes a few seconds.
Why connect to SFDC?
Chili Piper writes to Salesforce the meetings booked as an activity on the Event Object. Chili Piper can also re-assign the lead/contact owner based on rules. Furthermore, if someone books a meeting who does not previously exist as a Lead or Contact in Salesforce, Chili Piper can create the Lead or Contact so that your reps don't need to do so manually.
Optionally for reporting purposes, a set of custom fields can be added to your Salesforce Org.
How is this done?
To initially access the application via OAuth, you need to be a Salesforce admin or integration user. You will receive the login URL from the Customer Success Manager helping you onboard your account.
For the initial login, we recommend that the Salesforce admin makes the connection. You may use a Sync User at some point to avoid problems should the Salesforce admin who initially connects leave the organization, or you need to limit the scope of the Chili Piper Integration.
We'll prompt you to log in via Salesforce on this screen:
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 the Global Sync user:
- API Enabled
- To connect and interact with Chili Piper
- View Setup and Configuration
- Required to view individual field accessibility permissions and to view app setup
- View Roles and Role Hierarchy
- View All Users
- For user sync
Standard Object Permissions
- Accounts: Read/Edit/View All
- Contacts: Read/Edit/View All/Create*
- Leads: Read/Edit/View All/Create*
- Opportunities: Read†
- Cases: Read†
- Campaigns: Read/Edit/View All†
*Create is required if Chili Piper will be creating Leads/Contacts in your instance.
†Only required if you are making use of this object type in Chili Piper (Cases, Opportunities, or Campaigns)
Access to Events (Activities) is inherited by the related object.
Sync users 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 to security, we recommend using delegated object permissions with View / Modify on the object itself rather than Modify All Data.