Niches · Meeting capture & meeting infrastructure
Record every qualifying meeting on a user's calendar without being asked each time
Two or three companies' docs show a full fit.
What counts as done
After one calendar connection, a bot is scheduled for each future event that matches the rules, updated or cancelled when the event moves or is switched off, with no duplicate bot for a shared event, on a plan the docs name.
How agents ask for it: record all my customer calls
, join my meetings with external guests automatically
, stop recording my 1:1s
Does the job 2
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Nylas Notetaker API BB Nylas, Inc. | Calendar sync takes event_selection and participant_filter rules, reschedules or cancels bots as events change, allows per-event override, and deduplication_policy sends one bot for teammates' shared meeting. Pricing names bot hours and connected accounts per plan, Free included. source |
| Recall.ai B Hyperdoc Inc. | Calendar V1 schedules bots by recording preferences such as record_external, with a per-meeting override, deduplicates shared events, and unschedules on deletion or move; the pricing FAQ says the Calendar API is free. acc-10's enterprise gate (February 2025) no longer matches. source |
Does the job, with a limit 5
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Attendee D Attendee Labs, Inc. | Calendar sync follows reschedules and cancellations, a bot tied to calendar_event_id takes its join_at from the event, and deduplication_key stops repeats, but the docs leave which events qualify entirely to the caller's code; no rule fields exist. source |
| Circleback B Circleback AI, Inc. | After connecting Google or Outlook, joining preferences pick internal or external meetings, organiser and response status, with a per-meeting toggle. Rules are set in the app, not by API, and shared-event duplicate handling isn't stated. source |
| Fathom C Fathom Video Inc. | The user can toggle auto-recording of internal, external and impromptu meetings in Fathom's settings, but no API sets the rules or opts out one event, so an agent or third-party calendar can't drive it. source |
| Meeting BaaS B SAS SPOKE | v2 has calendar sync on every plan (2 calendars on pay-as-you-go), event created, updated and cancelled webhooks, and per-event scheduling with all_occurrences, but which events get a bot is the caller's code; no rule fields or shared-event deduplication are documented. source |
| MeetStream C MeetStream Corp. | Calendar auto-scheduling sends a bot to every eligible meeting with a default bot config and deduplication_key works on calendar scheduling, but eligibility rules (external guests, named attendees) and per-event opt-out aren't documented in what we read. source |
Couldn't check 4
The docs were closed to us, or silent. These carry no mark either way.
| Listing | Why |
|---|---|
| Fireflies.ai B Fireflies.AI Corp. | The API has no calendar or scheduling call; Fireflies' own calendar auto-join settings live in the app and its help pages weren't read. source |
| MeetGeek C AIVISION PRODUCTS SRL | The API has no calendar or scheduling call; MeetGeek's own calendar auto-join settings are in the app and weren't read. source |
| Read AI E Read AI, Inc. | Help-centre pages on calendar auto-join and any API control returned 403. |
| tl;dv D tldx Solutions GmbH | The API has no calendar or scheduling call; tl;dv's own calendar auto-record settings live in the app and weren't read. source |
Doesn't do this job 2
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Granola B Granola, Inc. | Granola doesn't transcribe a meeting until the user clicks into its note; there's no rule-based auto-capture from a calendar. source |
| Zoom Realtime Media Streams (RTMS) C Zoom Communications, Inc. | Auto-start runs the app in meetings the user hosts or joins, set by an admin, but there's no calendar connection or event rule, and only Zoom meetings are covered. source |
What stops agents finishing
- calendar sync priced as an enterprise add-on (acc-10)
- tl;dv and Granola record only from the user's own app or calendar, so a third party's calendar cannot drive them
- no per-meeting opt-out before join
Around it
Before: scheduling.connect-calendars. After: meeting-capture.bot-to-transcript, meeting-capture.post-meeting-push.
Where this comes from
Weight 5 of 100 in Meeting capture & meeting infrastructure: 3 of 56 accounts (acc-10, acc-40, acc-41); held low because most accounts send bots by link, and calendar rules are a feature of the products built on top
The same as data: /api/v1/use-cases/meeting-capture.calendar-auto-join.json, or the MCP tool get_use_case with id meeting-capture.calendar-auto-join. Other jobs in this category: /api/v1/niches?category=meeting-capture.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.