Resources · Make integration

Meetbot Make integrationAutomate Meetbot with Make.

Can Make book a Meetbot meeting for you while you do something else? The Meetbot Make integration gives you 5 action modules and no trigger. This page is for the person who runs the calendar side of a team: connect the account, build a first scenario, then pick the right module.

Try the Meetbot integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Meetbot Make integration let you automate?

The Meetbot Make integration links your Meetbot account to Make, a no-code tool where you build a scenario (the automation itself: a chain of modules that runs on a schedule or when an app calls Make). Each module is one brick of that chain, and the Meetbot ones book meetings and read scheduling pages for you.

Turn a request into a booked meeting. A lead fills in a form in another app, Get availability slots asks Meetbot what is open, and Book a meeting takes one of those slots. Nobody copies an email address by hand.

Keep an inventory of your booking pages. Get scheduling pages brings back the pages of the account, and Get scheduling page info opens one of them, so a sales ops lead can push that information into a sheet or a CRM.

Reach what the list leaves out. Make an API call sends your own request to Meetbot with the same connection, for anything the four named modules do not cover.

One honest limit: Make says its own Meetbot documentation is incomplete, because little public information exists about the app. Test every module with Run once before you trust it, and keep the Make troubleshooting guide nearby. The same app often has an n8n node too; the n8n vs Make comparison lays out the criteria, and the Make training covers the editor from zero.

Connect

How do you connect your Meetbot account to Make?

  1. 01

    Add a Meetbot module

    In a scenario, click the + and search for Meetbot, then pick any of its modules. Make asks for a connection, meaning your Meetbot account linked once and reused by every Meetbot module. Click Create a connection.

  2. 02

    Name the connection

    Giving it a name is optional, but it pays off the day a second Meetbot account shows up, for example one per team. Pick a label that tells you which account sits behind it at a glance.

  3. 03

    Authorize Make and save

    Either approve Make on the Meetbot page that opens, or paste the key Meetbot gives you, depending on what the window asks. Then click Save, and the connection appears in the module.

First scenario

Build your first scenario with Meetbot

GoalWhen a new request lands in another app, Make reads the open Meetbot slots and books a meeting.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since Meetbot has no trigger, start with the app that receives the request, such as your form tool.

  2. 02

    Add Get availability slots

    Click the + on the right of that first module, search for Meetbot and pick Get availability slots. Choose your connection, then fill the fields; Make lists what it can read once the account is linked.

  3. 03

    Add Book a meeting

    Add Book a meeting after it and map the data. You will most likely take the contact from the first module and a slot from the second; the exact fields only show up after a test. Each item passing between modules is called a bundle.

  4. 04

    Test with Run once

    Click Run once to run the scenario one time. Open each module's bubble to read the bundles it received, and confirm the meeting really shows up on the Meetbot side.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default), then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Modules

What Meetbot can do in Make

Meetbot gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Meetbot1

Book a meeting

ActionIn the docs only

This is the module that puts a meeting on the calendar without anyone opening Meetbot. Make gives no official description of it, so the name is your guide, and a test run shows exactly what it expects.

When to use it
at the end of a flow, once a request has been approved and a slot has been picked earlier in the scenario.
Watch out
a booking reaches a real person, so run it on your own address with Run once before switching on.
Meetbot2

Get availability slots

ActionIn the docs only

You get the open times Meetbot can offer, ready to pass to the next module. Placing it right before a booking keeps the scenario from aiming at a time that is already taken.

When to use it
when an inbound request should land on a real free slot rather than a guessed one.
Watch out
Make publishes no description or limit for it; read the bundles after Run once to see what comes back.
Meetbot3

Get scheduling page info

ActionIn the docs only

Pick one scheduling page and this module brings back what Meetbot holds about it. That is handy when a later step needs details from a single booking page instead of the whole list.

When to use it
after Get scheduling pages, to zoom in on the one page a scenario is about.
Watch out
the documentation names no field, so map only what you saw in a test bundle.
Meetbot4

Get scheduling pages

ActionIn the docs only

Here you receive the scheduling pages of the connected account in one go. It suits a team that wants a shared view of its booking links, pushed into a sheet or a CRM record.

When to use it
when a scenario needs to know which pages exist before it reads or books anything.
Watch out
Make does not say whether this returns one bundle or several, so check with Run once before adding the next module.
Meetbot5

Make an API call

ActionIn the docs only

With this module you can reach any endpoint of the Meetbot API while reusing the connection you already created. It is the way out when none of the four named modules does what you need.

When to use it
only after checking that no dedicated module covers the task, since a dedicated one is simpler to fill.
Watch out
you write the request yourself, so you need the Meetbot API reference at hand.
Need help

Need help automating Meetbot with Make?

A person reads every message.

FAQ

Questions about Meetbot and Make

01Is the Meetbot Make integration free?
Yes, Meetbot is a standard app in Make, so it works on the Free plan, which also includes the 3,000+ other standard apps. The Free plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and allow unlimited active scenarios. Usage is counted in operations, one per module run on a bundle.
02What do you need to connect Meetbot to Make?
A Meetbot account and a Make account. The Make documentation lists no prerequisite for this app. In any Meetbot module, click Create a connection, give it a name if you like, authorize Make on the Meetbot page or paste the key Meetbot provides, then click Save. That single connection is then reused by all five Meetbot modules, including Make an API call. If something blocks at that stage, the documentation is limited, so the Make troubleshooting guide is the next stop.
03Can a Meetbot scenario start on its own without a trigger?
Yes, even though Meetbot has no trigger module. You have two ways to start. Put a trigger from another app first, for example a form or a CRM that receives the request, and add the Meetbot modules after it. Or open the scenario directly on a Meetbot module and let the schedule on that first module start it, every 15 minutes by default, or every minute at the lowest on a paid plan. A scheduled start is not real time: it runs at the interval you set.
04What if the Meetbot module you need is missing in Make?
Use Make an API call. It sends a request to any endpoint of the Meetbot API with the connection you already have, so it covers what Book a meeting, Get availability slots, Get scheduling page info and Get scheduling pages leave out. You will need the Meetbot API reference to write it. Keep in mind that Make describes its own Meetbot documentation as limited, because public information about the app is scarce, so test every module with Run once before switching the scenario on.
05Should you use Make or n8n for Meetbot?
It depends on where your other automations already live. Make offers five Meetbot modules, one of them an open API call, inside a visual editor where each module is a bubble and Run once tests the whole chain. The same app often has an n8n node as well. If your team already builds in one of the two tools, keeping Meetbot there avoids a second set of connections. The n8n vs Make comparison lays out the criteria without ranking the two.
Same platform

Other docs you might need on this stack.

Browse all integrations