> This page is for version v8.3.0 (default). > For other versions, use one of these documentation indexes: > - v8.3.0 (default): https://docs.workflows.com/v-8-3-0/llms.txt > For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.workflows.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.workflows.com/_mcp/server. # fathom_list_meetings READ # fathom_list_meetings Retrieves a list of meeting recordings from your Fathom account with optional date filtering and AI-generated summaries. Use this tool to discover available meetings before retrieving transcripts. > **Success** > > Fathom includes AI-generated summaries in the list results, giving you a quick overview of meeting content without downloading full transcripts. ## Prerequisites > **Fathom Integration Required** > > This tool requires Fathom integration to be configured. See the [Fathom Setup Guide](/mcp-integrations-fathom-setup) for configuration instructions. ## Parameters ### fromDate
**Type** string (ISO 8601 date)
**Required** No
**Description** Start date for filtering meetings. Format: `YYYY-MM-DD` . If omitted, returns meetings from the beginning of your account history.
**Example** `2024-11-01`
### toDate
**Type** string (ISO 8601 date)
**Required** No
**Description** End date for filtering meetings. Format: `YYYY-MM-DD` . If omitted, returns meetings up to the current date.
**Example** `2024-11-30`
### limit
**Type** number
**Required** No
**Description** Maximum number of meetings to return. Default: 10. Maximum: 100.
**Example** `20`
## Request ```json { "fromDate": "2024-11-01", "toDate": "2024-11-30", "limit": 20 } ``` ## Response ```json { "meetings": [ { "meetingId": "meeting_abc123", "title": "Product Planning - Q4 Roadmap", "date": "2024-11-15T14:00:00Z", "duration": 3600, "summary": "Discussed Q4 product roadmap priorities. Team agreed to focus on enterprise features and API improvements. Marketing will need updated positioning by Dec 1.", "participants": [ { "name": "Sarah Chen", "email": "sarah.chen@company.com" }, { "name": "Mike Johnson", "email": "mike.johnson@company.com" }, { "name": "Alex Rivera", "email": "alex.rivera@company.com" } ] }, { "meetingId": "meeting_def456", "title": "Client Check-in - Acme Corp", "date": "2024-11-18T10:00:00Z", "duration": 1800, "summary": "Client reported 40% improvement in efficiency since implementation. Requested training for 5 new team members. Follow-up scheduled for Dec 5.", "participants": [ { "name": "Jennifer Wu", "email": "jennifer@acmecorp.com" }, { "name": "Tom Davis", "email": "tom.davis@company.com" } ] } ], "total": 42, "hasMore": true } ``` ### Response Properties | Property | Type | Description | | --------------------------------- | ------- | --------------------------------------------------------------- | | `meetings` | array | Array of meeting objects with metadata | | `meetings[].meetingId` | string | Unique identifier for the meeting (use with other Fathom tools) | | `meetings[].title` | string | Meeting title from calendar | | `meetings[].date` | string | ISO 8601 timestamp of when the meeting occurred | | `meetings[].duration` | number | Meeting duration in seconds | | `meetings[].summary` | string | AI-generated summary of meeting content | | `meetings[].participants` | array | Array of participant objects | | `meetings[].participants[].name` | string | Participant's full name | | `meetings[].participants[].email` | string | Participant's email address | | `total` | number | Total number of meetings matching the filter criteria | | `hasMore` | boolean | Whether there are more meetings beyond the limit | ## Common Use Cases #### Quick Meeting Review Use AI summaries to quickly review meeting outcomes without reading full transcripts. **Example:** ``` "Show me summaries of my team meetings from this week" ``` **Natural language workflow:** * AI uses `fathom_list_meetings` with date filter for this week * Returns meetings with AI-generated summaries * You get instant overview of what was discussed **What you get:** * Quick meeting recaps * Key decisions and outcomes * Action items at a glance * No need to read full transcripts #### Find Meetings with Specific People Discover meetings with specific participants before creating minds. **Example:** ``` "Find all my Fathom meetings with client stakeholders from the enterprise segment this quarter" ``` **Natural language workflow:** * AI lists meetings from Q4 * Filters to those with external participants * Identifies enterprise client meetings * Provides list for selection **What you get:** * Relevant meeting list * Participant details * Meeting summaries * IDs for transcript retrieval #### Meeting Topic Discovery Use summaries to find meetings discussing specific topics. **Example:** ``` "Show me all meetings where we discussed API integration or technical architecture" ``` **Natural language workflow:** * AI lists recent meetings * Searches summaries for keywords * Returns matching meetings **What you get:** * Topic-filtered meeting list * Context from summaries * Participant information * Quick topic-based discovery ## Error Responses #### 401 Unauthorized ```json { "error": "Unauthorized", "message": "Fathom authentication failed" } ``` **Solution:** Verify your Fathom API key is configured correctly. See the [Fathom Setup Guide](/mcp-integrations-fathom-setup). #### 400 Bad Request - Invalid Date ```json { "error": "Bad Request", "message": "Invalid date format. Use YYYY-MM-DD" } ``` **Solution:** Ensure dates are in ISO 8601 format: `YYYY-MM-DD`. #### 429 Rate Limit Exceeded ```json { "error": "Rate Limit Exceeded", "message": "Too many requests to Fathom API" } ``` **Solution:** Wait before retrying. Reduce request frequency or use date filtering. #### No Meetings Found ```json { "meetings": [], "total": 0, "hasMore": false } ``` **Solution:** Not an error—no meetings match your criteria. Try: * Widening the date range * Removing date filters * Verifying meetings exist in Fathom * Checking account permissions ## Best Practices #### Leverage AI Summaries * Read summaries before downloading full transcripts * Use summaries for quick meeting recaps * Filter meetings by summary content * Identify key meetings without full transcript review #### Efficient Filtering * Use date ranges to narrow results * Start with recent meetings (last week/month) * Filter by participant for targeted discovery * Use limit parameter to control result size #### Integration Planning * List meetings first, then get transcripts selectively * Use participant info to identify mind creation targets * Check duration to prioritize substantive meetings * Save meeting IDs for later retrieval ## Integration with Mind Reasoner ### Typical Workflow #### List Meetings Use `fathom_list_meetings` to discover available meetings #### Review Summaries Read AI summaries to identify relevant meetings #### Select Meetings Choose meetings based on participants and topics #### Get Transcripts Use `fathom_get_transcript` for selected meetings #### Create Minds Build minds from transcript data **Natural language example:** ``` "Show me my client meetings from last month, then create minds for the client contacts who were most engaged" ``` ## See Also #### [fathom_get_transcript](/mcp-tool-fathom-get-transcript) Retrieve full transcripts after listing meetings #### [fathom_get_meeting_details](/mcp-tool-fathom-get-meeting-details) Get detailed meeting information and action items #### [Fathom Tools Overview](/mcp-integrations-fathom) See all Fathom tools and workflows