How does Lyro connect to Fathom?

You authorize a Fathom account on the integration page, and Lyro then uses that connection to look up data and trigger updates. Nothing needs to be built or maintained afterwards.

What Fathom data can Lyro reach?

Only what the connected account authorizes. Lyro fetches current information through that connection and triggers updates when asked, with no access beyond the authorization - and you can disconnect it at any time.

Will Lyro change something in Fathom without being asked?

No. An update happens because a conversation asked for it. If Lyro cannot complete one, it says so in the thread and can hand off to a teammate with the full history.

How is this different from opening Fathom directly?

The data is the same; the difference is where the answer appears. Lyro runs the lookup inside the conversation, so a question about a call does not become a separate task for somebody.

Fathom MCP integration

Pulls what a connected Fathom account holds into the conversation and triggers the update a request calls for.

Connect Fathom See all integrations

3actions available

What your agent can do with Fathom

Every action runs live through MCP. Nothing to build, nothing to maintain.

Look up Fathom data
Lyro retrieves analytics information relevant to conversations. Agents access web analytics without opening the dashboard separately.
Trigger a Fathom update
Lyro makes changes in Fathom to update workflow states automatically. Teams log actions that sync back to Fathom instantly.

How businesses use Fathom + Lyro

Each card is one request a support team gets, and the Fathom actions Lyro runs to close it.

Answer a question a call already settled
Rather than sending someone to a recording, Lyro looks up the connected Fathom account and answers from what it returns.
Connect Fathom AccountLook Up Fathom Data
Record the outcome while it is fresh
When a conversation produces a change, Lyro triggers the Fathom update in the same thread instead of adding it to a to-do list.
Look Up Fathom DataTrigger Fathom Update
Confirm the detail before repeating it
Lyro checks the current Fathom record first, so a reply about what was discussed is grounded in the account rather than in someone's recollection.
Connect Fathom AccountLook Up Fathom Data
Use a meeting lookup as one step of many
When a request spans more than meeting notes, Lyro folds the Fathom lookup in as a single step and handles the remaining work itself.
Look Up Fathom DataTrigger Fathom Update

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Fathom actions it has and picks the ones a request needs.

01
Connect Fathom
Authorize the Fathom account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Fathom actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Fathom · Lyro

Everything else about Fathom

Setup, permissions, and the limits of what Lyro can do inside Fathom.

You authorize a Fathom account on the integration page, and Lyro then uses that connection to look up data and trigger updates. Nothing needs to be built or maintained afterwards.