IMPLEMENTATION
Call this tool
Connect a user's Canny account once, then configure and run Create Post 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: "canny-create-post",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
canny: { authProvisionId: "apn_xxxxxxx" },
authorId: "Author ID",
boardId: "Board 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": "canny-create-post",
"configured_props": {
"canny": { "authProvisionId": "apn_xxxxxxx" },
"authorId": "Author ID",
"boardId": "Board 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": "canny",
},
},
},
)
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: "canny-create-post",
arguments: {
authorId: "Author ID",
boardId: "Board 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 |
|---|---|---|
authorId Author ID | string | The ID of the author of the post Required Dynamic |
boardId Board ID | string | The ID of a board Required Dynamic |
title Title | string | The title of the post Required |
details Details | string | The details of the post Required |
categoryId Category ID | string | The ID of a category Optional Dynamic |
eta ETA | string | The estimated date of the post's completion. In the format of MM/YYYY, eg, 06/2022. Optional |
etaPublic ETA Public | boolean | If the ETA should be made visible to all users Optional |
ownerId Owner ID | string | The ID of the user responsible for the completion of the work described in the post Optional Dynamic |
imageUrls Image URLs | string[] | An array of the URLs of post's images Optional |
customFields Custom Fields | object | Any custom fields associated with the post. Each field name (key) must be between 0 and 30 characters long. If field values are strings, they must be less than 200 characters long. 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
- canny-create-post
- Version
- 0.0.1
- App
- Canny
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗