Skip to main content

Connect Monday to Goose

Give Goose governed access to Monday’s 101 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add Monday to Goose in four steps

Admins approve the server once. Everyone in Goose then gets it through the same governed connection.

  1. 1

    Approve Monday in Runlayer

    Add Monday from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Goose to Runlayer

    Users add the Runlayer Plugin as a Goose extension; Goose has no native plugin install. Goose reaches Monday’s 101 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Goose setup guide
  3. 3

    Sign in to Monday

    Sign in the way Monday requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Monday from Goose

    Monday’s approved tools appear in Goose. Every call is checked against policy and recorded.

Tools

101 Monday tools in Goose

Runlayer policy decides which of these Goose users can call.

  • Agent catalog

    Browse the account-wide catalog of available trigger types and skills for monday platform agents.

  • Read all API

    Execute read-only GraphQL queries against the monday.com API.

  • Write all API

    Execute GraphQL mutations against the monday.com API to create, update, or delete data.

  • All Monday API

    Execute any monday.com API operation by generating GraphQL queries and mutations dynamically.

  • All widgets schema

    Fetch complete JSON Schema 7 definitions for all available widget types in monday.com.

  • Board insights

    Allows you to calculate insights about board's data by filtering, grouping and aggregating columns.

  • Change item column values

    Change the column values of a single item on a monday.com board.

  • Connect external agent

    Connect a custom external agent (an agent running on your own server/infra) to monday.com.

See all 101 Monday tools

Control

What Runlayer can see and stop in Goose

Some controls apply to every client at the gateway. Others depend on what Goose exposes to Runlayer.

  • Gateway policy (available)

    Every Monday call from Goose passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Goose as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Goose runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Goose’s model sees it.

  • Redact output in place (not available)

    Goose cannot apply masking, so Runlayer blocks output it would otherwise mask. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination