24sessions Zapier integrationAutomate 24sessions with Zapier.
The 24sessions Zapier integration gives you 6 triggers, 0 actions and 0 searches. Every one of them is instant: a new booking, a moved or canceled meeting, a fresh review. 24sessions starts the Zap, and another app does the work.
Verified Trustpilot reviews · AI, automation & growth agency
What the 24sessions Zapier integration actually does
It lets 24sessions, the video meeting platform that bundles scheduling, video calls and reviews, kick off automations in your other tools. Each time a meeting is booked, changed, canceled or reviewed, 24sessions warns Zapier and your Zap runs straight away. It only listens: nothing gets written back into 24sessions.
Three results people usually build first. A live booking log: New Booking drops every guest booking into a sheet or a CRM, so sales sees the pipeline without opening the calendar. A cancellation alert: Meeting Canceled pings the account owner, who can call back before the lead goes cold. A review feed: New Review sends each rating to wherever your team reads feedback, rather than leaving it inside 24sessions.
Two other triggers fill the gaps. Meeting Updated catches reschedules, and New Meeting Created by User isolates meetings your own staff set up from the schedule page. New Meeting covers both sources at once.
Now the limits, because they shape everything. Zapier offers no action and no search for 24sessions. A Zap can't create a meeting, cancel one or look one up. If the idea is to book meetings in 24sessions from a form elsewhere, this integration won't do it. It is a one-way street, out of 24sessions.
Before you commit, our Zapier review and the Make vs Zapier comparison are worth a read.
Zapier words in one minute
Seven terms come back all over this page. Here they are in plain English, once.
- Zap
- The automation you build: one trigger, then one or more actions that run every single time that trigger event happens.
- Trigger
- The event that starts a Zap, like a new booking in 24sessions. Once the Zap is switched on, Zapier simply waits for it.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something in another app on your behalf.
- Task
- The unit Zapier bills you for: one action completed successfully. The number on your plan counts these, nothing else.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself, the moment the event happens.
- Filter
- A step that lets the Zap continue only when the data that arrived meets your condition, and quietly stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action, a filter or a search turns it into one, and that needs a paid plan.
What it really costs
The 24sessions side is cheap by design: triggers never cost a task, and all six here are triggers.
- Trigger cost0 tasks, always
- Free plan100 tasks a month, 2 steps per Zap
- Premium appNo, works on the free plan
- Instant triggers6 of 6
You pay for the action that follows. Each successful action counts as one task; a failed one doesn't count. 24sessions is not a premium app, so it works on the free plan: 100 tasks a month, unlimited Zaps, but only two steps per Zap. Add a filter, say to keep only bookings from one form, and the Zap becomes multi-step, which needs a paid plan. The interval grid below applies to polling triggers; all six here are instant, so it doesn't touch you.
Connect your 24sessions account
- 01
Open your Zapier apps
In Zapier, go to the Apps page of your account and click + Add connection. A connection is your 24sessions account linked once, then reused by every Zap that needs it.
- 02
Find 24sessions
Type 24sessions in the search box of the dialog, pick it from the list, then click Add connection. A new browser tab opens on the 24sessions side, where the login happens.
- 03
Sign in and grant access
Log in to 24sessions in that tab and allow Zapier to reach the account. You need your own 24sessions account, plus access to any meetings you don't own but want the Zap to see.
Your first Zap: flag the bookings that matter
GoalEach new guest booking that came through a given booking form lands as a row in a shared sheet, ready for the sales team.
- 01
Create the Zap
Start a new Zap. In the first step, pick 24sessions as the app and
New Bookingas the event. Choose the connection you just added. - 02
Test the trigger
Run the test. Zapier pulls back the three most recent bookings from your account, so you map fields on a real one rather than on blanks. No booking yet? Make one on your own form first.
- 03
Add the filter
Click the plus icon, choose Filter, then set the field to watch, the rule and the value. Pick a text rule for a text field, or the filter will never pass.
- 04
Add the action
Click the plus icon again, pick your sheet app and its row action, then map the booking details your test brought back into the columns.
- 05
Test, then publish
Test each step and read what came back. When the row looks right, click Publish. This Zap has a filter, so it is multi-step and needs a paid plan.
The 6 instant 24sessions triggers
6 events start a Zap when something happens in 24sessions, and 6 of them are instant: the app calls Zapier straight away, whatever your plan.
Meeting Canceled
Instant triggerIn Zapier“Triggers when meeting is canceled.”
Starts your Zap as soon as a scheduled meeting is called off in 24sessions, so the people around that slot hear about it before they show up to an empty call.
New Meeting
Instant triggerIn Zapier“Triggers when you schedule a meeting (via schedule page) or get booked by a guest (via booking forms).”
The broadest of the six. It fires on every new meeting, whether you or a colleague scheduled it from the schedule page or a guest booked it through one of your booking forms.
New Booking on the same destination, or every guest booking lands twice.New Booking
Instant triggerIn Zapier“Triggers when you receive a new booking by a guest (via booking forms).”
Reacts only when an outside guest books a slot through a 24sessions booking form. Meetings your own team schedules are left out, which keeps the signal clean for inbound demand.
New Meeting Created by User
Instant triggerIn Zapier“Triggers when a new meeting is created by 24sessions user (via schedule page).”
The mirror of the booking trigger: it fires only when someone on your 24sessions account creates a meeting from the schedule page, and ignores what guests book themselves.
New Booking or use New Meeting if you want both.Meeting Updated
Instant triggerIn Zapier“Triggers when meeting is updated.”
Fires whenever an existing meeting changes in 24sessions. Think of a reschedule or a time shift: anything that makes the copy you stored elsewhere out of date.
New Review
Instant triggerIn Zapier“Triggers when a new review added.”
Picks up each review a participant leaves in 24sessions after a meeting, and hands it to the next step while the conversation is still fresh in everyone's mind.
When a 24sessions Zap breaks
Zapier lists no help article and no rate limit of its own for 24sessions. What breaks is what breaks on any Zap.
Four cases come up again and again. None of them is specific to 24sessions, and all four are easy to avoid once you know them. If you are stuck on one already, head to our Zapier troubleshooting page.
Old meetings never show up
A Zap only sees what happens after you publish it. Meetings booked before that day stay where they are; copying the history is a separate job.The Zap keeps firing itself
If the action writes into the very place a trigger watches, the Zap sets itself off in a loop and burns through your tasks fast. Keep source and destination apart.A big batch gets held back
After a bulk import or a migration in 24sessions, a sudden flood of events can be paused by Zapier's flood protection before it runs.The filter never lets anything through
Filter rules are typed. A text rule on a number field, or the reverse, never passes. Check the rule type before you blame the trigger.
Need help automating 24sessions with Zapier?
A person reads every message.
