Hedy ACTION
Create Session Context
Creates a new reusable Hedy session context — a named set of custom AI instructions that can be applied to meeting recordings to guide analysis. Free accounts are limited to 1 context; Pro accounts can create multiple. Set
isDefault to true to make this context automatically applied to new sessions. Use Update Session Context to modify an existing context, or Delete Session Context to remove one. 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 Create Session Context 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-create-session-context",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
hedy: { authProvisionId: "apn_xxxxxxx" },
title: "Title",
content: "Content",
},
})
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-create-session-context",
"configured_props": {
"hedy": { "authProvisionId": "apn_xxxxxxx" },
"title": "Title",
"content": "Content"
}
}'// 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-create-session-context",
arguments: {
title: "Title",
content: "Content",
},
})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 |
|---|---|---|
title Title | string | The context name (maximum 200 characters). Required |
content Content | string | Custom AI instruction text for this context (maximum 20,000 characters). Describe how Hedy should analyze meetings — e.g., focus areas, summary style, or specific data to extract. Optional |
isDefault Set as Default | boolean | Set to true to make this the default context automatically applied to new sessions. 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-create-session-context
- Version
- 0.0.2
- App
- Hedy
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗