Meetbot Zapier integrationAutomate Meetbot with Zapier.
The Meetbot Zapier integration gives you 1 action, 2 searches and 0 triggers. Another app starts the automation; Meetbot then looks up a scheduling page or its free slots, and books the meeting on the calendar behind that page.
Verified Trustpilot reviews · AI, automation & growth agency
What the Meetbot Zapier integration is for
The Meetbot Zapier integration lets another tool book meetings for you through a Meetbot scheduling page. Meetbot is a scheduling app, paid per meeting, built for people and for AI agents, that works on Google or Microsoft calendars. On Zapier it never starts anything: it checks availability and books.
A meeting on the calendar. Book Meeting takes a scheduling page, the guest's email and name, and a start time, and books the slot. A lead who fills in your form can end up with a meeting without anyone opening a calendar.
A list of open slots, with links. Find Slots looks up the available times on a scheduling page. Switch on its booking-link option and each slot comes back with a shareable link, ready to send to the person on the other side.
The details of a page. Get Info reads what Meetbot knows about a scheduling page, so the next steps of the Zap can reuse it. What exactly comes back is something to read on your first test.
Now the limits. Meetbot has no trigger on Zapier: a meeting booked directly on a Meetbot page does not start a Zap, so your other tools never hear about it this way. There is no action to cancel or move a meeting either; only booking is on offer. The same app also exists on Make: open our Meetbot Make integration page to compare the two set-ups.
Zapier vocabulary in one minute
Eight words carry this page. One line each, in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap; once the Zap is on, Zapier waits for it. Meetbot has none, so another app provides it.
- Action
- What the Zap does once started: the step that writes, sends or changes something for you, here a booked meeting.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance counts only those.
- Search step
- A step that looks up something that already exists in an app, such as Meetbot's free slots, so later steps can use it.
- Filter
- A step that lets the Zap continue only when what arrived meets the condition you set, and stops it otherwise.
- Polling vs instant trigger
- Zapier checks a polling trigger on a timer; an instant trigger is reported by the app itself the moment the event happens.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A search, a filter or a second action makes it one, and it then needs a paid plan.
What a Meetbot Zap costs on Zapier
Meetbot is not a premium app on Zapier, so it is available on the free plan. Billing happens in tasks, one per action that succeeds.
- Premium appNo, works on the free plan
- Tasks on the free plan100 per month
- Steps per Zap on the free plan2 (one trigger, one action)
- Zap with a Meetbot searchMulti-step, paid plan
The trigger of the other app costs nothing, however often Zapier checks it. Each meeting booked successfully counts one task; a booking that fails is not counted. The catch is the searches: the free plan builds two-step Zaps only, so Find Slots or Get Info in the middle of a Zap makes it multi-step and puts it on a paid plan. The interval grid below only applies when the app that starts your Zap uses a polling trigger; Meetbot has no trigger of its own.
Connect Meetbot to Zapier
- 01
Find Meetbot in your apps
Open the Apps page of your Zapier account and click + Add connection. In the dialog, search for Meetbot by name and select it from the results that appear.
- 02
Sign in on the Meetbot tab
Click Add connection. Meetbot opens in a new tab: sign in with the account that owns your scheduling pages. The connection is then reused by every Zap that calls Meetbot.
- 03
Allow access
Grant Zapier access to the account. If a Zap should book on a scheduling page that belongs to someone else, check first that your account has access to it.
Your first Zap: from a form to a booked meeting
GoalSomeone submits your form, Zapier looks up the free slots on your Meetbot page, then books one of them for that person.
- 01
Start from your form
Create a Zap and pick your form tool with its new-submission trigger. Meetbot cannot start a Zap, so the first card always comes from another app.
- 02
Test with a real submission
Test the trigger: Zapier brings back the three most recent submissions. Keep a real one, so the name and email you map later are real values.
- 03
Look up the slots
Add Find Slots and paste the URL of your scheduling page. This search makes the Zap multi-step, which means a paid plan.
- 04
Book the meeting
Add Book Meeting. Map the page URL, the guest's email and name from the form, and a start time from what Find Slots returned, in ISO 8601 format.
- 05
Test, then publish
Run each step once and check the meeting on the calendar. Then click Publish. Submissions received before that moment are not booked.
Meetbot action on Zapier
Meetbot gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Book Meeting
ActionIn Zapier“Books a new meeting.”
Reserves a slot on one of your Meetbot scheduling pages for a named guest, at the start time you pass. Four fields are required: the page URL, the guest's email, the guest's name and the start time.
2025-08-21T10:19:00.095Z; a plain date will not do.Meetbot searches on Zapier
2 search steps look for data that already exists in Meetbot, so a later step can use it.
A search step does not change anything in Meetbot: it reads, then hands what it found to the steps below. Both searches sit at the bottom of the action-event list in the editor, under SEARCH. Three settings decide what happens when the result is not the expected one.
Get Info
SearchIn Zapier“Gets information about a scheduling page.”
Reads the information Meetbot holds about one scheduling page, from the page URL you give it. Nothing is booked or changed.
Find Slots
SearchIn Zapier“Finds available slots for a meeting.”
Looks up the open times on a scheduling page. With Include Booking Link switched on, each slot also comes with a shareable link you can send to the guest.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap and skips the steps that depended on it. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?This box turns a search into a find-or-create. Meetbot exposes no find-or-create variant on Zapier, so it does not concern these two searches.
- If multiple search results are found?Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When a Meetbot Zap breaks
Zapier links no help article to Meetbot and documents no limit of its own. The weak points are the ones every Zap shares, plus a strict time format.
Read these four cases before you switch the Zap on. If a run still fails, start with our Zapier troubleshooting page.
A start time in the wrong format
Book Meeting expects ISO 8601. Whatever your source sends has to arrive in that shape; check the exact value Book Meeting receives at test, before publishing.No catch-up on the past
A Zap only reacts to what happens after it is published. Requests received before that are not booked; handling them is a separate job.A bulk import held back
If the starting app suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those items back.A Zap that sets itself off
As a general precaution: a Zap that writes where its own trigger looks can start itself again and eat tasks.
Need help automating Meetbot with Zapier?
A person reads every message.
