Skribby

Skribby sends a bot into a Google Meet, Microsoft Teams or Zoom call to record it and transcribe it — after the call, or live over a WebSocket with a realtime model — and also transcribes audio files that never came from a meeting.

Authentication

• API key

Actions

Generic API request. Call any Skribby 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 botSend a Skribby bot to a Google Meet, Microsoft Teams or Zoom meeting to record and transcribe it.
• Delete bot dataDestructivePermanently delete a bot and everything it produced — transcript and recording.
• Delete recording dataDestructivePermanently delete a recording and everything derived from it — the stored file and its transcript.
• Get botRead one bot: its status and stop reason, participants, lifecycle events, the recording link once it has finished, and the full transcript once status is finished.
• Get bot pricingRead what one bot costs: the hourly base rate, the transcription model's rate (and whether your own provider key is used), each add-on's rate, and — once the bot has finished — the final amount charged, in USD.
• Get recordingRead one recording: its transcription status, the link to the original file and when it is deleted, and the transcript once status is finished.
• List scheduled botsList every bot that is scheduled and has not started yet, in full, so you can review, reschedule or call off upcoming bots.
• Stop botDestructiveMake a running bot leave its meeting now.
• Transcribe recordingTranscribe an audio or video file that is not a live meeting — a file at a public URL — or transcribe a bot's recording again with another model or settings.
• Update scheduled botDestructiveChange a scheduled bot before it joins — reschedule it, point it at another meeting, or change its model, name, webhook or stop options.
• Validate bot configurationCheck a bot configuration without creating or starting a bot: the same inputs as skribby:createbot, run through every check Skribby makes — meeting URL format, authenticated account, model and parameters.

Triggers

• Bot status changedStarts when a Skribby bot whose webhookurl points at this trigger changes status — joining, recording, processing, finished with the transcript and recording ready, or not admitted — with the old and new status and, when it stopped, why (statusupdate).

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.