Salesforce package release notes

Overview 

This article outlines new features and updates made to the version 2 Calendly Salesforce package. 

To migrate from our unmanaged Salesforce package version (v1) to our managed package version (v2), check out: Upgrade your Calendly Salesforce package from version 1 to version 2.

Otherwise, if you are on a managed package version (v2 or higher), you can upgrade to the current version by visiting your Salesforce integrations page and selecting the banner to upgrade. 

If you're unsure what version you currently use, visit your Salesforce integrations page to confirm your version. 

Version 2.6 

With version 2.6, we've introduced the ability to sync Calendly no-show occurrences to Salesforce so that the event record in Salesforce will show when certain events result in a no-show. Check out the changes made in version 2.6 below.  

New features
  • Adds 1 new custom field to the Event object:
    • Is No-Show: This checkbox field reflects occurrences when invitees are marked as no-shows within Calendly.

  • Adds 1 new UpdateEventNoShowTemplate flow template:

    • This flow template comes disabled by default and must be activated by a SFDC admin in order for no-show syncs to occur.

      • When the UpdateEventNoShowTemplate flow template is active within Salesforce:

        • Invitees marked as a no-show within Calendly will trigger Salesforce to search for the corresponding event record with the matching invitee UUID to update the IsNoShow custom field accordingly. 

Version 2.5 

With version 2.5, we've introduced the ability to sync Calendly event guest and co-host email addresses to Salesforce so that the event record in Salesforce will show all of the event attendees. Check out the changes made in version 2.5 below. 

New features
  • Adds 3 new fields to the CalendlyAction object:
    • Additional Guests: This field is a comma separated list of guest email addresses associated with the event.

    • Additional Hosts: This field is a comma separated list of co-host email addresses associated with the event.

    • Group Name: This field contains the name of the group that the Calendly user who was scheduled with belongs to.

  • Updates CreateEventTemplate

    • After creating the Calendly event record, this flow will now also add additional attendees to the event if the event has guests and/or co-hosts. The default behavior of this flow update is the following:

      • Searches for a matching lead or contact based on the guest email address provided in the Calendly form response. If a matching lead or contact is found, then that lead / contact record is added as an event attendee.

      • Searches for a matching Salesforce user based on the co-host email address (if it is a collective event). If a matching user is found, then that Salesforce user record is added as an event attendee.

  • Adds 2 new flow templates:

    • Get Event Attendee Template

    • Create Event Attendee Template

    • The updated CreateEventTemplate uses the 2 new flows above to create event attendees when an event is scheduled.

Version 2.4 

In version 2.4, we've introduced the ability to sync Calendly routing form responses directly to Salesforce, allowing admins to create and update records when a routing form is submitted. Check out the changes made in version 2.4 below. 

New features
  • Adds a new custom object (CalendlyRoutingFormSubmission) which will store information, including the name of the form submitted, any UTM parameters or Salesforce ID associated with the form, and the result of the routing rules behind the form.
  • Add a new customer object (CalendlyRoutingFormQuestionsAnswers) which will store form questions and answers and relation to the CalendlyRoutingFormSubmissions object the question/answer is for. 
  • Adds CreateRoutingFormLeadTemplate 
    • The default behavior of this flow is to look for matching leads or contacts based on the email address provided in the Calendly form response. If a matching lead or contact is found, the flow updates the CalendlyRoutingFormSubmission with the lead/contact ID so that the form responses are associated with the existing record. If no lead/contact is found, the flow creates a new lead owned by the system admin and associates the CalendlyRoutingFormSubmission with the new record. 
  • Adds Apex classes to: 
    • Create CalendlyRoutingFormSubmission and CalendlyRoutingFormQuestionsAnswers object records. 
Usability updates
  •  Adds FormSubmissionUUID to CalendlyAction object 
    • This will be null if there is not Calendly routing form gating the booking page. This enables Salesforce admins to treat events coming from routing forms differently than events coming from direct visits to Calendly booking pages. 

Version 2.3

With version 2.3, we have introduced the ability to sync Calendly links to Salesforce so that admins can reference a Salesforce user's booking page dynamically in automations native to Salesforce or in other tools that can integrate into and sync field values from Salesforce. Check out the changes made in version 2.3 below. 

New features
  • Adds a new custom object (CalendlyLink) which will store the Calendly user's email address, their Calendly link, and information about the link. 
  • Adds a Calendly Link field to the User object to store the user's profile link. 
  • Adds a flow template (MapUserCalendlyLinkTemplate).
  • Adds Apex classes to:
    • Upsert the CalendlyLink custom object records 
Usability updates
  •  Sets flow templates to be deactivated by default. 
    • This is following Salesforce's best practice guidelines so that flow template changes can be intentionally added to the flow by the SFDC admin instead of impacting the instance by default. 
    • Note: If you are not using a custom flow and are using Calendly's default flow behavior, post upgrading to version 2.3 or higher, copy the default flow templates and set the copy to active. 
  • Adds Apex classes to: 
    • Report to Calendly the package version post installation. This will help Calendly proactively email customers about planned deprecations for outdated versions.

Version 2.1 

We built the Calendly package for Salesforce as a managed package to make it easier to add new features and functionality to the integration, and moving forward, not require users to reinstall the package to get access to new functionality. Check out the changes made in version 2.1 below.

New features
  • Managed package.
  • Future-proof changes against Salesforce feature deprecation. 
  • Removes OnCalendlyActionCreated process. 
    • The logic that triggers flows to run is now included in the CreateEvent and CancelEvent flow templates. 
  • Introduces logic to prevent duplicate creation of the CalendlyAction object. 
Usability updates
  • Rebuilds CreateEvent and CancelEvent flows as CreateEventTemplate and CancelEventTemplate flow templates. 
  • Adds logic to the CreateEventTemplate to find only active System admins as a back up owner for new records created if the Calendly host does not match any Salesforce users. 
  • The CancelEventTemplate updates the Is Rescheduled field on the activity if the old event was rescheduled. 
Data syncing changes
  • Adds 12 fields to CalendlyAction object to capture custom questions and answers 5-10 on the booking flow.
    • Previously, only the first 4 questions and answers were passed. 
  • Adds an Is Rescheduled field to the Activity object and to the CalendlyAction object. 
  • Passes location details into the Location field on the CalendlyAction custom object.