Connect Zapier and Make with meetergo
How to connect Zapier with meetergo: there is no meetergo API key to paste into Zapier, you sign in with your meetergo account instead. Which plan you need, how to reach the Make app, and what Forbidden resource and Unable to pull appointments mean.
Zapier and Make connect meetergo to thousands of other apps: a new booking can create a task, write a row in a spreadsheet, or start a sequence in a tool meetergo has no built-in integration for.
Zapier and Make are included on the Light plan and above, so on every paid plan. They are not available on Free.
There is no meetergo API key to paste into Zapier. You connect by signing in with your meetergo account inside Zapier, the same way you connect Google or Slack there. If a guide tells you to copy an API key from Settings → Integrations → Zapier, that screen does not exist. Which credential the other meetergo tools want is explained in Which credential do I need?.
Connect Zapier
- In meetergo, open Integrations & Apps and find the Zapier tile under Automation. It carries an Admin badge, because the connection applies to the whole account.
- Click More info. The tile has no Connect now button and nothing to configure — it opens zapier.com/apps/meetergo/integrations in a new tab, which is where the connection is actually made.
- In Zapier, create a Zap and pick meetergo as the trigger app.
- When Zapier asks you to connect an account, a meetergo sign-in window opens. Sign in with the email address and password of the meetergo account whose bookings the Zap should see, and confirm access.
- Zapier stores the connection under My Apps. Every later Zap can reuse it.
Being sent to the public Zapier page is the expected behaviour, not an error. meetergo deliberately hands the whole setup over to Zapier — there is nothing left to do on the meetergo side.
The sign-in window asks for an email address and a password. It has no Continue with Google or Continue with Microsoft button, so an account that was created through Google or Microsoft sign-in has no password to enter and the window fails with "Something went wrong. Please try again." Zapier then reports "Authorization access_token missing for meetergo". This cannot be fixed inside Zapier — write to support@meetergo.com and mention that you sign in with Google or Microsoft.
Connect Make
Make works the same way, but the meetergo app is not listed in Make's public app directory. You reach it through the invitation link on the tile:
- Open Integrations & Apps and find the Make tile.
- Click Connect now. It opens Make's app-invitation page for the meetergo app in a new tab.
- In Make, create a scenario, add the meetergo module, and sign in with your meetergo account when Make asks for a connection.
If you would rather not use the meetergo app at all, Make's own Custom webhook module also works: create the webhook in Make, then paste its URL into meetergo as described in Webhooks in meetergo.
What you can automate
The triggers in Zapier and Make are the same events meetergo sends as webhooks: a new appointment, a cancellation, a reschedule, a form submission, and a new user in your account. Webhooks in meetergo documents what each event contains, field by field — that reference is the source of truth for the data your Zap or scenario receives.
Two consequences of that shared plumbing are worth knowing before you build:
- Every connected trigger registers a webhook in meetergo. A Zap or scenario you switch on appears in the Webhooks dialog on the Integrations page and counts towards your webhook limit. Make's app labels its entries with
[MAKE]in the description. - Turning a Zap or scenario off deletes the subscription, so a webhook can vanish from the list on its own, and re-authenticating a connection usually leaves the old entry gone.
How meetergo delivers these events, and what that means for missed or disappearing webhooks, is described in How delivery works.
Testing a trigger
When Zapier asks for sample data, meetergo can supply one only for the new-appointment (booking_created) and new-user (new_employee) triggers, and even then only if your account already has a booking or a user to send. For every other trigger, and for an account with no bookings yet, do a real test instead:
- Leave the trigger listening in Zapier or Make.
- Book a test appointment on one of your own booking pages, or submit the form you want to react to.
- Use the request that arrives to map the fields. The raw payload is what your Zap gets, not what the field picker guesses.
If a meeting type requires confirmation, the booking only exists once the request is confirmed. booking_created fires at that moment, not when the booking form was submitted.
When something does not work
| What you see | What it means |
|---|---|
"Unable to pull appointments" and The app returned "Forbidden resource" | Your meetergo account is not on a plan that includes Zapier, or it was not yet when the connection was made. Check the plan first, then reconnect the meetergo connection in Zapier under My Apps — a connection created while the account was still on Free keeps failing until it is renewed. |
| "User not allowed to use Zapier" | The same cause, reported by meetergo instead of by Zapier: the account behind the connection has no Zapier access. |
| "Something went wrong. Please try again." in the sign-in window, or "Authorization access_token missing for meetergo" | The account signs in with Google or Microsoft and has no password. See the warning above. |
| "Webhook limit reached" when you switch a Zap on | Every Zap and scenario counts against the account's webhook limit. Open the Webhooks tile on the Integrations page and delete entries you no longer need, see Webhooks in meetergo. |
| The Zap ran fine yesterday and receives nothing today | The subscription was deleted, usually because the Zap was switched off, rebuilt or re-authenticated. Turn the Zap on again and check that the webhook is back in the Webhooks dialog. |
| The Zapier tile shows an upgrade dialog instead of opening Zapier | Your account is on Free. The dialog suggests a higher plan, but Light already includes Zapier and Make. |
| You cannot find the Zapier or Make tile at all | Integration permissions hide integrations a team member is not allowed to connect. Ask an admin, or see User roles and permissions: admin rights and who can see what. |
Do you actually need Zapier?
Often not, and the native route is less work:
- Google Calendar, Outlook, Zoom, Teams connect directly on the Integrations & Apps page. Bookings land in your calendar and video links are generated without any automation platform.
- KlickTipp, Brevo, HubSpot, Pipedrive and Salesforce have built-in integrations that write the contact and the appointment data for you.
- Reminders, follow-ups and internal notifications are workflows inside meetergo.
- Your own endpoint can receive the booking directly through a webhook, with no third-party account in between.
Reach for Zapier or Make when the tool you want has no built-in integration and you do not want to build the receiving end yourself.
FAQ
Where do I find my meetergo API key for Zapier?
There is none, Zapier signs in with your meetergo account instead. If you call the meetergo API yourself from a Webhooks by Zapier step, use a Personal Access Token.
Do I need an upgrade for Zapier?
Only if you are on Free. Every paid plan from Light upwards includes Zapier, Make, webhooks and the API.
Do I need Zapier to get bookings into my Google Calendar or into Zoom?
No. Both connect natively on the Integrations page and need no automation platform.
Can a Zap create a booking in meetergo?
The meetergo app in Zapier is built around booking events. If you need to write into meetergo, use the API with a Personal Access Token, for example through a Webhooks by Zapier step.
Can I limit a Zap to one meeting type?
Not in meetergo. Webhooks are always account-wide, so add a filter step in Zapier or Make on meetingType.id. How to Find Your Meeting Type ID shows where to get that value.
Why does my Zap show different field names than I expect?
meetergo sends a fixed payload and has no field mapping. Rename the fields in Zapier or Make, or see the payload reference in Webhooks in meetergo.
Related Articles
Was this article helpful?
Let us know if this article answered your questions.