{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/meeting-capture.calendar-auto-join/",
    "json": "https://www.anchorterminal.com/niches/meeting-capture.calendar-auto-join/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/meeting-capture.calendar-auto-join/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/meeting-capture.calendar-auto-join/index.min.md"
  },
  "markdown": "Two or three companies' docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 2 | 5 | 9 | 5 | 3 |\n\n## What counts as done\n\nAfter 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.\n\nHow agents ask for it: record all my customer calls; join my meetings with external guests automatically; stop recording my 1:1s\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **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.\n- **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.\n\n## Does the job, with a limit\n\nIt 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.\n\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n\n## Couldn't check\n\nThe docs were closed to us, or silent. These carry no mark either way.\n\n- **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.\n- **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.\n- **Read AI (Read AI, Inc.)**: Help-centre pages on calendar auto-join and any API control returned 403.\n- **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.\n\n- 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.\n- 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.\n\n## What stops agents finishing\n\n- calendar sync priced as an enterprise add-on (acc-10)\n- tl;dv and Granola record only from the user's own app or calendar, so a third party's calendar cannot drive them\n- no per-meeting opt-out before join\n\n## Around it\n\nBefore: scheduling.connect-calendars. After: meeting-capture.bot-to-transcript, meeting-capture.post-meeting-push.\n\n## Where this comes from\n\nWeight 5 of 100 in Meeting capture \u0026 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\n\nAs 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.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Record every qualifying meeting on a user's calendar without being asked each time",
        "url": ""
      }
    ],
    "description": "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 \u0026 meeting infrastructure with the reason and a source.",
    "facts": null,
    "h1": "Record every qualifying meeting on a user's calendar without being asked each time",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/meeting-capture.calendar-auto-join/",
    "published": "",
    "section": "agents",
    "title": "Record every qualifying meeting on a user's calendar without being…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/meeting-capture.calendar-auto-join/"
  },
  "tokens": {
    "markdown": 1400,
    "slim": 330
  },
  "version": 1
}
