Skip to main content
Claude answers questions about your boards, items, users, and teams by calling Engini tools - it never sees a monday API key or an HTTP request. This is the canonical Engini agent loop; every other agent recipe is a variation of it. Prerequisites: an Engini API key (ENGINI_API_KEY), an Anthropic API key (ANTHROPIC_API_KEY), and a monday.com connection on your account (engini connect monday creates one).

1. Client + toolset

The whole app-specific surface is three SDK calls:

2. One helper Anthropic needs

handle_tool_calls returns one result message per tool call; Anthropic expects all tool_result blocks for one assistant turn in a single user message:

3. The agent loop

That’s the whole agent: think → call tools → observe → repeat, until the model stops asking for tools. Keep appending to the same messages list across user turns and you have a chat assistant with memory.

Run the original

The runnable version (interactive chat loop, .env handling, connection pinning via ENGINI_MONDAY_CONNECTION) lives at python/examples/monday-agent/:

Try another app

Swap "monday" for any connector on your account (salesforce, gmail, shopify…) - list what’s connected:
The Priority ERP recipe is exactly this substitution.