AI meeting assistant that records, transcribes, and summarizes meetings
AI meeting assistant that records, transcribes, and summarizes meetings On Nagent, Fathom is exposed as a fully-configurable ai meeting assistants integration that any agent can call — 7 actions, and OAUTH2, API_KEY authentication. No code is required to wire Fathom into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Fathom to automate the kinds of tasks ai meeting assistants teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Fathom into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Fathom, with input parameters and output schema. Drop these into any step of an agent built in Helix.
FATHOM_CREATE_WEBHOOKTool to create a webhook to receive new meeting content from Fathom. Use when you need to set up notifications for meeting recordings. At least one of transcript, CRM matches, summary, or action items must be included in the webhook payload.
Input parameters
Recording types to monitor. Valid values: 'my_recordings', 'shared_external_recordings', 'my_shared_with_team_recordings', 'shared_team_recordings'. Must provide at least one type.
The endpoint URL where webhook events will be sent. Must be a valid HTTPS URL.
Whether to include meeting summaries in webhook payloads. At least one of include_transcript, include_summary, include_action_items, or include_crm_matches must be True.
Whether to include meeting transcripts in webhook payloads. At least one of include_transcript, include_summary, include_action_items, or include_crm_matches must be True.
Whether to include CRM data matches in webhook payloads. At least one of include_transcript, include_summary, include_action_items, or include_crm_matches must be True.
Whether to include extracted action items in webhook payloads. At least one of include_transcript, include_summary, include_action_items, or include_crm_matches must be True.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FATHOM_DELETE_WEBHOOKTool to delete an existing webhook by its ID. Use when you need to remove a webhook that is no longer needed.
Input parameters
The unique ID of the webhook to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FATHOM_GET_RECORDING_SUMMARYTool to retrieve the AI-generated summary for a specific recording. Use when you need to access the summary of a meeting recording. Supports both synchronous mode (returns summary directly) and asynchronous mode (delivers summary to webhook URL specified in destination_url parameter).
Input parameters
The identifier for the specific meeting recording.
Webhook URL for asynchronous delivery of the summary. If provided, the endpoint behaves asynchronously and returns a confirmation. If omitted, returns the summary directly (synchronous mode).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FATHOM_GET_RECORDING_TRANSCRIPTTool to retrieve the full transcript for a specific recording. Use when you need to access the complete meeting transcript with speaker information and timestamps. Can operate synchronously (returns transcript directly) or asynchronously (posts transcript to a destination URL). In the response, speaker is an object — access speaker.display_name rather than treating speaker as a string. Prefer this tool over fetching transcripts via list-meetings calls with include_transcript=true, which produces extremely large responses when many meetings are returned.
Input parameters
The ID of the meeting recording to fetch the transcript for.
Optional destination URL for asynchronous transcript delivery via POST. If provided, the transcript will be posted to this URL instead of being returned directly.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FATHOM_LIST_MEETINGSTool to retrieve a paginated list of meeting recordings for the authenticated user or organization. Use when you need to fetch meetings with optional filtering by dates, domains, meeting type, or recorder. Supports data enrichment via include_* parameters.
Input parameters
Filter by team names. Provide a list of team names.
Pagination cursor for fetching the next page of results. The response includes a `next_cursor` field; paginate through all pages when filtering by date range to avoid missing older recordings.
Filter by recorder email addresses. Provide a list of email addresses.
Filter meetings created after this ISO 8601 timestamp (e.g., '2024-01-01T00:00:00Z').
Filter meetings created before this ISO 8601 timestamp (e.g., '2024-12-31T23:59:59Z').
NOT SUPPORTED FOR OAUTH USERS. This parameter is only available with API key authentication. OAuth authenticated users cannot use this flag on the list endpoint and must fetch summaries via the dedicated GET_RECORDING_SUMMARY action for individual recordings. Default is false.
NOT SUPPORTED FOR OAUTH USERS. This parameter is only available with API key authentication. OAuth authenticated users cannot use this flag on the list endpoint and must fetch transcripts via the dedicated GET_RECORDING_TRANSCRIPT action for individual recordings. Default is false.
Include linked CRM data in the response. Default is false.
Include action items data in the response. Default is false.
Filter by company domains (exact match). Provide a list of domains.
Filter by domain type. Options: 'all' (default), 'only_internal', 'one_or_more_external'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FATHOM_LIST_TEAM_MEMBERSTool to retrieve a paginated list of all team members in the organization. Use when you need to view team members, optionally filtered by team name or paginated using a cursor.
Input parameters
Team name to filter by. Allows filtering results by specific team.
Cursor for pagination. Used for retrieving subsequent pages of results.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FATHOM_LIST_TEAMSTool to retrieve a paginated list of all teams in the organization. Use when you need to get information about teams accessible through the API.
Input parameters
Cursor for pagination. Use the next_cursor value from a previous response to get the next page of results.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 37 agents privately built on Nagent that already use Fathom.
Build on Nagent
Connect Fathom to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Fathom, and click "Connect Now." You'll authenticate with OAUTH2, API_KEY — Nagent handles credential storage and refresh automatically. Once connected, Fathom is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Fathom is connected, you configure its 7 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Fathom steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Fathom event fires, the agent kicks off automatically.
Every Fathom action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Fathom ships with 7 pre-built ai meeting assistants actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Fathom together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Fathom-based workflows tailored to your business.