Connect n8n to CLEATUS
Use CLEATUS in n8n through the MCP Client Tool in an AI Agent workflow, or through the REST API in an HTTP Request node.
n8n connects to CLEATUS in two ways. An AI Agent workflow uses the CLEATUS Model Context Protocol (MCP) server through the MCP Client Tool node. A fixed, scheduled workflow calls the CLEATUS REST API from an HTTP Request node with an API key.
Who this is for
This article is for CLEATUS users who build automations in n8n. Examples are a daily opportunity digest, a sync from your pipeline to another system, and alerts in Slack or Microsoft Teams.
Choose a method
| MCP Client Tool | HTTP Request | |
|---|---|---|
| Use it for | AI Agent workflows that decide which CLEATUS tool to call | Fixed steps that run on a schedule or a trigger |
| Sign-in | Your CLEATUS sign-in (OAuth) | A CLEATUS API key in the X-Api-Key header |
| CLEATUS plan | DATA + AI or higher | DATA + AI + Automations or higher |
Your subscription must be active, or your trial must be started.
Use the MCP Client Tool
- In an n8n workflow with an AI Agent node, add the MCP Client Tool node as a tool of the agent.
- Set the endpoint to
https://www.cleat.ai/api/mcp/mcpand the transport to HTTP Streamable. - Set authentication to OAuth. On the first run, the Connect to CLEATUS page opens. Sign in, pick the company under Select company, and click Authorize.
- Test it. Ask the agent: "Pull my top five CLEATUS recommendations and summarize why each fits."
The agent can then search opportunities, read solicitations, manage your pipeline and tasks, and run your CLEATUS workflows.
Use the REST API
1. Create an API key
In CLEATUS, open Settings > Integrations. In the Data & Automation section, click Manage on the API Keys card, then create a key. Choose Read-only unless the workflow must change data. CLEATUS shows the key only once, so save it as an n8n credential right away. Full steps: CLEATUS REST API and API keys.
2. Add an HTTP Request node
Point the node at an endpoint under https://api.cleat.ai/api/v1, and send the key in the X-Api-Key header. For example, this request gets your highest-scoring recommendations:
GET https://api.cleat.ai/api/v1/recommendations?limit=5&min_score=80
X-Api-Key: <your API key>
The API reference lists every endpoint.
3. Build the workflow
A typical workflow is: Schedule Trigger > HTTP Request to CLEATUS > Filter > a Slack, Teams, or email node.
Troubleshooting
- 401 errors from the HTTP Request node. The key is wrong, revoked, or expired, or it is not in the
X-Api-Keyheader. The REST API does not accept a Bearer token. - 403 errors with
api_tier_insufficient. The REST API is on the DATA + AI + Automations plan and above. Upgrade your plan, or use the MCP Client Tool instead. - The MCP Client Tool finds no pipeline, tasks, or saved searches. You picked the wrong company during sign-in. Sign in again and pick the correct company.
- Rate-limit errors. Each key or sign-in gets 100 reads and 30 writes per minute. Add a Wait node between calls in a loop.
- Still stuck? Email support@cleat.ai with the time of the failing request.
Related
- CLEATUS MCP Server: the endpoint, authentication, and rate limits.
- CLEATUS REST API and API keys: keys, endpoints, pagination, and errors.
- Integrate Zapier with CLEATUS: the same kind of automation with no code.
- For more example workflows, see cleat.ai/agents/n8n.