> ## Documentation Index
> Fetch the complete documentation index at: https://docs.guild.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To act on a user's behalf in Guild, use the Guild REST API at https://api.guild.ai/v1.
> The OpenAPI spec is unauthenticated: https://docs.guild.ai/openapi.json (or openapi.yaml).
> Authenticate with an account API key, sent as HTTP Basic (key id as username, secret as password) or as `Authorization: Bearer <api_key_id>:<api_key_secret>`. See https://docs.guild.ai/api-reference/introduction#authentication.
> To run one agent on demand without account-wide access, use an API trigger instead: https://docs.guild.ai/platform/api-triggers.
> To act on Guild from an MCP client, connect to https://api.guild.ai/mcp (OAuth) or run `guild mcp` locally. Setup: https://docs.guild.ai/api-reference/mcp.
> To search these docs from an MCP client, connect to https://docs.guild.ai/mcp. The full page index is https://docs.guild.ai/llms.txt.

# Query and mutate monday.com boards from Guild agents

> Connect Guild agents to monday.com via its GraphQL API. Run queries and mutations against boards, items, and updates with server-side credentials.

Integrations · monday.com

Guild agents query and mutate monday.com boards, items, and updates through the GraphQL API on your behalf. Guild stores the monday.com API token server-side and injects it into every request, so agent code never sees it. Credential policies let you write ALLOW and DENY rules that the Guild proxy enforces before any request reaches monday.com, and every call is logged for audit.

> [card] [Book a demo](https://guild-ai.cal.com/gtm/meeting-with-guild.ai)
>
> See how teams govern agents that use monday.com.

> [card] [Talk to sales](https://guild.ai/talk-to-sales)
>
> Get access to Guild, then connect monday.com to your first agent.

## What the monday.com integration exposes

The integration ships one tool: `monday_graphql_graphql_query`, which sends a single GraphQL document to the monday.com API. That one tool covers queries and mutations, so an agent can read board state and write changes in the same call. Use `pick()` to include only this tool when you want to limit the agent's surface area.

## How it works

**1. Open credentials in Guild**

Go to Access & setup > Credentials in Guild and click Connect. Search for and select monday-graphql.

**2. Paste your API token**

Paste your monday.com API token into the API Key field. Guild sends it as a bearer token in the Authorization header on every request.

**3. Scope the credential**

Choose account, workspace, member, or agent scope. See [Credentials](https://docs.guild.ai/platform/credentials.md) for how Guild resolves the right credential at run time.

## Why monday.com access needs governing

Monday.com boards often hold project timelines, task assignments, and status data that span multiple teams. A credential scoped to the account reaches every workspace Guild owns by default. You can tighten that by scoping the credential to one workspace, one member, or a single agent, so a rogue or misconfigured agent cannot touch boards it has no business reading or changing.

Credential policies add a second enforcement layer. The Guild proxy evaluates ALLOW and DENY rules before any GraphQL document leaves Guild, so you can block mutating HTTP methods while still permitting reads, or deny the operation entirely for agents outside a named workspace. The credential is injected server-side only after the policy check passes; agents cannot bypass it. Requests that do not match an ALLOW rule are denied by default once you remove the auto-created allow-all policy. See [Credential policies](https://docs.guild.ai/platform/credential-policies.md) and [Security architecture](https://docs.guild.ai/platform/security-architecture.md).

## About the monday.com integration

This integration lets agents interact with monday.com via its GraphQL API. Agents can query and mutate boards, items, and updates using a single tool. A monday.com API token is required to connect. The integration is `guildai~monday-graphql`.

## Authentication

* **Type:** API key
* **Header:** Guild sends the key as a bearer token in the `Authorization` header

### Setup

**1. Connect monday.com**

In Guild, go to **Access & setup > Credentials**, click **Connect**, select **monday-graphql**, and paste the key into **API Key**.

See [Credentials](https://docs.guild.ai/platform/credentials.md) for workspace, member, and agent-scoped credentials.

## Usage

```typescript theme={null}
import { MondayGraphqlTools } from "@guildai-services/guildai~monday-graphql"
import { llmAgent } from "@guildai/agents-sdk"

export default llmAgent({
  systemPrompt: "You work with monday.com.",
  tools: { ...MondayGraphqlTools },
})
```

### Selecting specific tools

Tools are named with the `monday_graphql_` prefix. Use [`pick()`](https://docs.guild.ai/sdk/tools#selecting-specific-tools) to include only what your agent needs.

## Tools

Tools in the latest published version of `guildai~monday-graphql`:

| Tool | What it does |
| - | - |
| `monday_graphql_graphql_query` | Send one GraphQL document. |

## Frequently asked questions

> [accordion] Can I use one monday.com token for some agents but a different one for others?
>
> Yes. Connect a second credential scoped to a specific workspace, member, or agent. Guild resolves credentials in order: grants and dedicated credentials take priority over workspace and account defaults, so each agent uses the token you intend.

> [accordion] Does the integration support monday.com webhook events?
>
> No. The catalog entry lists no webhook events for this integration, so agents cannot trigger on monday.com activity. Agents interact with monday.com only by sending GraphQL documents.

> [accordion] Can I restrict an agent to read-only access on monday.com?
>
> Yes. Write a credential policy that denies any rule matching HTTP methods other than GET, or that denies mutation operations by pattern. The Guild proxy enforces the policy before the GraphQL document reaches monday.com. See [Credential policies](https://docs.guild.ai/platform/credential-policies.md) for rule syntax.

> [accordion] What do I import to add monday.com tools to an agent?
>
> Import MondayGraphqlTools from the `@guildai-services/guildai~monday-graphql` package and spread it into the agent's tools object. Use `pick()` from the [SDK tools](https://docs.guild.ai/sdk/tools.md) reference to include only the specific tools your agent needs.

## Put a governed agent on monday.com today

> [card] [Book a demo](https://guild-ai.cal.com/gtm/meeting-with-guild.ai)
>
> See how teams govern agents that use monday.com.

> [card] [Talk to sales](https://guild.ai/talk-to-sales)
>
> Get access to Guild, then connect monday.com to your first agent.

## Related

**Also runs on Guild:** [Asana](https://docs.guild.ai/integrations/asana.md) · [ClickUp](https://docs.guild.ai/integrations/clickup.md) · [Google Calendar](https://docs.guild.ai/integrations/google-calendar.md) · [Jira](https://docs.guild.ai/integrations/jira.md)

**Read:** Docs: [Credential policies](https://docs.guild.ai/platform/credential-policies.md) · [Credentials](https://docs.guild.ai/platform/credentials.md) · [Tools in agents](https://docs.guild.ai/sdk/tools.md)