Zoom ACTION
Get Meeting Recordings
Get the cloud recording metadata for one Zoom meeting. Use when you need to know what a meeting recorded — its video, audio, chat, and transcript files — or to pick a specific file to download. To find a meeting ID, call List Meetings or List All Recordings first. Returns the meeting's details plus a
recording_files array whose entries each carry id, file_type, file_size, recording_type, and status. This is metadata only: the download_url on each file does not work on its own — pass that file's id to Get Recording Download Link to get a usable URL. Example: call with meetingId=84598792483 → returns the meeting's topic and start time plus recording files such as { id: "a1b2c3d4-5e6f-7890-abcd-ef1234567890", file_type: "MP4", recording_type: "shared_screen_with_speaker_view", file_size: 148203910, status: "completed" }. A meeting with no cloud recordings returns an empty recording_files array rather than an error, so check the array's length before reporting a failure. See the documentation- Action
- Read only
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Zoom account once, then configure and run Get Meeting Recordings 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: "zoom-get-meeting-recordings",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
zoom: { authProvisionId: "apn_xxxxxxx" },
meetingId: "Meeting ID",
},
})
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": "zoom-get-meeting-recordings",
"configured_props": {
"zoom": { "authProvisionId": "apn_xxxxxxx" },
"meetingId": "Meeting ID"
}
}'// 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": "zoom",
},
},
},
)
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: "zoom-get-meeting-recordings",
arguments: {
meetingId: "Meeting ID",
},
})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 |
|---|---|---|
meetingId Meeting ID | string | The meeting to get the recordings for. For a recurring meeting, pass the meeting UUID (available from List All Recordings) to target a specific occurrence — the numeric meeting ID always returns the most recent one. Required Dynamic |
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
- zoom-get-meeting-recordings
- Version
- 0.1.1
- App
- Zoom
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗