Fireflies ACTION
Find Clip by ID
Retrieve a single meeting clip (a Fireflies "bite") by its ID, including its render status and media URLs. Use this to follow up on Create Meeting Clip, which returns immediately with
status: pending and no media. Poll until status reaches a terminal ready or error, and stop on either — pending and processing mean the clip is still rendering. Once ready, the playable media is at sources[].src, with preview and thumbnail also populated; all three are null beforehand. Note that summary_status tracks the AI-generated summary separately and can finish while status is still pending, so poll status rather than summary_status. Use List Clips to look up a clip ID. See the documentation- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Fireflies account once, then configure and run Find Clip by ID 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: "fireflies-find-clip-by-id",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
fireflies: { authProvisionId: "apn_xxxxxxx" },
biteId: "Clip 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": "fireflies-find-clip-by-id",
"configured_props": {
"fireflies": { "authProvisionId": "apn_xxxxxxx" },
"biteId": "Clip 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": "fireflies",
},
},
},
)
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: "fireflies-find-clip-by-id",
arguments: {
biteId: "Clip 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 |
|---|---|---|
biteId Clip ID | string | The clip to retrieve, e.g. kwQIMbxsyi1. Returned as id by Create Meeting Clip, or use List Clips to browse existing clips. Required |
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
- fireflies-find-clip-by-id
- Version
- 0.0.2
- App
- Fireflies
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗