Hedy ACTION
Update Topic
Updates properties of an existing Hedy topic. All fields are optional — only the fields you provide will be changed. To clear the custom AI context, pass an empty string or
null for topicContext. Use Get Many Topics to find the topic ID. See the documentation- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Hedy account once, then configure and run Update Topic 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: "hedy-update-topic",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
hedy: { authProvisionId: "apn_xxxxxxx" },
topicId: "Topic ID",
name: "Name",
},
})
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": "hedy-update-topic",
"configured_props": {
"hedy": { "authProvisionId": "apn_xxxxxxx" },
"topicId": "Topic ID",
"name": "Name"
}
}'// 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": "hedy",
},
},
},
)
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: "hedy-update-topic",
arguments: {
topicId: "Topic ID",
name: "Name",
},
})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 |
|---|---|---|
topicId Topic ID | string | The unique identifier of the topic (e.g., topic_5f8e9a). Use Get Many Topics to list available topic IDs. Required |
name Name | string | New topic name (maximum 100 characters). Optional |
description Description | string | New topic description (maximum 500 characters). Optional |
color Color | string | New hex color code (e.g. #FF5722). Optional |
iconName Icon Name | string | New icon identifier. Optional |
topicContext Topic Context | string | New custom AI analysis instructions (maximum 20,000 characters). Pass an empty string to clear the existing context. 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
- hedy-update-topic
- Version
- 0.0.2
- App
- Hedy
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗