# Fathom Your Toolhouse AI Worker can connect to Fathom using 7 specialized tools. ## Auth Connection This service requires an auth connection to use its tools. You can set this up in your Toolhouse dashboard under [Auth Connections](https://toolhouse.app/auth-connections?authkit_slugs=fathom). ## Tools (7) ### `Fathom Create Webhook` Integration name: **FATHOM\_CREATE\_WEBHOOK** Tool 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------------------- | ------- | :------: | -------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `triggered_for` | array | ✅ | `["my_recordings"]` | 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. | | `destination_url` | string | ✅ | `"https://webhook.site/test-fathom-webhook"` | The endpoint URL where webhook events will be sent. Must be a valid HTTPS URL. | | `include_summary` | boolean | | — | 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. | | `include_transcript` | boolean | | — | 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. | | `include_crm_matches` | boolean | | — | 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. | | `include_action_items` | boolean | | — | 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. | *** ### `Fathom Delete Webhook` Integration name: **FATHOM\_DELETE\_WEBHOOK** Tool to delete an existing webhook by its ID. Use when you need to remove a webhook that is no longer needed. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | -------------------- | -------------------------------------- | | `id` | string | ✅ | `"_Lptjdyv8TKWQbBs"` | The unique ID of the webhook to delete | *** ### `Fathom Get Recording Summary` Integration name: **FATHOM\_GET\_RECORDING\_SUMMARY** Tool 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). #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------------- | ------- | :------: | ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `recording_id` | integer | ✅ | `102117184` | The identifier for the specific meeting recording. | | `destination_url` | string | | `"https://example.com/webhook"` | 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). | *** ### `Fathom Get Recording Transcript` Integration name: **FATHOM\_GET\_RECORDING\_TRANSCRIPT** Tool 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------------- | ------- | :------: | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `recording_id` | integer | ✅ | `123456789` | The ID of the meeting recording to fetch the transcript for. | | `destination_url` | string | | `"https://example.com/destination"` | Optional destination URL for asynchronous transcript delivery via POST. If provided, the transcript will be posted to this URL instead of being returned directly. | *** ### `Fathom List Meetings` Integration name: **FATHOM\_LIST\_MEETINGS** Tool 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------------------------- | ------- | :------: | ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `teams` | array | | `["Sales","Engineering"]` | Filter by team names. Provide a list of team names. | | `cursor` | string | | `"eyJpZCI6MTIzfQ=="` | 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. | | `recorded_by` | array | | `["user@example.com","admin@company.org"]` | Filter by recorder email addresses. Provide a list of email addresses. | | `created_after` | string | | `"2024-01-01T00:00:00Z"` | Filter meetings created after this ISO 8601 timestamp (e.g., '2024-01-01T00:00:00Z'). | | `created_before` | string | | `"2024-12-31T23:59:59Z"` | Filter meetings created before this ISO 8601 timestamp (e.g., '2024-12-31T23:59:59Z'). | | `include_summary` | boolean | | `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 summaries via the dedicated GET\_RECORDING\_SUMMARY action for individual recordings. Default is false. | | `include_transcript` | boolean | | `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_crm_matches` | boolean | | `false` | Include linked CRM data in the response. Default is false. | | `include_action_items` | boolean | | `false` | Include action items data in the response. Default is false. | | `calendar_invitees_domains` | array | | `["example.com","company.org"]` | Filter by company domains (exact match). Provide a list of domains. | | `calendar_invitees_domains_type` | string | | `"all"` | Filter by domain type. Options: 'all' (default), 'only\_internal', 'one\_or\_more\_external'. | *** ### `Fathom List Team Members` Integration name: **FATHOM\_LIST\_TEAM\_MEMBERS** Tool 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | ----------------------------------------------------------------------- | | `team` | string | | `"Engineering"` | Team name to filter by. Allows filtering results by specific team. | | `cursor` | string | | `"eyJsYXN0X2lkIjoxMjN9"` | Cursor for pagination. Used for retrieving subsequent pages of results. | *** ### `Fathom List Teams` Integration name: **FATHOM\_LIST\_TEAMS** Tool to retrieve a paginated list of all teams in the organization. Use when you need to get information about teams accessible through the API. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | -------------------------------- | ----------------------------------------------------------------------------------------------------------- | | `cursor` | string | | `"eyJpZCI6IjEyMzQ1Njc4OTAifQ=="` | Cursor for pagination. Use the next\_cursor value from a previous response to get the next page of results. | *** --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.toolhouse.ai/toolhouse/integrations/fathom.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.