Manage Agent Triggers (Platform MCP)
Lists, adds, or removes the triggers attached to a monday platform agent — triggers define when the agent runs automatically — using the Platform MCP.
Use this tool to manage the triggers attached to a monday platform agent. Triggers define when the agent runs automatically.
This tool runs against the monday.com dev (preview) API schema. Only triggers that can be added programmatically appear in agent_catalog. OAuth / third-party triggers (Slack, Gmail, Salesforce, etc.) require user setup in the monday.com UI and cannot be managed here.
| Action | Required fields | Description |
|---|---|---|
list | agent_id | Returns active triggers with node_id, block_reference_id, name, and field summary. |
add | agent_id, block_reference_id | Attaches a trigger type to the agent. |
remove | agent_id, node_id | Detaches a trigger instance by node_id (not block_reference_id). |
To add a trigger: call agent_catalog action: "list_triggers" to find the block_reference_id, field_schemas, and required_fields; collect the required field values from the user; then call action: "add". The add response returns only { success } — call action: "list" afterward if you need the new instance's node_id.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| action | enum | Yes | One of list, add, remove. |
| agent_id | string | Yes | Unique identifier of the agent. |
| block_reference_id | string | Conditional | Required for add. The trigger type's block_reference_id from agent_catalog action: "list_triggers". Never guess this value. |
| field_values | object | No | Used with add when the trigger type has required fields. Key/value object whose shape is described by field_schemas in the catalog. Scalar fields use string/number/boolean; selection fields use { "value": "<id>", "label": "<name>" }. |
| node_id | string | Conditional | Required for remove. The node_id of the trigger instance — get it from action: "list". Each instance has a unique node_id. |
Examples
List the triggers on an agent:
{
"action": "list",
"agent_id": "7"
}Add a trigger by its catalog reference:
{
"action": "add",
"agent_id": "7",
"block_reference_id": "status-change-ref",
"field_values": { "board_id": "42" }
}Remove a trigger instance:
{
"action": "remove",
"agent_id": "7",
"node_id": "node-abc"
}Related tools
- agent_catalog — discover available trigger types and their required
field_values. - manage_agent_skills — manage which skills this agent can perform.
- manage_agent — manage the agent entity itself.
Programmatic equivalent
This tool maps to the agent_active_triggers query and add_trigger_to_agent / remove_trigger_from_agent mutations on the monday.com dev (preview) API schema. There is no stable public GraphQL equivalent yet.
Updated about 4 hours ago
