rocketkind
Productivity

Meeting BaaS

Meeting BaaS sends a bot into a Zoom, Google Meet or Microsoft Teams call to record it, transcribe it, stream its audio or live transcript, and hand back the recording and transcript afterwards.

Authentication

  • API key

Actions

Generic API request. Call any Meeting BaaS API endpoint on this connection, for the case where no shipped action covers it yet. The connection supplies the base URL, the authentication and the egress route, so only the path, query and body are yours to fill.

  • Cancel calendar botDestructiveCancel the bots scheduled for a calendar event instance or for every occurrence of its series.
  • Cancel scheduled botDestructiveCancel a scheduled bot so it never joins its meeting.
  • Connect calendarConnect a Google or Microsoft calendar so Meeting BaaS syncs its events and can send bots to their meetings, using your own OAuth application's client and a user's refresh token.
  • Create botSend a Meeting BaaS bot into a Zoom, Google Meet or Microsoft Teams meeting now to record it, and optionally transcribe it, stream its audio or live transcript to your WebSocket, or call you back when it finishes.
  • Create bots in batchSend several bots into meetings in one call, each with its own configuration (the same fields as meetingbaas:createbot).
  • Create Meet loginAdd a Google account of a Meet SSO workspace that authenticated Meet bots can sign in as, optionally in an email group bots draw from round-robin (meetConfig.emailgroup on createbot).
  • Create Meet workspaceRegister a Google Workspace domain for authenticated Google Meet bots via SAML SSO, with a signing keypair Meeting BaaS generates or one you supply.
  • Create scheduled botSchedule a bot to join a meeting at a set time (up to 90 days ahead), with the same recording, transcription, streaming and callback options as meetingbaas:createbot.
  • Create scheduled bots in batchSchedule several bots in one call, each with its own join time and configuration.
  • Create Teams loginAdd a Microsoft 365 account (email and password) of a Teams workspace that authenticated Teams bots sign in as — the bot then shows that account's name and picture — optionally in an email group bots draw from.
  • Create Teams workspaceRegister a Microsoft 365 domain whose accounts authenticated Microsoft Teams bots sign in with.
  • Create Zoom credentialStore a Zoom OAuth credential — your Zoom app's client, plus a user's authorization code for a user credential — so bots can join Zoom meetings authenticated (zoomConfig.credentialid on createbot).
  • Delete bot dataDestructivePermanently delete a finished bot's recordings, transcription and other artifacts from Meeting BaaS, and by default from the transcription provider too.
  • Delete Meet loginDestructiveRemove a Google Meet login from the pool authenticated Meet bots sign in with.
  • Delete Meet workspaceDestructiveDelete a Google Meet SSO workspace and every Meet login under it.
  • Delete Teams loginDestructiveRemove a Microsoft Teams login from the pool authenticated Teams bots sign in with.
  • Delete Teams workspaceDestructiveDelete a Microsoft Teams workspace and every Teams login under it.
  • Delete Zoom credentialDestructiveDelete a stored Zoom credential; bots configured with it can no longer join authenticated.
  • Disconnect calendarDestructiveDisconnect a calendar: Meeting BaaS stops syncing it and removes its events and their scheduled bots.
  • Get botRead one bot in full once it has run: status, participants and speakers, duration, token usage, and signed download URLs for its video, audio, transcription, raw transcription, diarization and chat messages (valid for 4 hours; read the bot again for fresh ones).
  • Get bot statusRead only where a bot is in its lifecycle (queued, joiningcall, incallrecording, completed, failed, …) and the status of its transcription — a light check when the full bot details are not needed.
  • Get calendarRead one calendar connection: its status and status message, webhook subscription and expiry, and the result of its last sync.
  • Get calendar eventRead one calendar event in full: description, location, organizer, attendees and their responses, meeting URL, whether a bot is scheduled, and the provider's raw payload.
  • Get Meet loginRead one Google Meet login: workspace, email, email group, state and active sessions.
  • Get Meet login utilizationRead how busy the Google Meet login pool is: logins total, active and invalid, concurrent sessions against capacity, and the same per email group — to see whether authenticated Meet bots will find a free login.
  • Get Meet workspaceRead one Google Meet SSO workspace: domain, certificate, state and last error.
  • Get scheduled botRead one scheduled bot's full configuration, join time and schedule status.
  • Get storage configurationRead the account's bring-your-own-storage configuration — the S3-compatible endpoint, region and buckets Meeting BaaS writes recordings to, the access key ids (never the secrets) and when it was last verified.
  • Get Teams loginRead one Microsoft Teams login: workspace, email, email group, state and active sessions.
  • Get Teams login utilizationRead how busy the Microsoft Teams login pool is: logins total, active and invalid, concurrent sessions against capacity, and the same per email group.
  • Get Teams workspaceRead one Microsoft Teams workspace: domain, state and last error.
  • Get Zoom credentialRead one stored Zoom credential: its type, Zoom identity, scopes, state and last error.
  • List bot screenshotsList the screenshots a bot captured while it was in the meeting, each with a download URL — useful to see why a bot was stuck in a waiting room or failed to join.
  • List botsList this account's bots, newest first, with their meeting, platform, current status, timing, token usage and extra metadata — filtered by name, participant, meeting, platform, status, creation window or extra metadata.
  • List calendar eventsList a connected calendar's event instances with their title, times, meeting URL and platform, seriesid and whether a bot is scheduled — filtered by date window and status.
  • List calendarsList this account's calendar connections with their platform, account email, connection status and last sync, filtered by email, platform or status.
  • List event seriesList a connected calendar's event series — one per one-off meeting or recurring meeting — each with its event instances.
  • List Meet loginsList this account's Google Meet logins with their workspace, email group, state and active session count, optionally filtered by extra metadata.
  • List Meet workspacesList this account's Google Meet SSO workspaces with their domain, certificate and state, optionally filtered by extra metadata.
  • List provider calendarsPreview the Google or Microsoft calendars an OAuth refresh token can reach, before connecting one — each with the id meetingbaas:createcalendar takes as rawCalendarId, its name, email and whether it is the primary calendar.
  • List scheduled botsList this account's scheduled bots with their meeting, join time and schedule status, filtered by join window, status, platform, name, meeting or extra metadata.
  • List Teams loginsList this account's Microsoft Teams logins with their workspace, email group, state and active session count, optionally filtered by extra metadata.
  • List Teams workspacesList this account's Microsoft Teams workspaces with their domain and state, optionally filtered by extra metadata.
  • List Zoom credentialsList this account's stored Zoom credentials with their type, Zoom identity, scopes and state, filtered by name, Zoom email, display name, user ID, type, state or extra metadata.
  • Pause recordingDestructivePause a bot's recording while it stays in the meeting, optionally announcing it in the chat; nothing is recorded until meetingbaas:resumerecording.
  • Remove bot from meetingDestructiveMake a bot leave its meeting now.
  • Remove storage configurationDestructiveRemove the account's bring-your-own-storage configuration so new recordings go back to Meeting BaaS storage.
  • Resend final webhookSend a finished bot's final webhook (bot.completed or bot.failed) to every webhook endpoint of the account again, with the same payload as the original — for when the first delivery was missed.
  • Resubscribe calendarRenew the push-notification subscription Meeting BaaS holds on a calendar with Google or Microsoft — for a connection whose subscription expired and stopped receiving changes.
  • Resume recordingDestructiveResume a bot's paused recording, optionally announcing it in the chat.
  • Retranscribe botTranscribe a finished bot's recording again, for example after a transcription failure or with a different provider configuration; the new transcription consumes tokens and arrives as a fresh bot.completed.
  • Retry callbackSend a finished bot's callback again, to the URL in its callbackconfig or to one you give here, with a freshly generated payload and new signed URLs — for when all four automatic attempts failed.
  • Schedule calendar botSchedule a bot for a calendar event — one instance (eventId) or every future occurrence of its series (allOccurrences) — with the same configuration options as meetingbaas:createbot; Meeting BaaS follows the event if it moves.
  • Send chat messagePost a message in the meeting chat as the bot, which must be in the call.
  • Set storage configurationDestructivePoint the account's recordings, audio chunks and logs at your own S3-compatible buckets, replacing any previous configuration; Meeting BaaS checks it can use them before saving.
  • Sync calendarRe-read a calendar's events from Google or Microsoft now instead of waiting for the provider's push notifications.
  • Test storage configurationCheck that Meeting BaaS can still write to and read from the configured buckets with the stored keys; body.data.ok says whether it can and body.data.error why not.
  • Update bot metadataDestructiveMerge new keys into the extra metadata of an existing bot, even while it is in the meeting — keys you send are added or overwritten, the rest are kept.
  • Update calendar botDestructiveChange the configuration of bots already scheduled for a calendar event instance or a whole series.
  • Update calendar credentialsDestructiveReplace a calendar connection's OAuth client and refresh token — the fix for a connection that went to error or revoked.
  • Update Meet loginDestructiveRename a Google Meet login, move it to another email group, reactivate it, or change its extra metadata.
  • Update Meet workspaceDestructiveRename a Google Meet SSO workspace, rotate its keypair, reactivate it after a failure, or change its extra metadata.
  • Update scheduled botDestructiveChange a scheduled bot before it joins — its join time, meeting, name or any configuration.
  • Update Teams loginDestructiveRename a Microsoft Teams login, change its password or email group, reactivate it, or change its extra metadata.
  • Update Teams workspaceDestructiveRename a Microsoft Teams workspace, reactivate it after a failure, or change its extra metadata.
  • Update Zoom credentialDestructiveRename a stored Zoom credential, replace its client, re-authorize it with a new authorization code, or change its extra metadata.

Triggers

  • Bot callback receivedStarts when Meeting BaaS calls back about one bot you created with a callback — bot.completed with its recording URLs, or bot.failed with the reason.
  • Bot completedStarts when a bot has left its meeting and finished processing (bot.completed), carrying the participants, speakers, duration and signed download URLs for the video, audio, transcription and diarization — valid for 4 hours; read the bot again with meetingbaas:getbot for fresh ones.
  • Bot failedStarts when a bot ends without a recording (bot.failed) — refused entry, timed out, out of tokens, removed from the meeting — with a machine-readable errorcode and a human-readable errormessage.
  • Bot status changedStarts on every step of a bot's lifecycle (bot.statuschange) — queued, joiningcall, inwaitingroom, incallrecording, callended, transcribing and the rest — with the new status code and when it changed.
  • Calendar connectedStarts when a calendar connection is created (calendar.connectioncreated), with its platform, account email and status.
  • Calendar connection errorStarts when a calendar connection runs into an error (calendar.connectionerror) — typically a failed OAuth token refresh — with the error text.
  • Calendar connection updatedStarts when a calendar connection changes (calendar.connectionupdated) — new credentials, or a status change such as active to revoked — with its new status.
  • Calendar disconnectedStarts when a calendar connection is deleted (calendar.connectiondeleted); its events and calendar bots are gone with it.
  • Calendar event cancelledStarts when an event in a connected calendar is cancelled (calendar.eventcancelled), with the cancelled instances.
  • Calendar event createdStarts when an event is added to a connected calendar (calendar.eventcreated), with its series and instances — title, times, meeting URL and platform — so a bot can be scheduled for it.
  • Calendar event updatedStarts when an event in a connected calendar changes (calendar.eventupdated), with the instances affected — moved times, a changed meeting link — and whether bots are scheduled on them.
  • Calendar events syncedStarts when a calendar's first sync completes (calendar.eventssynced), carrying every synced event series with its instances, meeting URLs and whether a bot is scheduled — the point to schedule bots on a newly connected calendar.
  • Chat message receivedStarts the moment a meeting participant posts in the chat of a meeting a bot is in (bot.chatmessage), with the sender and the text.
  • Live meeting audioStarts when a Meeting BaaS bot joins its call and streams the meeting's audio into the workflow as it is spoken.

Product names, logos and brands are the property of their respective owners and are used here for identification only. Their use does not imply endorsement by, or affiliation with, those owners.