CONNECT APP
Build with Fathom
Artificial Intelligence (AI)
- OAuth
MCP
Give your agent Fathom tools
Every Fathom action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Fathom account for each tool call — you store no tokens.
// 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()
// e.g. run Get Recording Download Status:
const result = await mcp.callTool({
name: "fathom-get-recording-download-status",
arguments: {
recordingId: "Recording ID",
downloadId: "Download ID",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"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",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Get Recording Download Status:
result = await session.call_tool("fathom-get-recording-download-status", {
"recordingId": "Recording ID",
"downloadId": "Download ID",
})API PROXY
Call the Fathom API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Fathom API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://api.fathom.ai/external/v1/teams",
})
// Any allowed Fathom endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://api.fathom.ai/external/v1/teams
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkuZmF0aG9tLmFpL2V4dGVybmFsL3YxL3RlYW1z?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Fathom actions from your backend
Connect a user's Fathom account once, then run Get Recording Download Status on their behalf from your own code — TypeScript, Python, or plain HTTP.
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-get-recording-download-status",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
fathom: { authProvisionId: "apn_xxxxxxx" },
recordingId: "Recording ID",
downloadId: "Download ID",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="fathom-get-recording-download-status",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"fathom": {"authProvisionId": "apn_xxxxxxx"},
"recordingId": "Recording ID",
"downloadId": "Download ID",
},
)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-get-recording-download-status",
"configured_props": {
"fathom": { "authProvisionId": "apn_xxxxxxx" },
"recordingId": "Recording ID",
"downloadId": "Download ID"
}
}'TOOLS
Fathom actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Get Recording Download Status
actionCheck the status of a previously requested recording download and, oncecompleted, get the signed video/audio download URLs. Use Request Recording Download first to obtain a Download ID. See the documentationRead-onlyv0.0.2 -
Get Recording Summary
actionGet the summary of a recording. See the documentationRead-onlyv0.0.2 -
Get Recording Transcript
actionGet the transcript of a recording. See the documentationRead-onlyv0.0.2 -
List Meeting Types
actionList the meeting types configured for the account (e.g.Quarterly Business Review), including whether each is currentlyactiveorinactive. Use this to discover valid meeting type names before filtering meetings by type. See the documentationRead-onlyv0.0.2 -
List Meetings
actionList meetings. See the documentationRead-onlyv0.0.2 -
List Team Members
actionList the members of a team, or all team members across the account. Use List Teams to find a valid team name to filter by. See the documentationRead-onlyv0.0.2 -
List Teams
actionList the teams configured for the account. Use this to discover valid team names before filtering List Team Members, List Users and Permissions, or other team-scoped tools. See the documentationRead-onlyv0.0.2 -
List Users and Permissions
actionList the users on the account and their admin permissions (settings access level and view access). Admin-only — the connected account must haveaccount_adminsettings access, or the request fails with a 403 error. Use List Teams to find a valid team name to filter by. See the documentationRead-onlyv0.0.2 -
Request Recording Download
actionRequest a downloadable video/audio file for a recording. The initial response may already havestatus: completedwith the signed download URL included (common for audio-only recordings, which finish synchronously) — use that URL right away in this case. Otherwise the response returnsstatus: processingand adownload_id; use Get Recording Download Status to poll until the status is no longerprocessing. Stop polling oncompleted(signed download URL is included) or onfailed(inspect the returned failure reason instead of continuing to poll), or provide aDestination URLto have Fathom POST the completed payload there instead of polling. See the documentationWritev0.0.2
MULTI-APP
Use Fathom with other popular apps
Most products don't stop at one integration. Pair Fathom with the other apps your users rely on, and ship use cases that span both.
- App slug
- fathom
- Authentication
- OAuth
- Categories
- Artificial Intelligence (AI)
- Actions
- 9
- Triggers
- 1
- API proxy
- Available
OAuth scopes
These are the scopes Pipedream's managed Fathom OAuth client requests when one of your users connects an account. Supply your own OAuth client to request a different set.
- public_api