Symbl.ai ACTION
Update Speaker Events
Update the Speaker Events of the Conversation. See the doc here.
- Action
- Writes data
- Destructive
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Symbl.ai account once, then configure and run Update Speaker Events 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: "symbl_ai-put-speaker-events",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
symbl_ai: { authProvisionId: "apn_xxxxxxx" },
conversationId: "Conversation Id",
speakerEvents: ["Speaker Events"],
},
})
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": "symbl_ai-put-speaker-events",
"configured_props": {
"symbl_ai": { "authProvisionId": "apn_xxxxxxx" },
"conversationId": "Conversation Id",
"speakerEvents": ["Speaker Events"]
}
}'// 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": "symbl_ai",
},
},
},
)
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: "symbl_ai-put-speaker-events",
arguments: {
conversationId: "Conversation Id",
speakerEvents: ["Speaker Events"],
},
})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 |
|---|---|---|
conversationId Conversation Id | string | The Id of the Conversation Required Dynamic |
speakerEvents Speaker Events | string[] | Provide a JSON array of speaker events with their type, user and offset information. Each Speaker Event object is represented by the following structure: [{"type": "started_speaking","user": {"id": "4194eb50-357d-4712-a02d-94215ead1064","name": "user","email": "user@example.com"},"offset": {"seconds": 0,"nanos": 5000000000}},{"type": "stopped_speaking","user": {"id": "4194eb50-357d-4712-a02d-94215ead1064","name": "User","email": "user@example.com"},"offset": {"seconds": 15,"nanos": 5000000000}}]. See doc here 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
- symbl_ai-put-speaker-events
- Version
- 0.0.5
- App
- Symbl.ai
- Authentication
- OAuth
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗