rocketkind
Productivity

Recall.ai

Recall.ai sends a bot into a Zoom, Google Meet, Microsoft Teams, Webex or GoTo Meeting call to record and transcribe it, and keeps the recording, transcript and participant data for you to read afterwards.

Authentication

  • API key

Actions

Generic API request. Call any Recall.ai 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.

  • Create async transcriptTranscribe a finished recording after the call with the provider you choose.
  • Create botSend a Recall.ai bot to a video meeting (Zoom, Google Meet, Microsoft Teams, Webex, GoTo Meeting) to record it and, when a transcript provider is configured, transcribe it.
  • Create calendarConnect a user's Google Calendar or Microsoft Outlook calendar to Recall from an OAuth refresh token your own OAuth application obtained, so Recall syncs its events (calendar.syncevents) and you can schedule bots on them.
  • Delete bot mediaDestructivePermanently delete everything Recall stored for a bot — its recordings, video, audio, transcripts and participant data — while keeping the bot record itself.
  • Delete calendarDestructiveDisconnect and delete a Calendar V2 calendar, so Recall stops syncing its events.
  • Delete recordingDestructivePermanently delete a recording and every media artifact under it (video, audio, transcripts, participant events, meeting metadata) from Recall.
  • Delete scheduled botDestructiveCancel a scheduled bot that has not yet joined its call, so it never joins.
  • Get botRead one bot: its configuration, the statuschanges history that says where it is in its lifecycle (and the subcode when it failed), and the recordings it produced with their mediashortcuts — the quickest way to the transcript and video download URLs once the bot is done.
  • Get calendarRead one Calendar V2 calendar — after a calendar.update event, to see whether it is still connected and, if not, why (statuschanges).
  • Get calendar access tokenGet a current OAuth access token for a connected calendar's Google or Microsoft account, minted by Recall from the stored refresh token, so a workflow can call the calendar provider's own API without running its own refresh.
  • Get calendar eventRead one synced calendar event, including the bots scheduled on it and the provider's raw event (attendees, organizer, description).
  • Get meeting metadataRead one meeting metadata artifact: its status, the recording and bot it belongs to, and its data.
  • Get mixed audioRead one mixed audio artifact: its status, the recording and bot it belongs to, and its data.
  • Get mixed videoRead one mixed video artifact: its status, the recording and bot it belongs to, and its data.
  • Get participant eventsRead one participant events artifact: its status, the recording and bot it belongs to, and its data.
  • Get recordingRead one recording, including mediashortcuts with the transcript, mixed video, mixed audio, participant events and meeting metadata artifacts and each one's data.downloadurl.
  • Get separate audioRead one separate audio artifact: its status, the recording and bot it belongs to, and its data.
  • Get separate videoRead one separate video artifact: its status, the recording and bot it belongs to, and its data.
  • Get transcriptRead one transcript artifact: its status, the recording and bot it belongs to, and its data.
  • List botsList the bots in this Recall workspace, newest first, with each bot's id, name, join time, status history and recordings.
  • List calendar eventsList the events Recall synced from one Calendar V2 calendar, each with its start and end time, meeting URL and platform, the bots scheduled on it, and isdeleted for events removed from the calendar.
  • List calendarsList the Calendar V2 calendars connected to this Recall workspace, each with its account email, platform and connection status.
  • List Desktop SDK uploadsList the uploads made by the Desktop Recording SDK in this workspace, each with its status and the recordingid it produced once complete — the bridge from a desktop recording to recall:getrecording.
  • List meeting metadataList the meeting metadata artifacts in this Recall workspace, each with its status and download URL.
  • List mixed audioList the mixed audio artifacts in this Recall workspace, each with its status and download URL.
  • List mixed videoList the mixed video artifacts in this Recall workspace, each with its status and download URL.
  • List participant eventsList the participant events artifacts in this Recall workspace, each with its status and download URL.
  • List recordingsList recordings in this Recall workspace — one per stretch a bot recorded, or per Desktop SDK upload — with each one's status and mediashortcuts.
  • List separate audioList the separate audio artifacts in this Recall workspace, each with its status and download URL.
  • List separate videoList the separate video artifacts in this Recall workspace, each with its status and download URL.
  • List transcriptsList the transcript artifacts in this Recall workspace, each with its status and download URL.
  • Output mediaMake the bot render a live webpage as its camera or screenshare — the way an interactive meeting agent shows a face or a shared screen that can also hear and speak through the page.
  • Output screenshareShow a still JPEG image on the bot's screenshare in the meeting — a logo, a slide, a status card.
  • Output videoShow a still JPEG image on the bot's camera in the meeting — a logo, a slide, a status card.
  • Pause recordingDestructivePause the bot's current recording — for an off-the-record stretch — without ending it; recall:resumerecording continues the same recording.
  • Pin participantDestructivePin one participant's video in the bot's separate H.264 video stream, or unpin whoever is pinned by leaving participantId out.
  • Play audio in callMake the bot play an MP3 clip into the meeting — a spoken notice or an agent's reply, for example the file a text-to-speech action produced.
  • Remove bot from calendar eventDestructiveUnschedule the bot from a synced calendar event — when the user opts out of recording or the meeting was cancelled — so it does not join.
  • Remove bot from callDestructiveMake a bot leave the meeting it is in now.
  • Resume recordingDestructiveResume a recording that recall:pauserecording paused, continuing the same recording.
  • Schedule bot for calendar eventSchedule a Recall bot to join a synced calendar event's meeting, configured like recall:createbot — meeting URL and join time default to the event's.
  • Send chat messagePost a message in the meeting chat as the bot — a recording notice, a link, an agenda — while it is in the call.
  • Start recordingDestructiveTell a bot that is in the call to start recording now, with the recording settings given here — or restart the recording, closing the current one, if it is already recording.
  • Stop audio outputDestructiveStop the audio the bot is currently playing into the meeting, for example to cut off a clip when someone starts talking.
  • Stop media outputDestructiveStop the webpage the bot is rendering on its camera, its screenshare, or both.
  • Stop output screenshareDestructiveStop showing the image on the bot's screenshare.
  • Stop output videoDestructiveStop showing the image on the bot's camera.
  • Stop recordingDestructiveTell a bot to end its current recording while staying in the call.
  • Update calendarDestructiveUpdate a Calendar V2 calendar in place — typically to hand Recall a fresh refresh token after the user re-authorized, which reconnects a disconnected calendar, or to change its metadata.
  • Update scheduled botDestructiveChange a scheduled bot before it joins its call — move its join time, point it at a different meeting URL, rename it or change what it records.

Triggers

  • Artifact status changedStarts on any status change of a recording or one of its media artifacts — transcript, participant events, meeting metadata, mixed or separate video and audio — processing, done, failed or deleted.
  • Bot breakout room changedStarts when a Zoom bot enters or leaves a breakout room, or — for a bot in the main room with participants choosing rooms — a breakout room opens or closes.
  • Bot doneStarts when a bot has shut down and its recording is uploaded (bot.done) — the point at which the recording's media and transcript can be read with recall:getbot or recall:getrecording.
  • Bot failedStarts when a bot hits an error that shuts it down (bot.fatal) — usually it could not join the call; data.data.subcode says why.
  • Bot status changedStarts on every bot lifecycle step — joining the call, waiting room, recording permission allowed or denied, recording, call ended, done, fatal — with the new status code and subcode.
  • Calendar events changedStarts when events on a Calendar V2 calendar were created, updated or deleted (calendar.syncevents).
  • Calendar updatedStarts when a Calendar V2 calendar's state changes (calendar.update) — most often when it disconnects because the user revoked access.
  • Live meeting audioStarts when a Recall.ai bot joins its call and streams the meeting's mixed audio into the workflow as it is spoken.
  • Live partial transcriptStarts for each interim, not yet final, transcript result while the meeting is running (transcript.partialdata) — for live captions.
  • Live participant eventStarts on in-call participant activity while the meeting is running — join, leave, details updated, speech, webcam and screenshare on or off, and chat messages (data.data.data.text).
  • Live transcript utteranceStarts for each finalized utterance while the meeting is running (transcript.data), with the words, timings and speaking participant.
  • Recording doneStarts when a recording finishes processing (recording.done) and all of its media artifacts can be read — the recording id is data.recording.id.
  • Recording failedStarts when a recording could not be captured (recording.failed); data.data.subcode says why.
  • Transcript doneStarts when a transcript finishes (transcript.done) — from realtime transcription after the call or from recall:createtranscript — so it can be read with recall:gettranscript using data.transcript.id.
  • Transcript failedStarts when a transcript could not be produced (transcript.failed); data.data.subcode says why, for example providerconnectionfailed when the third-party provider rejected the request.

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.