Skip to main content

Adding a Custom Button in Salesforce to Book Meetings

Jorge Ferreira Filho
  • Updated

Who can use this feature?

Available on All Products
Available to Admins Salesforce Admins
Billing Center Get a Demo

Creating a button on the page layout to launch Chili Piper's ChiliCal is an easy way to take advantage of Chili Piper inside Salesforce.

While "Links" can also be created and used in some situations to book or share via email or API, this article will focus on the instructions for creating a Custom Button within Salesforce Setup that loads ChiliCal and/or Handoff.

It is also possible to use a Salesforce Screenflow to load Chili Piper, should you need the User to take some action or update fields before the User loads Chili Piper to book a meeting. The URLs for the buttons listed below will also work and be supported via Screenflows. 

This article is dedicated to users who have migrated and are working with our Demand Conversion Platform instance. If you are still a Legacy user, check this article instead.

Once set, the end-user must have a logged-in session with Chili Piper access to the Scheduler's Interface.

Table of Contents

Creating a Salesforce Custom Button

  1. Navigate to "Object Manager" in Salesforce Setup
  2. Search for the Object you wish to create the button
  3. Click Into "Buttons, Links, and Actions" → "Add Button or Link"
  4. Name the Label, add a description (optional), and select the following:
    • Display Type: "Detail Page Button"
    • Behavior: "Display in a new window"
    • Content Source: "URL"

Choose the Correct URL to add to Salesforce

Chili Piper requires one of three types of values from within Salesforce to find an email address to be able to schedule a meeting on the calendar:

  • Lead Id
  • Contact Id
  • Email Address

Chili Piper accepts both 15-digit and 18-digit Salesforce IDs for passing the value. Differently from Legacy, the URLs below can be used to open the ChiliCal's and Handoff's Scheduler, as you can switch between both in the Demand Conversion Platform.

Click the articles below to learn more about the above-mentioned Schedulers:

Now, let's check the URLs that can be added to Salesforce per object:

Lead Object

 https://fire.chilipiper.com/chilical-scheduler/?crmRecordType=Lead&crmRecordId={!Lead.Id}

Example:

Lead Salesforce 2025-01-14 at 12.35.01 PM.jpg

 

Contact Object

https://fire.chilipiper.com/chilical-scheduler/?crmRecordType=Contact&crmRecordId={!Contact.Id}

Example:

Contact Salesforce 2025-01-14 at 12.35.56 PM.jpg

Route by and Relating to Opportunity, Case, or Custom Object

Opportunity Object

https://fire.chilipiper.com/chilical-scheduler/?crmRecordType=Contact&crmRecordId={!Opportunity.Primary_Contact__c}&opportunityId={!CASESAFEID(Opportunity.Id)}

 In this URL, we are using a custom Lookup(Contact) field called "Primary Contact" - {!Opportunity.Primary_Contact__c} to book a meeting. A Primary Contact must be defined on the Opportunity to be able to schedule a meeting.

You may have different naming conventions for your field(s) in Salesforce and need to adjust the merge tag to ensure a Contact Id gets populated in the URL from the Contact you wish to book a meeting with.

Opportunity Salesforce 2025-01-14 at 12.36.54 PM.jpg

Case Object

https://fire.chilipiper.com/chilical-scheduler/?crmRecordType=Contact&crmRecordId={!Case.ContactId}&caseId={!CASESAFEID(Case.Id)}

Example:

Case Salesforce 2025-01-14 at 12.41.55 PM.jpg

Custom Object

https://fire.chilipiper.com/chilical-scheduler/?crmRecordType=Contact&crmRecordId={!Custom_Object__c.Contact_Id__c}&objectId={!Custom_Object__c.Id}
If you are routing by or relating to a Custom Object, the Contact Id are not on the object's layout by default. As such, you'll may need to add a custom lookup field on the custom object that references the related Contact's Id or Email Address for the Button to work.

Once you have a Contact Id or Email Address available on the Custom Object Record, you can use a tag like {!Custom_Obj.Contact__c} where "Custom_Obj" is your object name and "Contact__c" is the custom field name. These names will vary depending on how you set them up.

If you have multiple custom object records related to the Lead/Contact, you will want to also pass one additional parameter customObjectId={!Custom_Obj.Id} so that Chili Piper knows which of the Related Custom Object Records to route against your Rules.

Items to Note:

  • This will relate the SFDC event to whichever record is passed (it may route based on it too, if you've set up custom object matching and rules)

  • You can use this interchangeably with the opportunityId or caseId (ie, you can pass it an Opportunity Id value and it'll work). However, it's recommended to use the respective one for those objects.

  • You wouldn't use both objectId and opportunityId together in the URL; you would use either one or the other.

  • Setting this objectId value will override whatever settings are configured within the App CRM Actions or Handoff Router settings.

 

Add the button to the layout

Once your Custom Button is created on the respective Object, the next step is adding the Button to the Salesforce Page Layout so that End Users are able to access and click on the Button to load Chili Piper. 

  1. Now that the Custom Button is available in Custom Buttons, navigate to a real Opportunity record, click the Gear Icon on the page → "Edit Page"

    2. Click into the "Highlight Panel", then click "Add Actions" on the Right Panel, search for the name of the Button that you created, and Add it to the PageAdd Button to Lightning Page.gif

    Note: Salesforce Lightning Page Layouts have a maximum amount of 10 Visible Action Buttons

    3. Click "Save" in the top right and your Custom Button to book meetings will be Live. 

Visualize Page

When you click the Button, you should expect to see the Chili Piper's Scheduler open using the Name and Email Address of the respective Lead or Contact you are booking.  

 Available Parameters

Query string parameters that can be added to the scheduler URL to customize the behavior of the Scheduler. Below are the available parameters that can be added.

id email address Pass the prospect's email address as an ID if the prospect is in your CRM.
  CRM ID Pass prospect CRM ID (both Lead & Contact objects work for Salesforce)

by

 firstname-last name (Unique Chili Piper link)

The booker's full name (if they want to get notified and get credit)

assignee

 firstname-last name (Unique Chili Piper link)

Specifies an assignee while using a Round-Robin Scheduling Link.

For example, the Scheduling Link below would assign the meeting being booked to John Doe:

https://fire.chilipiper.com/round-robin/example-rr?assignee=john-doe
opportunityId SFDC Opp ID

The SFDC ID of the Opportunity that the meeting should be related to.

This also determines which opportunity to route in rule execution (aka tiebreaking).
caseId SFDC Case ID

The SFDC ID of the Case that the meeting should be related to.

This also determines which case to route in rule execution (aka tiebreaking).
objectId SFDC Custom Obj ID

The SFDC ID of a Custom Object that the meeting should be related to.

This also determines on which custom object to route in rule execution (aka tiebreaking).
accountId SFDC Account ID

The SFDC ID of an Account. Creates a Contact under the Account passed to us.
campaignId & status SFDC Campaign ID / Status

The SFDC Campaign Id to be associated to the prospect and the campaign member status value.
meetingTypeId

Meeting Type ID

Passes a specific meeting template (Meeting Type) to the meeting being booked, even if the Scheduling Link is associated with a different one.

 

workspaceId

WorkSpace ID

The Chili Piper workspace should be loaded in the scheduler.

crmRecordType

CRM Record Type

The SFDC record that should be used in the booking process.

crmRecordId

CRM Record ID

The SFDC record ID that should be used in the booking process.

 

 

 

 

Related articles

Comments

0 comments

Please sign in to leave a comment.