Grain ACTION
Get Recording
Fetches a specific recording by its ID from Grain, returning its metadata (title, times, URL, tags, teams, meeting type). Enable the optional include props to add highlights, participants, AI action items, AI summary, calendar event, HubSpot data, or screenshares to the response. Use List Recordings to find recording IDs, and Get Transcript to fetch the full transcript. Example:
recordingId: "pppp6666-qq77-rr88-ss99-tttt00000000" with aiSummary: true returns the recording's metadata plus {"ai_summary": {"text": "..."}}. See the documentation- Action
- Read only
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Grain account once, then configure and run Get Recording 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: "grain-get-recording",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
grain: { authProvisionId: "apn_xxxxxxx" },
recordingId: "Recording ID",
highlights: true,
},
})
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": "grain-get-recording",
"configured_props": {
"grain": { "authProvisionId": "apn_xxxxxxx" },
"recordingId": "Recording ID",
"highlights": true
}
}'// 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": "grain",
},
},
},
)
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: "grain-get-recording",
arguments: {
recordingId: "Recording ID",
highlights: true,
},
})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 |
|---|---|---|
recordingId Recording ID | string | The ID of the recording to fetch. Use List Recordings to find recording IDs. Required |
highlights Include Highlights | boolean | Whether to include the recording's highlights Optional |
participants Include Participants | boolean | Whether to include the recording's participants Optional |
aiActionItems Include AI Action Items | boolean | Whether to include the recording's AI action items Optional |
aiSummary Include AI Summary | boolean | Whether to include the recording's AI summary Optional |
calendarEvent Include Calendar Event | boolean | Whether to include the recording's calendar event data Optional |
hubspot Include HubSpot Data | boolean | Whether to include associated HubSpot data Optional |
screenshares Include Screenshares | boolean | Include the recording's screenshare ranges in the response 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
- grain-get-recording
- Version
- 1.0.2
- App
- Grain
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗