Fathom ACTION
List Meeting Types
List the meeting types configured for the account (e.g.
Quarterly Business Review), including whether each is currently active or inactive. Use this to discover valid meeting type names before filtering meetings by type. See the documentation- Action
- Read only
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Fathom account once, then configure and run List Meeting Types from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "fathom-list-meeting-types",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
fathom: { authProvisionId: "apn_xxxxxxx" },
cursor: "Cursor",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "fathom-list-meeting-types",
"configured_props": {
"fathom": { "authProvisionId": "apn_xxxxxxx" },
"cursor": "Cursor"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "fathom",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "fathom-list-meeting-types",
arguments: {
cursor: "Cursor",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
cursor Cursor | string | Opaque pagination cursor for fetching the next page of results. Use the next_cursor value returned in the previous response, e.g. eyJwYWdlX251bSI6Mn0=. Omit to fetch the first page. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- fathom-list-meeting-types
- Version
- 0.0.2
- App
- Fathom
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗