Agentic Fabriq
Recall.ai
AI · AI
Meeting bots, recordings, and transcripts under the workspace they connected.
Connect Recall.ai with Fabriq Developer
Your user pastes their Recall.ai credential on a page Agentic Fabriq hosts, so it never reaches your backend and never becomes one shared key across all of your users. Same call as OAuth, one more argument.
Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.
Connecting Recall.ai in practice
Recall.ai’s regions are independent deployments: us-west-2, us-east-1, eu-central-1 and ap-northeast-1 each have their own login, their own API key, and resources that cannot be read from another region. Asking for a bot less than 10 minutes before a meeting draws on a limited pool of warm ad-hoc bots, which answers 507 when it is empty.
Scopes that draw scrutiny
Region-local API key (Authorization token)One key per region, created in that region’s dashboard. It can create bots that join and record meetings, and read every recording and transcript in the workspace.Calendar OAuth (Google Calendar or Microsoft Outlook)Calendar V2 connects a user’s calendar so bots can be scheduled automatically, which means Recall holds a calendar grant on top of the meeting recordings.Webhook and callback HMAC signatureRecall signs webhooks, websocket and callback requests with an HMAC, and an unverified receiver will accept forged transcripts.
Rate limits
- Per workspace, per endpoint: Create Bot 120 requests/min, List Bots 60 requests/min.
- Retrieve Bot, Update Scheduled Bot, Delete Bot, Delete Bot Media, Remove Bot From Call and the bot output endpoints: 300 requests/min each.
- Ad-hoc bots (join_at under 10 minutes out, or omitted) share a warm pool; depletion returns 507 and Recall suggests retrying every 30 seconds.
- There is no limit on concurrent bots in meetings scheduled more than 10 minutes in advance; the 30-concurrent figure applies to ad-hoc bots only.
Worth knowing
- Default retention depends on when the account was created: before 12 June 2025 recording media expires after 7 days, after that date it is kept forever unless recording_config.retention sets a timed or forever policy.
- Storage is billed at $0.000069 per recording-hour per hour once media has been stored more than 7 days, which is about $0.05 per recording hour per 30 days — so "retain forever" is a running cost.
- api.recall.ai is an alias for us-east-1 only, so code that hardcodes it silently talks to the wrong region for an EU or APAC workspace.
- Moving a pay-as-you-go workspace to another region means creating a new account there; only monthly-plan customers can have a region added.
- Bots are single-use and each runs on its own machine, so "reuse the bot for the next meeting" is not a thing the API offers.
Checked against Regions and base URLs (2026-09-29), Creating and scheduling bots (2026-09-29), Storage and data retention (2026-09-29), Create Bot reference (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Recall.ai behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.