{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/meeting-capture.post-meeting-push/",
    "json": "https://www.anchorterminal.com/niches/meeting-capture.post-meeting-push/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/meeting-capture.post-meeting-push/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/meeting-capture.post-meeting-push/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 | 6 | 35 | 12 | 8 |\n\n## What counts as done\n\nA signed webhook or a pollable list tells the agent a meeting's transcript and summary are ready, carrying an id the agent fetches once; the summary, action items with owners and the full transcript are readable in that fetch, so the agent writes one record per meeting with no duplicates.\n\nHow agents ask for it: after every sales call update the CRM; put action items from my meetings into Linear; save each meeting to Obsidian; draft the minutes and the follow-up\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Circleback (Circleback AI, Inc.)**: A webhook automation posts each matching meeting signed with an X-Signature HMAC, carrying notes, attendees, action items with assignee name and email, and the transcript; webhooks are a paid-plan automation, and list meetings can be polled by status on Free.\n- **Fathom (Fathom Video Inc.)**: A signed webhook fires when a meeting's content is ready and can carry summary, transcript with named speakers and action items with assignee; acc-50 verified HMAC and upserted by recording_id. A webhook id can't be read back later, so it must be saved.\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- **Fireflies.ai (Fireflies.AI Corp.)**: HMAC-signed meeting.transcribed and meeting.summarized webhooks carry the meeting id, and one transcript query returns sentences and summary, but action_items is a single string with no owner field.\n- **Granola (Granola, Inc.)**: An HMAC-signed note.generated webhook carries the note_id, and Get Note returns summary and transcript, but webhooks and API need Business or Enterprise, action items sit inside the summary text without owners, and no failure event exists.\n- **MeetGeek (AIVISION PRODUCTS SRL)**: A webhook posts the meeting_id when analysis completes, and summary, Task highlights and transcript are fetchable, but no signature scheme is documented, the failure payload has no id, and tasks are text with the owner only in the sentence.\n- **Nylas Notetaker API (Nylas, Inc.)**: An HMAC-signed notetaker.media webhook with available state carries URLs for recording, speaker-labelled transcript, summary and action items, but action items are bare strings with no owner, URLs expire in 60 minutes, and transcripts are occasionally raw text.\n- **Read AI (Read AI, Inc.)**: The plans page lists webhooks among paid premium integrations, and acc-11 found Read AI was the only notetaker with webhooks but that it posted notes rather than full transcripts; the webhook reference returned 403.\n- **tl;dv (tldx Solutions GmbH)**: MeetingReady and TranscriptReady webhooks carry meeting and transcript data, and notes are fetchable, but no webhook signature scheme is documented, action-item owners aren't a field, and API and webhooks need Pro or Business on the organiser's side.\n\n- not this job: Attendee (Attendee Labs, Inc.): A signed post_processing_completed webhook carries the bot id and the transcript is fetchable, but Attendee produces no summary or action items, so the fetch the success names can't be met.\n- not this job: Meeting BaaS (SAS SPOKE): A signed bot.completed webhook carries the bot id and transcript, but summaries appear only in some providers' raw output and no action items with owners are produced, so the success can't be met.\n- not this job: MeetStream (MeetStream Corp.): A signed transcription.processed webhook tells the agent the transcript is ready, but the docs index has no summary or action-item output, so the success can't be met.\n- not this job: Recall.ai (Hyperdoc Inc.): Signed recording.done and transcript.done webhooks carry ids to fetch, but Recall returns no summary or action items, so the fetch the success names can't be met.\n- not this job: Zoom Realtime Media Streams (RTMS) (Zoom Communications, Inc.): meeting.rtms_stopped marks the end of a stream, but Zoom produces no stored summary, action items or transcript for the app to fetch; the app must build them itself.\n\n## What stops agents finishing\n\n- no webhook, so each user must set up Zapier (acc-11)\n- webhooks and API on a paid plan only (Granola Business, tl;dv Pro)\n- webhook fires before the transcript is complete\n- webhook secret or id cannot be read back (Fathom)\n\n## Around it\n\nBefore: meeting-capture.bot-to-transcript, meeting-capture.calendar-auto-join. After: crm.log-activity, project-management.capture-tasks, crm.follow-up-email, productivity.write-doc.\n\n## Where this comes from\n\nWeight 12 of 100 in Meeting capture \u0026 meeting infrastructure: 8 of 56 accounts (acc-11, acc-16, acc-24, acc-40, acc-50, acc-51, acc-53, acc-54), plus about a dozen n8n Fireflies templates seen in a search (vendor-adjacent, not counted)\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/meeting-capture.post-meeting-push.json, or the MCP tool get_use_case with id meeting-capture.post-meeting-push. 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": "After each meeting, file the notes and action items where the team works",
        "url": ""
      }
    ],
    "description": "After each meeting, file the notes and action items where the team works: 2 companies fully do it, 6 with a limit, 35 carry the tag. Every listing in Meeting capture \u0026 meeting infrastructure with the reason and a source.",
    "facts": null,
    "h1": "After each meeting, file the notes and action items where the team works",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/meeting-capture.post-meeting-push/",
    "published": "",
    "section": "agents",
    "title": "After each meeting, file the notes and action items where the team…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/meeting-capture.post-meeting-push/"
  },
  "tokens": {
    "markdown": 1500,
    "slim": 330
  },
  "version": 1
}
