Fireflies ACTION
Update Meeting
Update a meeting's title, privacy level, and/or channel. Each selected field is applied through a separate, sequential mutation rather than a single atomic call — if a later update fails, earlier successful changes remain applied. Set only the fields you want to change — unset fields are left untouched. Updating the title requires admin privileges on the Fireflies team. See the documentation for Update Meeting Title, Update Meeting Privacy and Update Meeting Channel
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Fireflies account once, then configure and run Update Meeting 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-update-meeting",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
fireflies: { authProvisionId: "apn_xxxxxxx" },
meetingId: "Meeting ID",
title: "Title",
},
})
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-update-meeting",
"configured_props": {
"fireflies": { "authProvisionId": "apn_xxxxxxx" },
"meetingId": "Meeting ID",
"title": "Title"
}
}'// 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-update-meeting",
arguments: {
meetingId: "Meeting ID",
title: "Title",
},
})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 update. Use Find Meeting by ID or Find Recent Meeting to look up a meeting ID. Required Dynamic |
title Title | string | The new title for the meeting, e.g. Q3 Budget Review. Must be between 5 and 256 characters and should not contain special characters. Optional |
privacy Privacy | string | Who can access the meeting. link - anyone with the link, owner - only the meeting owner, participants - meeting participants only, teammates - the owner's teammates, teammatesandparticipants - teammates and participants. Optional |
channelId Channel ID | string | Move the meeting into this channel. Use List Channel ID Options to browse available channels. 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
- fireflies-update-meeting
- Version
- 0.0.2
- App
- Fireflies
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗