Resources · Make integration

MyMeet.io Make integrationAutomate MyMeet.io with Make.

Can Make pick up your MyMeet.io bookings and pass them to the rest of your tools? The MyMeet.io Make integration offers 1 module, a scheduled trigger called Watch Bookings. This guide is for teams that take meetings through MyMeet.io and shows how to connect the account and build a first scenario around it.

Try the MyMeet.io integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the MyMeet.io Make integration do for you?

The MyMeet.io Make integration lets a Make scenario (the automation you build, a chain of modules) start from your MyMeet.io bookings. It has a single module, Watch Bookings, a trigger that Make checks on the scenario's schedule. Everything that happens after it is done with the modules of your other apps.

A booking log your whole team can read. Watch Bookings sits first, and a spreadsheet module after it adds one row per booking it receives. Sales and support see the same list without opening MyMeet.io.

A heads-up in the team chat. Put a messaging module after the trigger so the person in charge of the meeting gets a note when a booking reaches Make. Nobody has to refresh a calendar to know what is coming.

A contact record that stays current. A CRM module can take the booking and file it against the right person, so account managers prepare the call with context.

Keep expectations realistic. Make states that its documentation for MyMeet.io is limited because little public information exists about the app, and the type of Watch Bookings is inferred from its name rather than confirmed. There is no action module and no Make an API Call module, so MyMeet.io stays a source of data in Make, never a destination. To learn the editor properly, the Make training starts from scratch; to weigh tools, read n8n vs Make; and when a run fails, Make troubleshooting covers the usual causes.

Connect

How do you connect MyMeet.io to Make?

  1. 01

    Open the connection window

    Add the Watch Bookings module to a scenario and click Create a connection. A connection is your MyMeet.io account linked to Make once, then reused by every MyMeet.io module.

  2. 02

    Give it a clear name

    Naming the connection is optional, but a label such as the account owner or the team makes it easy to pick the right one later, especially when several MyMeet.io accounts end up in the same Make organization.

  3. 03

    Authorize and save

    Depending on what MyMeet.io asks for, either approve Make on the MyMeet.io page that opens or paste the key the app gives you. Then click Save and the module is ready to configure.

First scenario

Build your first scenario with MyMeet.io

GoalWhen a booking shows up in MyMeet.io, Make passes it to the app your team already works in.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + in the middle of the editor. This is where the first module, the one that starts everything, will go.

  2. 02

    Add Watch Bookings

    Search for MyMeet.io, pick Watch Bookings and click Create a connection to link your account. Fill in the fields the module shows once the connection exists.

  3. 03

    Choose where bookings go

    Click the + on the right of Watch Bookings and add a module from the app that should receive each booking. Map the booking data into its fields by clicking the values coming from the trigger.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time and shows the bundles each module received, a bundle being one item passed along, here a booking. Check that the data landed where you expected.

  5. 05

    Schedule and switch on

    Open the clock on Watch Bookings: a new scenario runs every 15 minutes by default, and the Free plan cannot go below that. Adjust if needed, then switch the scenario on.

Triggers

What starts a MyMeet.io scenario

1 module starts a scenario when something happens in MyMeet.io. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by MyMeet.io as soon as it happens.

MyMeet.io1Watch Bookings

Watch Bookings

triggerIn the docs only

Watch Bookings gives you the entry point to MyMeet.io in Make: judging by its name, it brings bookings from your account into the scenario so the following modules can act on them. Each booking travels as its own bundle.

How it fires
scheduled, Make checks the app on the scenario's schedule, every 15 minutes by default, with the clock badge on the module.
When to use it
whenever a meeting booked in MyMeet.io should trigger work elsewhere, such as a row, a message or a contact update.
Watch out
the documentation for this app is limited and the scheduled type is deduced from the module name, so confirm with Run once what one bundle actually contains.
Need help

Need help automating MyMeet.io with Make?

A person reads every message.

FAQ

Common questions about MyMeet.io and Make

01Is the MyMeet.io Make integration free?
Yes. MyMeet.io is a standard app in Make, available from the Free plan onward. The Free plan allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes of execution at most and files up to 5 MB. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Each module run on one bundle counts as one operation on your plan, and paid usage is counted in credits per month.
02What do you need to connect MyMeet.io to Make?
A MyMeet.io account and a Make account. Make's documentation lists no prerequisite and no dedicated connection guide for this app, so the generic flow applies: add Watch Bookings, click Create a connection, optionally name it, authorize Make on the MyMeet.io page or paste the key the app provides, then click Save. If the app asks for something unexpected, check its own settings before retrying the connection in Make. Once saved, the same connection serves every scenario that uses MyMeet.io.
03Does the MyMeet.io Make trigger fire instantly?
No. Watch Bookings is treated as a scheduled trigger, a type inferred from its name because the documentation is limited. Make checks MyMeet.io on the scenario's schedule, every 15 minutes by default. On the Free plan the minimum interval is 15 minutes, and on paid plans it can drop to 1 minute. A booking made just after a check is therefore picked up on the following one, not the moment it is created.
04What if the MyMeet.io Make integration lacks the module you need?
It depends on what is missing. The integration has only 1 module, Watch Bookings, and no Make an API Call module, so you cannot write back to MyMeet.io or reach other parts of it from Make. The usual approach is to keep MyMeet.io as the starting point and handle the rest with modules of other apps. For a need the trigger cannot cover, the team at the agency can look at the case with you.
05Make or n8n for MyMeet.io?
It depends on your criteria, and this page only covers Make. In Make, MyMeet.io offers a single scheduled trigger, Watch Bookings, available on the Free plan, with limited documentation. The same app often has an n8n node, so check what that node offers before choosing. Compare the modules each tool gives you for MyMeet.io, the apps you need after it and which editor your team is comfortable with, rather than a general ranking of the two tools.
Same platform

Other docs you might need on this stack.

Browse all integrations