Create a Google Calendar event when a new Exly booking is received

Every new booking in Exly becomes an event in the Google Calendar you choose, built from the booking details Exly sends, so your coaching sessions and classes sit alongside the rest of your schedule.

Exly

Google Calendar

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 1.3k sites Free to import

The Create a Google Calendar event when a new Exly booking is received workflow on the FlowMattic canvas, with 2 steps across Exly, Google Calendar — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Creators and coaches who sell sessions on Exly often plan the rest of their week in Google Calendar. Copying each booking across by hand is easy to forget, and a missed entry means a double-booked hour. This workflow adds the booking to your calendar when it comes in.

The Exly trigger, Booking Received, fires when a new booking arrives in your Exly account. FlowMattic passes the booking data on, and the Google Calendar step, Create Detailed Event, creates an event from the values you map, in the calendar you pick.

One Exly booking leads to one new calendar entry. The workflow does not update or remove the event if the booking changes later, so treat the calendar entry as a copy made at booking time. Send one test booking after import to see which fields Exly provides, such as the customer and the session time, before you map the event's start and end.

One-to-one coaching calls

A client books a coaching slot on Exly and the call appears in the Google Calendar you use for client work, next to your other appointments.

Fitness or yoga classes

Each class booking adds an event to a studio calendar, giving the instructor a running view of who booked into which session.

Consultations for a small agency

Paid consultations booked through Exly show up on a shared team calendar, so whoever takes the call can see it there.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Exly Booking Received
Runs when a new booking is received in your Exly account. The booking details are passed on for mapping into the calendar event.
Step 2Action
Google Calendar Create Detailed Event
Creates an event in the Google Calendar you choose from the Exly booking values you map. Connect your Google account on import and check a test booking to confirm the times come through correctly.

What you need

FlowMatticCore
Exly AccountAccount
Google Calendar AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Put the customer's name and the offering title into the event summary, so each calendar entry tells you who booked and what for.
Use a calendar set aside for Exly bookings, so you can show or hide them as a group in Google Calendar.
Add a Gmail or Email step after the calendar step if you want your own note each time a booking lands.

Questions about this workflow

Does a cancelled Exly booking remove the Google Calendar event?

No. The template only reacts to new bookings and creates events. Removing or changing an event would need another workflow and an Exly event that reports the change.

Will older Exly bookings be added to my calendar?

No. Only bookings received after you turn the workflow on start a run, so earlier bookings stay off the calendar unless you add them yourself.

Do I need a Google Workspace account for the calendar step?

No. Any Google account you can connect works, as long as it can edit the calendar you pick in the Create Detailed Event step.

What if Exly sends the session time in a different time zone?

Check a test booking in Task History and compare it with the event in Google Calendar. If the hour is off, adjust how you map the time before you rely on the workflow.