Pull meeting transcripts and summaries into incident and change context
Connect Fathom with an API key and Luumen can read your recorded meetings the way you would: list what was recorded, pull the AI summary, and read the full transcript when the summary is not enough. Useful when a postmortem, a vendor call, or a change review happened on a call and the details never made it into a ticket. Webhook changes are previewed and approved first.
7 tools: 5 read, 2 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Fathom run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as create webhook for meeting content, delete webhook. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Fathom — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.