Action required for Calendly (1.0.2) users

Written by Owner

Updated at August 20th, 2025

+ More

Table of Contents

Impact on your Zaps Updating your Zaps

Note

This information was accurate at the time of publication. Please check out the latest product update notes for any updates or changes.

Calendly is updating to a new app version, which brings several enhancements:

Enhanced security: Connect to Calendly using OAuth for a more secure experience. This replaces the previous API Key method.
New trigger:
- Invitee No Show Created: Triggers when an invitee is marked as “no-show” within Calendly.
Improved group subscriptions: The new group subscription scope allows you to configure Invitee Created/ Cancelled triggers to be triggered only for certain user groups within Calendly.
Expanded data: Additional fields and labels are available to use in your Zaps.

Impact on your Zaps

Current Zaps: Zaps that use the previous Calendly app version (1.0.2) will continue working until April 30, 2025. After this date, these Zaps will stop running.
Action required: To ensure uninterrupted services, you’ll need to manually update each affected Zaps to the latest app version. This may involve remapping fields to accommodate changes.
- View all affected Zaps that use Calendly (1.0.2). You only need to update connections and Zaps labels with CalendlyCLIAPI@1.0.2 in the Apps column.

Locate your affected Zaps.
1. View all affected Zaps that use Calendly (1.0.2) by using the App column.
Open each Zap and click on the affected Calendly step. The right sidebar will open to the Setup tab.
In the App tab, click Change.
Search for and select Calendly as it appears without any specific version numbers.
In the Account field, reconnect your app account.
Click Continue.
In the Configure tab, verify that your fields are set up as expected.
1. Some fields may no longer exist in the updated app version. There are new fields available for use when mapping fields in your Zaps.
In the Test tab, re-test your trigger or action step to ensure it works as expected.
Click Publish to finalize your changes and turn your Zap on.

You will need to repeat these steps for each affected Zap.