Fathom is a live automation source: watchers react the moment something happens. One plain sentence is the whole setup:
Binee reads Fathom and never changes anything in it. What it learns there powers answers, insights, and dashboards, and any follow-up work happens through tools where writing is supported, always with your approval.
You tell Binee: "Warn me when something promised in a meeting has no task behind it two days later."
That is the whole setup. Binee builds the automation, watches around the clock, and when something matches, the insight arrives with the evidence attached, in your Inbox, by email, or in Slack.
Paste your Fathom API key once in Settings, Integrations (Binee shows exactly where to find it).
Ask about any call: "what action items came out of Monday's kickoff?"
Turn on Meeting commitments and let promises get matched against what actually happens afterwards.
Connected with your own Fathom API key, pasted once in Settings. Binee tells you honestly when the key needs replacing.
Binee reads transcripts to investigate, guided by your automation's wording, and never stores the raw transcript.
No. Transcripts are read during an investigation, guided by your automation's wording, and never stored. Only the finding and its evidence references are kept.
No preference: both connect with a pasted key, both feed meeting recaps and commitment tracking, and both work with the same automations. Connect whichever your team records with.
Binee gets sharper with every connection: the more tools it reads, the more dots it can connect around Fathom.