Run Claude inside your workflows on your own key

Claude in MadMax is a model provider, not an app to automate. Connect an Anthropic API key and the AI agent steps inside your workflows can run on Claude models of your choosing, billed to your Anthropic account. Everything around the agent stays the same: the trigger, the branches, the approval that waits for a person, the apps the agent reads from and writes to. The agent keeps its full task list (custom prompt with a JSON output schema, extract, classify, summarize) and its tools: calculator, browser, sandboxed code, your sub-workflows and any operation of a connected app, plus conversation memory and knowledge-base retrieval. You still describe the workflow in plain English and MadMax builds and verifies it, running each agent step on real upstream data and failing one that returns an empty object even though nothing crashed. The key only changes which model answers when a bound step runs; unbound steps run the platform default, so you can build first and bind Claude where the judgment matters.

What teams build

• A file upload trigger accepts a contract PDF, an extract task on Claude pulls parties, term, renewal date and governing law into named fields, and a store upsert keeps a row per contract so a scheduled check can email the owner 60 days before each renewal.
• An email trigger receives a customer's mail, a Claude custom-prompt agent bound to your help-center knowledge base drafts the reply and says when the answer is not in the material, and an approval shows the draft to a support agent with one-click approve or reject before it goes out.
• A GitHub pull request event starts a run, the diff and changed files come through the GitHub connection, and a Claude agent with the repository indexed in a knowledge base posts a review with inline comments as the MadMax bot.

How it connects

Paste an API key from the Anthropic console (it starts with sk-ant-) into Settings → connectors → Claude (Anthropic), or add it from an agent step's Provider picker without leaving the canvas. The key routes the agent steps you bind it to through Anthropic on your own account, and MadMax does not meter those calls. The canvas chat that builds and edits workflows always stays on the platform model. The live web-search tool is a platform-model feature a Claude-bound step ignores; the browser, code, workflow and connected-app tools still work. Rotating the key is a reconnect in place. See managing connections.

Related

• AI settings and models
• AI agent step
• Custom prompt task
• Managing connections
• Gemini on your own key