--- title: "Custom Button for Marking a No Show via Salesforce Event" source_url: https://help.chilipiper.com/hc/en-us/articles/36584062881299-Custom-Button-for-Marking-a-No-Show-via-Salesforce-Event article_id: 36584062881299 updated_at: 2026-07-24T18:56:02Z content_hash: 3d788b66 --- ## Who can use this feature? Available on All Products or Routing & Scheduling Available to All Users [Billing Center](https://fire.chilipiper.com/fire/admin/billing/overview) [Get a Demo](https://www.chilipiper.com/request-demo?utm_source=zendesk&utm_medium=help-center&utm_campaign=chili-hub) You can build a custom button in Salesforce to mark a Meeting as a No Show. This will automatically update a custom field ("No_Show_CP__c") in Salesforce, facilitating your reporting and allowing you to credit back a rep when the prospect doesn't attend the meeting with just one click! If you have not been upgraded to the Demand Conversion Platform (Fire), [check this article instead](https://help.chilipiper.com/hc/en-us/articles/360053022214-Custom-Button-for-Marking-a-No-Show-via-Salesforce-Event). #### Table of Contents - [Initial Notes](#h_01JFFEJ2NPD91AHPNBGYF0CA9M) - [Expected Behavior](#h_01JFFEXGST6JR6H9C9H7M1HT5B)[What if a meeting is rescheduled?](#h_01JFFETN6DKNS8RFS77B17DAX5) - [Setup Instructions](#h_01JFFEYER0VVZ5S3MR00TB569T) - [Final Notes (Advanced)](#h_01JFFFSW4C0JW0HBDW1WH7H820) ## Initial Notes Before covering the setup steps, there are a few important matters to consider: - The Salesforce Event must have been booked via Chili Piper (Fire) for this button to work - An _**apiToken=**_ parameter must be generated from the Chili Piper UI and appended to the end of the URL. **This step requires Chili Piper Admin Access**. We will cover how to generate this token in the [Setup Instructions](#h_01JFFEYER0VVZ5S3MR00TB569T). - Assuming the token is valid and has the proper permissions, a user does not need to be logged in to Chili Piper to be able to mark a Meeting as a No Show. - You will need Salesforce Setup access and the ability to create a Custom Button and add it to the page layout to create this Custom Button. - If you’re expecting the "No_Show_CP__c" custom field to be updated on the Event, Lead, and/or Contact Objects, the Chili Piper Integration User for your account must have Read and Edit permissions for this field in Salesforce. - The URL Endpoint accepts both 15 and 18 Digit Salesforce Event Record Id’s ## Expected Behavior Once the custom button is created successfully and added to the Salesforce Event Page layout, when a User clicks on the button, a new tab is opened with the No Show URL, including the Salesforce Event ID and authentication token. If the request is successful, the page will display: { “success”: true } ![](https://help.chilipiper.com/hc/article_attachments/36584073458323) When this happens:: - The Chili Piper system will receive the No Show for Round Robin purposes. This is when the meeting assignee is credited back for the No Show (if applicable). - The Salesforce **Event** Custom Field "No_Show_CP__c" will be updated to **true** from its default value of false - The Salesforce **Lead or Contact** Field "No_Show_CP__c", of the Record related to the Event, will also be updated to **true**. In the Workspace Level [Meetings Activity](https://help.chilipiper.com/hc/en-us/articles/31428605286931-Demand-Conversion-Platform-s-Meetings-Activity-and-Events-History) Dashboard view for a meeting marked as a No Show, we should see the meeting reflected like so: ![](https://help.chilipiper.com/hc/article_attachments/36584073467283) In the end-user [MyApp ChiliCal's view](https://help.chilipiper.com/hc/en-us/articles/26405583935891-ChiliCal-s-Scheduler-MyApp-s-Home-Page), we should also expect to see the value updated: ![](https://help.chilipiper.com/hc/article_attachments/36584073471251)   ### What if a meeting is rescheduled? If a meeting has been marked as a No Show, and that meeting is rescheduled either via a Reschedule URL or by the time being moved manually with the User’s Calendar, we expect the No Show field on **both the Event and related Lead or Contact** to be reset to the value of **false**. If you have added the "Reschedule_CP__c" custom field to the Event, each time a meeting is rescheduled, we will expect the field to increase by a value of one (1). Zero (0) is the default value. ## Setup Instructions The instructions below share the details on creating the Chili Piper API Key and Salesforce Custom Button. If you are a Legacy Chili Piper client who already has the Legacy No Show button setup, you can either: - Add a net new custom button for the Demand Conversion Platform (Fire). - Adjust your current Custom Button with the new URL.Note that if you go this route, once it’s saved and updated, any No Shows marked against a Legacy Chili Piper meeting will no longer be supported or marked as a No Show within Salesforce. Now, let's proceed to configure the button in Salesforce:   ### 1. Generate an API Access Token from the Chili Piper application. You must be a Chili Piper Admin to follow the steps below. - Navigate to Command Center → Integrations → API Access Token - Click “Generate Token” Button - Name your token (ie "Salesforce - No Show Button") - Set Permissions **Meetings.Modify** and **Meetings.Read****** - Click "Generate" - Copy and Save Access Token. **Note that after closing this pop-up, you will no longer be able to copy it, so be sure to save it somewhere**. Otherwise, you will need to create a new one. [Check this article's section](https://help.chilipiper.com/hc/en-us/articles/35576029581971-Edge-API-References-Demand-Conversion-Platform#:~:text=show%20a%20meeting-,Generating%20and%20Managing%20Your%20Tokens,-If%20you%20plan) if you need any further assistance in the API Token generation.    ### 2. Create Salesforce Button - **Setup** →**Object Manager** → **Event** → **Buttons, Links, and Actions** - Click New Button and configure it as: Label: “No Show" (the label can be any value you choose for your team; it does not need to be "No Show") - Display Type = Detail Page Button - Behavior = Display in New Window - Content Source = URL - URL to Input = https://fire.chilipiper.com/api/fire-edge/v1/org/crm/noshow/{!CASESAFEID(Event.Id)}?apiKey={Your_API_Token_Here} - Important: You **must** replace the value for {Your_API_Token_Here} with the API Token Value from Step #1. - Double-check the syntax & **Save** the button. The screenshot below shows how it should look within Salesforce Setup:![](https://help.chilipiper.com/hc/article_attachments/36584073487507) ### 3. Add the Button to the Event Page Layout - Now that the Custom Button is available in Custom Buttons, navigate to a real Event record, click the Gear Icon on the page → "**Edit Page**"![](https://help.chilipiper.com/hc/article_attachments/36604800824595)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 Page. ![Add Button to Lightning Page.gif](https://help.chilipiper.com/hc/article_attachments/36604800832019) _The above gif aims to generally show how to add a button to the Salesforce page layout, and is not specific to this particular button._ ## Test to confirm behavior Once the button has been added, schedule a test meeting via your Chili Piper link or the ChiliCal Scheduler against a test Lead or Contact in Salesforce. Find the test Event Record in Salesforce and click the No Show Button. Wait a few seconds, refresh the page, and check if the No Show checkbox is set to true. If it does, then the button will work correctly for your users within Salesforce.  ## Final Notes (Advanced) - If you’d rather run the API request to set the No Show via a Salesforce Screen Flow or some other more advanced method, this is possible, assuming you add **chilipiper.com** to the allowlist in Salesforce Remote Sites Settings. - Should you wish to track when the No Show or Cancel Custom fields are set to true, some clients have created custom Date fields on the Activity Object, such as: Became_a_No_Show_On__c - Became_a_Cancel_On__c - Last_Rescheduled_On__c - Then, use a Salesforce Flow to set the date values against these fields upon certain field updates, such as No_Show_CP__c being set to **true**.