The MeetGeek API lets you push every meeting from an entire team — not just your own — into your CRM, database, or automation tool the moment it finishes analyzing. You do this with team-level webhooks: MeetGeek sends each completed meeting to a webhook URL you register, and with team sharing enabled, that includes meetings from every member of the team. This guide walks through the full setup, including the one detail that trips most people up.
Why team sharing instead of one org-wide API key? A single organization-wide key that could read every meeting in the company would give your automation total visibility — including private or sensitive calls that individual members never meant to expose. Team sharing keeps control with each person: members decide which of their meetings they share with the team, and only shared meetings reach the service account and your automations. You get workspace-wide automation without sacrificing anyone's privacy — nothing flows into an external tool unless its owner opted in by sharing it.
What you need before you start
Team-level automation works on Business and Enterprise plans, which include team creation, team sharing, and API access. Set up these three things once.
Create a service account
Create a dedicated MeetGeek user account for your automation (for example, [email protected]). Using a separate account keeps your automation stable and independent of any one person's login.
Create a team and enable Team Sharing
Go to the Teams page at app.meetgeek.ai/teams.
Create a team and invite your service account, along with every team member whose meetings you want to capture.
On the Team Sharing page, make sure the service account has at least view access to each member's meetings.
Important: Sharing is set per member, not per role. Each team member must have Share permission enabled in the team's sharing rule for their meetings to reach the service account — being an admin makes no difference. Set this on the Team Setup and Sharing page, using an Automated rule (everyone shares) or a Custom rule (tick Share for each member). If a member doesn't have Share enabled, their meetings stay invisible to the service account and won't trigger automation.
Get your API key
Log in as your service account, then go to the Integrations & Automations page at app.meetgeek.ai/integrations. Open the Public API card and copy your API key.
Set up team-level webhooks
Team-level webhooks send every completed team meeting to your automation tool the instant it's processed — ideal for pushing consultation calls into Monday.com, GoHighLevel, or your CRM as soon as they finish.
How team-level webhooks work
When a meeting's analysis completes, MeetGeek sends a POST request to your configured webhook URL with the meeting data in JSON. For meetings shared with a team, the webhook is triggered for every team member who has view access — so your service account receives an event for the whole team's meetings, not just its own.
MeetGeek sends up to three POST requests: your server should respond with an HTTP 200 OK and no body to acknowledge receipt. The second and third requests are sent only as retries if the first isn't acknowledged. For the exact payload fields, see the MeetGeek API Documentation.
Step 1: Get a webhook URL from your automation tool
In Make, add a Custom Webhook module and copy the URL it generates. In Zapier, use Webhooks by Zapier → Catch Hook. In n8n, add a Webhook node and copy its URL.
Step 2: Register the webhook URL in MeetGeek
Log in as your service account.
Go to the Integrations & Automations page and open the Public API card.
Paste your webhook URL into the Webhook URL field.
Click Save to activate it.
Step 3: Build the rest of your scenario
Once the webhook is registered, every completed team meeting will POST its data to your automation tool. From there, map the fields (meeting title, summary, transcript, highlights, action items) to your destination — Monday.com, GoHighLevel, a CRM, or any of the thousands of apps your tool supports.
Why a custom webhook instead of the native trigger? The built-in MeetGeek trigger in Make, Zapier, and n8n (such as Make's "Watch New Meetings" or the equivalent "New Meeting" trigger in Zapier and n8n) only listens to the connecting user's own meetings — it won't pick up other team members' meetings. Registering a webhook URL in the Public API section, combined with team sharing, is what delivers every team meeting to your scenario, whichever tool you use. If you only need a single user's own meetings, the native trigger is fine; for anything workspace-wide, use the webhook.
Need Help?
If you have any questions or need assistance, reach out to us at [email protected] or use the chat messenger in the MeetGeek app.