Meety Zapier integrationAutomate Meety with Zapier.
The Meety Zapier integration offers 3 triggers, 1 action and 0 searches. A booking that is made, moved or cancelled can start your automations straight away, and Zapier can also create a booking in Meety from another app. All of it works on the free plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the Meety Zapier integration does for your bookings
The Meety Zapier integration connects Meety, a booking app that puts a scheduling calendar inside your own products, to the rest of your tools. It works in both directions: the life of a booking in Meety (created, rescheduled, cancelled) can start a Zap, and a Zap can create a booking in Meety.
Three setups cover what most teams want from it.
A team that hears about every booking. Booking Created posts each new appointment in your chat channel, so whoever handles it knows without opening Meety. A schedule that stays true elsewhere. Booking Rescheduled and Booking Cancelled each feed a row in your tracking spreadsheet, so the sheet reflects moves and drop-outs as well as new slots. Bookings that start outside Meety. Create Booking turns a request captured in another app into a real booking, as long as that app carries everything Meety asks for.
What Zapier does not do here: it cannot change or cancel a booking, and it cannot look one up, because Meety offers no such action and no search. It does not replay bookings made before your Zap was switched on. And Create Booking needs a full set of details (service, variant, start and end time, the person's name and email, attendees, quantity), so check at the test that your source supplies each one.
The good news on timing: all three triggers are instant, so the plan interval does not slow them down. To weigh platforms, see our Make vs Zapier comparison or our n8n vs Zapier comparison.
Zapier words, explained once
Eight terms come back throughout this page. Here they are in plain words.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap, such as a booking being cancelled in Meety. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, like creating a booking.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan is counted in tasks.
- Polling trigger
- A trigger Zapier checks on a timer, asking the app for new items at a fixed interval. None of the Meety triggers works this way.
- Instant trigger
- A trigger the app reports itself: it calls Zapier the moment the event happens, so nothing waits for a check. All three Meety ones are.
- Filter
- A step that lets the Zap continue only when what arrived meets the condition you set, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter or a second action makes it one, and it then needs a paid plan.
What Meety on Zapier really costs
Meety is not a premium app: every Meety trigger and its action are open on the free plan.
- Premium appNo, open on the free plan
- Free plan100 tasks a month, unlimited two-step Zaps
- BilledEach successful action, never the trigger
- Meety triggersAll instant, no polling interval
A booking that starts a Zap costs nothing by itself, because the trigger never uses a task. Each action that succeeds counts as one task, whether it is Create Booking in Meety or a message in another app; an action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each one limited to two steps: a trigger and a single action. A filter, or a second action, makes the Zap multi-step and needs a paid plan. The interval grid below is how often Zapier checks polling triggers on each plan; it does not apply to the three Meety triggers, which are all instant.
Connect your Meety account to Zapier
- 01
Start from the Apps page
In Zapier, open the Apps page and click + Add connection. A connection is your Meety account linked once to Zapier, then reused by every Zap step that works with Meety.
- 02
Find Meety and add it
Search for Meety by name in the dialog, pick it, then click Add connection. You need a Meety account to link: the one whose bookings the Zap will watch or fill.
- 03
Sign in and grant access
Sign in to Meety in the tab that opens and grant Zapier access to the account. For anything you do not own yourself and want the Zap to touch, you also need read or write access to it.
Your first Zap: tell the team about bookings that matter
GoalEach new Meety booking that passes your filter lands as a message in the team channel. The filter makes it a multi-step Zap, so it needs a paid plan.
- 01
Create the Zap
Start a new Zap, pick Meety as the app that starts it and Booking Created as the event. Select the Meety connection you added earlier.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent bookings of the connected account, so you build the rest from a real booking rather than a guess.
- 03
Add the filter
Click the plus icon and add a Filter step. Fill the three boxes: the field to look at, the rule, the value. A text rule only works on text.
- 04
Add the message
Add your chat tool as the action, pick the channel and map the booking details you saw in the test. Check at the test what each mapped field really holds.
- 05
Test and publish
Test the action once, read what came back, then click Publish. Each matching booking now reaches the channel right away, for one task.
Meety triggers on Zapier
3 events start a Zap when something happens in Meety, and 3 of them are instant: the app calls Zapier straight away, whatever your plan.
Booking Cancelled
Instant triggerIn Zapier“Triggers when a booking is cancelled.”
Starts your Zap when a booking in Meety gets cancelled, so the slot it freed can be dealt with in your other tools.
Booking Created
Instant triggerIn Zapier“Triggers when a new booking is created.”
Fires each time a new booking appears in your Meety account and passes that booking on to the next steps.
Booking Rescheduled
Instant triggerIn Zapier“Triggers when a booking is rescheduled.”
Kicks in when an existing Meety booking moves to a different time, so the change can follow it to the tools where that booking also lives.
Meety action on Zapier
Meety gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Booking
ActionIn Zapier“Create a new booking.”
Books a slot in Meety from another app, filling in the service, the time and the person attending.
When a Meety Zap breaks
Zapier attaches no help article to Meety and no limit specific to the app is on record. The risks come from how Zapier behaves in general, plus the strict fields of Create Booking.
Four cases are worth reading before you publish. Most of them do not look like an error at first: the Zap just does more, or less, than planned. If a Zap still acts up after these checks, see our Zapier troubleshooting guide.
Past bookings are not replayed
A Zap reacts only to what happens after it is switched on. Bookings created, moved or cancelled before that are not picked up; moving them is a separate job.A booking Zap that feeds itself
As a general precaution: a Zap that writes into the place its trigger watches can set itself off again and again, and burn through your tasks.A sudden wave of bookings
If a trigger suddenly sends a huge batch, after a bulk import or a migration for instance, Zapier's flood protection can hold those items back.Create Booking missing a value
Each of the ten fields of Create Booking is marked required. Before publishing, check at the test that the step before it fills every one of them.
Need help automating Meety with Zapier?
A person reads every message.
