monday ACTION
List Workspace ID Options
List the account's workspaces as
{ value, label } option pairs, to discover a Workspace ID to pass to Create Board or to filter List Boards. Use when you know a workspace by name but need its ID. Example: call with Page 1; returns e.g. [{ "value": 12345, "label": "Marketing" }]. Returns at most Limit workspaces per page (25 by default), so if exactly Limit come back there are probably more — call again with Page incremented by 1. See the documentation- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's monday account once, then configure and run List Workspace ID Options 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-list-workspace-id-options",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
monday: { authProvisionId: "apn_xxxxxxx" },
page: 10,
limit: 10,
},
})
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-list-workspace-id-options",
"configured_props": {
"monday": { "authProvisionId": "apn_xxxxxxx" },
"page": 10,
"limit": 10
}
}'// 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-list-workspace-id-options",
arguments: {
page: 10,
limit: 10,
},
})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 |
|---|---|---|
page Page | integer | The page of results to retrieve, starting at 1. Increment this to walk through workspaces when a call returns a full page of results. Optional |
limit Limit | integer | The maximum number of workspaces to return per page. Defaults to 25. If exactly this many are returned there are probably more, so call again with Page incremented by 1. 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-list-workspace-id-options
- Version
- 0.0.4
- App
- monday
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗