Skip to main content
MeetingKit records a meeting once it knows about it. There are three ways to tell it, and you don’t need all of them. We recommend connecting calendars, plus a “Send bot to meeting” button. Your users connect their calendar once, and every meeting on it follows their recording choices. The button covers the calls that are on no calendar.
Six ways in, one card each: 1 connect calendars on MeetingKit's consent screen (POST /calendar_connect_links); 2 the same connect link under your brand, coming soon; 3 push calendar events you already sync (POST /calendar_events); 4 a directory connection for Google Workspace or Microsoft 365, coming soon; 5 send bots to a meeting link (POST /bots); 6 invite by email to bot@meetingkit.com, coming soon.
Use one calendar source per workspace: connected calendars or pushed events, not both. A call that arrives from both becomes two meetings, and only one of them gets the recording. Whichever way a meeting gets in, it is the same meeting, with the same results.

​
Coming soon

  • Connect calendars under your brand. The same connect link, through your own Google or Microsoft app: the consent screen shows your product’s name instead of MeetingKit’s. You register a calendar-only app once and give MeetingKit its credentials; MeetingKit still runs the consent, the tokens and the sync.
  • Directory connection, Google and Microsoft. A customer’s admin connects the whole company in one step: a Google Workspace domain or a Microsoft 365 tenant. MeetingKit reads the directory and creates a member and a calendar connection for each person, with no click from each user, and keeps up with joiners and leavers.
  • Invite by email. A user adds the notetaker’s address, such as bot@meetingkit.com, to a meeting invite, and it joins. No calendar to connect.