# How to connect Make to OpenClaw (paste one key, 25 tools) > Connect Make to OpenClaw with ClawLink: paste your Make key once and 25 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/make The usual route to Make access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Make setup: install one ClawHub skill, connect Make in the browser, and OpenClaw can call real Make actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/make ## Setup It takes three steps to connect OpenClaw to Make. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Make** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect make # connect Make (browser OAuth) npx -y @useclawlink/cli actions make # list available actions npx -y @useclawlink/cli run make --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Make in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Make API key once. Verify the connection by asking OpenClaw: > Create it in Make for me, then confirm the important fields before you finish. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Make is connected in the dashboard, that agent calls the same 25 Make tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Make MCP for OpenClaw Looking for a Make MCP server for OpenClaw? ClawLink connects Make to OpenClaw and exposes 25 Make tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Make integration](https://claw-link.dev/hermes/make) works the same way. ## What the OpenClaw Make integration can do 25 Make tools are ready for OpenClaw once the account is connected. ### All 25 Make tools for OpenClaw | Tool | What it does | |---|---| | **Create organizations** `make_create_organizations` | Create a new organization | | **Get cashier prices** `make_get_cashier_prices` | Get pricing details | | **Get cashier products** `make_get_cashier_products` | List available subscription products | | **Get current authorization** `make_get_current_authorization` | Get current authorization and scopes | | **Get enums imt regions** `make_get_enums_imt_regions` | List Make regions | | **Get enums llm models** `make_get_enums_llm_models` | List available LLM models | | **Get enums module types** `make_get_enums_module_types` | List module types | | **Get operations** `make_get_operations` | Get daily operations usage | | **Get users me** `make_get_users_me` | Get current user profile | | **List enums countries** `make_list_enums_countries` | List supported countries | | **List organizations** `make_list_organizations` | List organizations you belong to | | **List teams** `make_list_teams` | List teams in an organization | | **Ping API** `make_ping_api` | Ping Make API to verify connectivity | | **Get enums apps review statuses** `make_get_enums_apps_review_statuses` | Retrieve available app review statuses in Make | | **Get enums imt zones** `make_get_enums_imt_zones` | Retrieve available IMT zones in Make | | **Get enums organization features** `make_get_enums_organization_features` | Retrieve available organization features in Make | | **Get enums user API token scopes** `make_get_enums_user_api_token_scopes` | Retrieve all available API token scopes in Make | | **Get enums user email notifications** `make_get_enums_user_email_notifications` | Retrieve available email notification types for Make users | | **Get enums user features** `make_get_enums_user_features` | Retrieve the list of all existing user features and their descriptions | | **Get enums variable types** `make_get_enums_variable_types` | Retrieve available variable types in Make | | **List enums languages** `make_list_enums_languages` | Retrieve a list of language codes and names | | **List enums llm builtin tiers** `make_list_enums_llm_builtin_tiers` | Retrieve all predefined LLM tiers (small, medium, large) with their associated models | | **List enums locales** `make_list_enums_locales` | Retrieve all supported locales in Make | | **List enums timezones** `make_list_enums_timezones` | Retrieve all supported timezones in Make | | **Create users password reset demand** `make_create_users_password_reset_demand` | Create a password reset demand for a user by their email address | ## Example prompts **Create Organizations** > Create it in Make for me, then confirm the important fields before you finish. **Get Cashier Prices** > Pull the relevant data from Make, summarize it in plain English, and point out anything that needs attention. **Get Cashier Products** > Pull the relevant data from Make, summarize it in plain English, and point out anything that needs attention. **Get Current Authorization** > Pull the relevant data from Make, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Make working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Make API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Make account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Make. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Make actions to the runtime in a format your agent can reliably use. | 25 tools for Make are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Make to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Make in the browser, and the 25 tools above work from chat. There is no SDK and no config file, and the Make key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Make skill but can't call the tools The ClawHub skill teaches OpenClaw about Make, but the calls run through the ClawLink plugin and your connected account. Make sure Make is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Make from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Make tools Make tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Make call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Make returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Make has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Make integration? Yes. ClawLink is the fastest way to connect OpenClaw to Make: link your Make account once in the browser and OpenClaw can call the Make API through 25 ready-made tools — no custom code or token handling. ### How do I add Make to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Make skill from ClawHub, then you click Connect in the dashboard to authorize Make. OpenClaw calls the tools from the next message — no config files, and the Make key you paste is stored server-side instead of in your environment. ### How long does it take to connect Make to OpenClaw? About two minutes. Sign in, click Connect next to Make in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Make up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Make working from chat. ### OpenClaw installed the Make skill but can't call the tools The ClawHub skill teaches OpenClaw about Make, but the calls run through the ClawLink plugin and your connected account. Make sure Make is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [GitHub tools](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty tools](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.