# Record every qualifying meeting on a user's calendar without being asked each time

> Record every qualifying meeting on a user's calendar without being asked each time: 2 companies fully do it, 5 with a limit, 9 carry the tag. Every listing in Meeting capture & meeting infrastructure with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/meeting-capture.calendar-auto-join/
- Markdown: https://www.anchorterminal.com/niches/meeting-capture.calendar-auto-join/index.md (~1,400 tokens)
- Slim: https://www.anchorterminal.com/niches/meeting-capture.calendar-auto-join/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/meeting-capture.calendar-auto-join/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 5 | 9 | 5 | 3 |

## 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

The docs show it meets the test above, and nothing we read says otherwise.

- **Nylas Notetaker API (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.
- **Recall.ai (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.

## Does the job, with a limit

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.

- **Attendee (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.
- **Circleback (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.
- **Fathom (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.
- **Meeting BaaS (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.
- **MeetStream (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.

## Couldn't check

The docs were closed to us, or silent. These carry no mark either way.

- **Fireflies.ai (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.
- **MeetGeek (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.
- **Read AI (Read AI, Inc.)**: Help-centre pages on calendar auto-join and any API control returned 403.
- **tl;dv (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.

- not this job: Granola (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.
- not this job: Zoom Realtime Media Streams (RTMS) (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.

## 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

As data: https://www.anchorterminal.com/api/v1/use-cases/meeting-capture.calendar-auto-join.json, or the MCP tool get_use_case with id meeting-capture.calendar-auto-join. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
