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, so it’s a 3 click process that takes a few seconds.
Why connect to SFDC?
Chili Piper writes to Salesforce the meetings that get 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, there are set of custom fields that 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. Login as that user to connect Chili Piper via OAuth here.
For the initial login, we recommend that the Salesforce admin does the connection. You may choose to use a Sync User at some point to avoid problems should the Salesforce admin who originally connects leaves the organization or should you need to limit the scope of the Chili Piper Integration.
We'll prompt you to login via Salesforce on this screen:
Below are the minimum Permission Sets for a User to Create the Chili Piper Account via Salesforce or for a User to become the Global Sync user:
- API Enabled
- View Setup and Configuration
- View Roles and Role Hierarchy
- View All Users
Standard Object Permissions
-Accounts: Read/Edit/View All
-Contacts: Read/Edit/View All/Create*
-Leads: Read/Edit/View All/Create*
*Create is required if Chili Piper will be creating Leads/Contacts in your instance.
Access to Events is typically inherited by the related object. Sync user should have "Modify All Data" to ensure creation, editing, and deletion of Events is possible.
Note: Profiles such as Salesforce Chatter users can book meetings, but only the meetings booked for others will have an associated Salesforce Event. Chatter users cannot own / be assigned events, so these will not create Events. Therefore, the Global Sync user cannot be a Chatter user.