Planview Leankit ACTION
Find OR Create Card
Find or create a new card. See the docs here
- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Planview Leankit account once, then configure and run Find OR Create Card 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: "planview_leankit-find-or-create-card",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
planview_leankit: { authProvisionId: "apn_xxxxxxx" },
boardId: "Board 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": "planview_leankit-find-or-create-card",
"configured_props": {
"planview_leankit": { "authProvisionId": "apn_xxxxxxx" },
"boardId": "Board 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": "planview_leankit",
},
},
},
)
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: "planview_leankit-find-or-create-card",
arguments: {
boardId: "Board 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 |
|---|---|---|
boardId Board ID | string | The ID of the board Required Dynamic |
title Title | string | The card title Required |
laneId Lane Id | string | The ID of the lane Optional Dynamic |
customId Custom ID | string | The card header Optional |
typeId Type ID | string | The ID of the type Optional Dynamic |
customIconId Custom Icon ID | string | The custom icon Optional Dynamic |
laneClassTypes Lane Class Types | string | Only return cards in lane class types specified in a csv list. Optional |
since Since | string | Only return cards updated after this ISO8601 date. String format: YYYY-MM-DD Optional |
deleted Deleted | boolean | Return the card IDs for deleted cards Optional |
only Only | string | Return only the fields specified in a csv list. Optional |
omit Omit | string | Return all fields except the ones specified in a csv list. Optional |
sort Sort | string | Sort results by. Defaults to rank if there is a search param, otherwise activity. 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
- planview_leankit-find-or-create-card
- Version
- 0.0.3
- App
- Planview Leankit
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗