thenotetakers.com compares AI notetakers on the workflows they feed: CRM updates, project management tools, Zapier, webhooks, APIs and MCP servers. "Integrates with" can mean very different things, so this page explains what each post compares, where the evidence comes from, how tools are chosen and ordered, and how posts are kept current.
What each post compares
Each post starts from one workflow and compares tools one level below the integrations page. The criteria the posts use:
- Trigger or event. What starts the workflow: a meeting ending, a note being added or shared, a recording becoming available, a transcript being ready. For Zapier, the triggers and actions the vendor's Zapier app lists. For webhooks, the events the vendor documents.
- What data lands. Whether the request or record carries the full content (notes, action items, transcript, insights) or only an ID that you fetch with a second API call. For CRMs, whether the tool logs notes or activity, creates tasks, or writes values into specific fields.
- Which records it touches. The CRM objects (contacts, companies, deals, opportunities) or project tool items the data attaches to, and whether the tool can create new records.
- Filtering and scope. Whether you can choose which meetings send, by tag, title, participant, domain, folder or keyword, and whether a webhook is scoped to one user, a team or the whole workspace.
- Delivery details. For webhooks: request signing, retries, resends of past meetings and custom auth headers.
- Write back. Whether a zap or API can write data back into the notetaker, not only read from it.
- Plan needed. The plan that unlocks the integration, the API or the webhook, with its list price and any per integration user limits.
The free plan series applies the same criteria to what each vendor's free plan allows: API access, rate limits, and which integrations work without paying.
How integration claims are checked
Every integration claim is traced to a first party source, each recorded with the date it was checked:
- API references and developer docs for endpoints, payload fields, events, authentication and rate limits.
- Webhook documentation for events, payload samples, signing and retries.
- Zapier app pages and other app marketplace listings (for example a CRM's marketplace) for the triggers, actions and permissions an integration actually exposes.
- Help center articles for setup steps and plan gates.
- Pricing pages for which plan includes the integration.
- Changelogs for new or retired events, fields and endpoints.
Field names, event names and parameters are written exactly as the vendor documents them. When a vendor's pages disagree, for example a setup guide saying every user can use an integration while the pricing table leaves it off the free plan, the post says the pages conflict and cites both. When the docs do not describe a behavior, such as whether a webhook retries, the post says it is not documented.
How tools are included
The shortlist for a post is the set of notetakers whose own documentation shows they support the workflow: a native integration, a documented Zapier app, a documented webhook or a public API. A tool that only reaches the target through a third party route is described that way, with the route named. A tool can be left out when its documentation does not say enough to fill in the trigger, the data or the plan.
How order is decided
Each post opens with its picks, one line per tool, each naming the case that tool handles best. The first pick is the tool that handles the post's stated workflow best on the criteria above. The others are named for the case where they are the better choice: webhooks on every plan, the deepest field mapping, the most fine grained events. A different workflow can produce a different first pick. There are no point scores, rubric weights, star ratings or aggregate scores.
The site's own API
The posts are available to your own tools as well. The developers page documents a read-only JSON API, an MCP server, and llms.txt plus a Markdown copy of every page, with no sign up and no API key.
Conflicts of interest
Every tool in a post is held to the same criteria and the same sourcing rules.
What the site does not do
The site carries no ads. Vendors who want a correction are asked for a link to the public page that documents the change.
Freshness
Every post shows its Updated date; pricing and plan limits are rechecked when a vendor changes pricing or plans, and at least every 90 days. A changed API reference, a new or retired webhook event, or an updated Zapier or marketplace listing also triggers a recheck of the posts that cite it, and the Updated date moves when a post changes.
Questions about a post go to hello@thenotetakers.com, or see the contact page.