monday ACTION
Create Board
Create a new board in a workspace. Use when you need a new board before adding groups, columns or items to it. Set
Board Name and Board Kind (public, private or share); if you omit Workspace ID the board is created in the Main Workspace. Example: Board Name Q3 Campaigns, Board Kind public. Returns the new board's ID as a string (e.g. 2419687965), not the full board object — call List Boards if you need its details. Use List Workspace ID Options to find a valid Workspace ID. See the documentation- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's monday account once, then configure and run Create Board 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: "monday-create-board",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
monday: { authProvisionId: "apn_xxxxxxx" },
boardName: "Board Name",
boardKind: "Board Kind",
},
})
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": "monday-create-board",
"configured_props": {
"monday": { "authProvisionId": "apn_xxxxxxx" },
"boardName": "Board Name",
"boardKind": "Board Kind"
}
}'// 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": "monday",
},
},
},
)
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: "monday-create-board",
arguments: {
boardName: "Board Name",
boardKind: "Board Kind",
},
})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 |
|---|---|---|
boardName Board Name | string | The new board's name Required |
boardKind Board Kind | string | Who can see the board: public (any account member), private (invited members only) or share (shareable with guests outside the account). Required |
workspaceId Workspace ID | integer | The workspace to create the board in, as a workspace ID (e.g. 12345). Use List Workspace ID Options to look up a workspace ID by name. Omit to use the account's Main Workspace. Optional Dynamic |
folderId Folder ID | integer | The folder to create the board in, as a folder ID. Use List Boards and read a board's board_folder_id to find a folder ID. Omit to leave the board outside any folder. Optional Dynamic |
templateId Board Template ID | integer | The board's template ID. You can obtain it from the URL when selecting the desired board (e.g. https://{subdomain}.monday.com/boards/2419687965) where 2419687965 is the template ID. See the documentation for more information 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
- monday-create-board
- Version
- 0.0.16
- App
- monday
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗