monday ACTION
List Updates
List the updates (comments) posted on a board's items, including each update's ID, body and author. Use this to discover the
Parent Update ID required by Create an Update when replying to an existing update. Set Board ID. Example: Limit 25, Page 1. Returns an array of update objects, each carrying the item_id of the item it was posted on. If exactly Limit updates 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 Updates 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-updates",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
monday: { authProvisionId: "apn_xxxxxxx" },
boardId: "Board ID",
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-updates",
"configured_props": {
"monday": { "authProvisionId": "apn_xxxxxxx" },
"boardId": "Board ID",
"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-updates",
arguments: {
boardId: "Board ID",
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 |
|---|---|---|
boardId Board ID | string | The board to act on, as a board ID (e.g. 2419687965). Use List Board ID Options to look up a board ID by name. Required Dynamic |
limit Limit | integer | The maximum number of updates to return per page. Defaults to 25. If exactly this many updates are returned there are probably more, so call again with Page incremented by 1. Optional |
page Page | integer | The page number to return, starting at 1. Increment this to walk through updates when a call returns a full page of Limit results. 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-updates
- Version
- 0.0.1
- App
- monday
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗