Prospects book tours through Calendly, but that interest doesn't count for much unless it turns into a tracked lead in Flex. Entering each booking by hand means some prospects fall through before anyone follows up. Connecting Calendly and Flex through Zapier creates a lead the moment someone books, and alerts your team again if they cancel or don't show.
This connection runs through Flex's own app in Zapier's directory, built on Flex's Zapier API. Each Zap has exactly one trigger and one resulting action, so a single Zap only ever moves data one way, from the trigger app to the action app. Flex's Zapier actions only create new records; they can't update existing ones, which matters more in this article than most, since two of these workflows are about following up on an existing lead.
Prerequisites
Before you connect Calendly and Flex, confirm the following:
A Calendly Standard plan or higher. Zapier triggers aren't available on Calendly's free plan.
Admin or owner access in Calendly if you want to watch bookings across your whole team rather than one person's calendar.
Admin access in Flex, using your Flex admin credentials or a Client ID and Client Secret if your organization uses SSO.
Important: Custom properties of type date or multi-select aren't supported in Flex actions, so if you're passing custom Calendly field answers into the Opportunity below, confirm the field type on the Flex side first.
Example workflows
Create a lead and opportunity when a tour is booked
When a prospect books a tour through Calendly, this Zap creates the opportunity in Flex, along with the member and company associated with it, so the lead is tracked from the first booking rather than whenever someone remembers to log it. This is the official pre-built template for this pairing.
Trigger | Action |
 Invitee Created Triggers when an invitee schedules an event. Filter by even type 'Tour'. |  Create Opportunity Creates an opportunity for a new member. This action allows creating a new company as well. |
Notify the location manager when a tour is booked
When a tour is booked, this Zap alerts the location manager right away, so they know to prepare for the visit instead of finding out when the prospect walks in.
Trigger | Action 2 | Action 3 |
Invitee Created Triggers when an invitee schedules an event. Filter by even type 'Tour'. | Create Opportunity Creates an opportunity for a new member. This action allows creating a new company as well. | Send an email or Slack message with the booking details, using whichever notification tool is already in your stack. |
Build this as one Zap with three steps in order, not as a second Zap running alongside workflow 1. Two independent Zaps watching the same trigger can run in either order, so the notification Zap might fire before the opportunity exists. There's also no separate "log" step to add here, since Flex has no action to attach notes or activity to an Opportunity. The Opportunity created in step 2 is the booking record.
Note: If you operate multiple locations, you'll need a separate version of this Zap per location, or a Path step to route the notification to the right manager, since there's no way to filter this automatically by location.
FAQs
Can this integration flag a lead in Flex when a tour is canceled, or the prospect doesn't show up?
Not by updating the Flex record. Flex has no action to update or tag an existing Opportunity, so there's no way to mark it as canceled or no-show in Flex via Zapier. What you can build instead is a notification: one Zap on Calendly's Invitee Canceled trigger, and a separate one on Invitee No Show Created, since those are two different triggers. Each one alerts the sales rep or location manager, so a missed tour turns into a manual follow-up task rather than disappearing.
Does the no-show trigger work for every Calendly setup?
Not necessarily. Calendly's own documentation states that no-show triggers aren't available at group scope, only at the individual user level. If tours are booked through a shared or organization-wide Calendly account, check with whoever manages your Calendly plan before building around this trigger.
Why doesn't the usual 15-minute delay apply to these workflows?
That delay only applies when Flex is the trigger, checking Flex for new data on a polling cycle. In every workflow in this article, Calendly is the trigger, and Flex is the action, so the Create Opportunity step runs as soon as Calendly's instant trigger fires. Other integrations in this series where Flex is on the trigger side still have that delay.