# How to connect Route4me to OpenClaw (paste one key, 97 tools) > Connect Route4me to OpenClaw with ClawLink: paste your Route4me key once and 97 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/route4me The usual route to Route4me 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 Route4me setup: install one ClawHub skill, connect Route4me in the browser, and OpenClaw can call real Route4me 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/route4me ## Setup It takes three steps to connect OpenClaw to Route4me. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Route4me** — 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 route4me # connect Route4me (browser OAuth) npx -y @useclawlink/cli actions route4me # list available actions npx -y @useclawlink/cli run route4me --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 Route4me in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Route4me API key once. Verify the connection by asking OpenClaw: > Use Route4me to add order custom field and walk me through the result in plain English. ### 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 Route4me is connected in the dashboard, that agent calls the same 97 Route4me 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). ## Route4me MCP for OpenClaw Looking for a Route4me MCP server for OpenClaw? ClawLink connects Route4me to OpenClaw and exposes 97 Route4me 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 Route4me integration](https://claw-link.dev/hermes/route4me) works the same way. ## What the OpenClaw Route4me integration can do 97 Route4me tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 97. ### 30 of 97 Route4me tools for OpenClaw | Tool | What it does | |---|---| | **Add order custom field** `route4me_add_order_custom_field` | Add a new custom field definition for orders | | **Add route note** `route4me_add_route_note` | Add a note to a route or address destination | | **Create address** `route4me_create_address` | Add a new address to the address book | | **Create avoidance zone** `route4me_create_avoidance_zone` | Create an avoidance zone with circular, rectangular, or polygon shape | | **Display datatable config** `route4me_display_datatable_config` | Retrieve datatable configuration for vehicle capacity profiles | | **Find address** `route4me_find_address` | Retrieve detailed information about a specific address from the Route4Me address book | | **Geocode address** `route4me_geocode_address` | Geocode an address and obtain its coordinates | | **Geocode address body** `route4me_geocode_address_body` | Geocode an address by sending a body payload with the address and options | | **Geocode address forward** `route4me_geocode_address_forward` | Convert an address to geographic coordinates using forward geocoding | | **Geocode addresses** `route4me_geocode_addresses` | Geocode multiple addresses in a single request | | **Get activity** `route4me_get_activity` | Retrieve activities from the Route4Me activity feed with optional filtering and pagination | | **Get address** `route4me_get_address` | Get address/destination information from a route | | **Get address book groups** `route4me_get_address_book_groups` | Retrieve address book groups from Route4Me | | **Get addresses from addressbook** `route4me_get_addresses_from_addressbook` | Retrieve addresses from the Route4Me address book | | **Get async export** `route4me_get_async_export` | Save tracking history file via async export | | **Get avoidance by ID** `route4me_get_avoidance_by_id` | Retrieve a specific avoidance zone by its territory ID | | **Get avoidance2** `route4me_get_avoidance2` | Retrieve all avoidance zones (territories) using API v5.0 | | **Get clustered locations** `route4me_get_clustered_locations` | Retrieve locations grouped by geographic proximity using geohash clustering | | **Get current member information** `route4me_get_current_member_information` | Retrieve the current authenticated member's information | | **Get feed** `route4me_get_feed` | Retrieve all activities from the Route4Me activity feed | | **Get last scheduled route member** `route4me_get_last_scheduled_route_member` | Retrieve the most recently scheduled route for a specific member as of today | | **Get location heatmap** `route4me_get_location_heatmap` | Retrieve a heat map of location clusters from the address book | | **Get location servicetime heatmap** `route4me_get_location_servicetime_heatmap` | Retrieve location service-time heatmap data for address book locations | | **Get location type** `route4me_get_location_type` | Get location type details by ID | | **Get member configuration settings** `route4me_get_member_configuration_settings` | Get member configuration settings with optional filtering | | **Get note custom types** `route4me_get_note_custom_types` | Retrieve all custom note types configured for the account | | **Get optimization profile** `route4me_get_optimization_profile` | Retrieve detailed information about an optimization profile by its unique identifier | | **Get route destination by ID** `route4me_get_route_destination_by_id` | Get a route address/destination by its ID | | **Get route info** `route4me_get_route_info` | Get detailed route information by route ID | | **Get route list** `route4me_get_route_list` | Retrieve a list of routes with filtering and pagination | ## Example prompts **Add Order Custom Field** > Use Route4me to add order custom field and walk me through the result in plain English. **Add Route Note** > Use Route4me to add route note and walk me through the result in plain English. **Create Address** > Create it in Route4me for me, then confirm the important fields before you finish. **Create Avoidance Zone** > Create it in Route4me for me, then confirm the important fields before you finish. ## 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 Route4me working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Route4me API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Route4me 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 Route4me. | 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 Route4me actions to the runtime in a format your agent can reliably use. | 97 tools for Route4me are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Route4me 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 Route4me in the browser, and the 97 tools above work from chat. There is no SDK and no config file, and the Route4me 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 Route4me skill but can't call the tools The ClawHub skill teaches OpenClaw about Route4me, but the calls run through the ClawLink plugin and your connected account. Make sure Route4me 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 Route4me 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 Route4me tools Route4me 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 Route4me 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. ### Route4me 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 Route4me has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Route4me integration? Yes. ClawLink is the fastest way to connect OpenClaw to Route4me: link your Route4me account once in the browser and OpenClaw can call the Route4me API through 97 ready-made tools — no custom code or token handling. ### How do I add Route4me to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Route4me skill from ClawHub, then you click Connect in the dashboard to authorize Route4me. OpenClaw calls the tools from the next message — no config files, and the Route4me key you paste is stored server-side instead of in your environment. ### How long does it take to connect Route4me to OpenClaw? About two minutes. Sign in, click Connect next to Route4me in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Route4me 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 Route4me working from chat. ### OpenClaw installed the Route4me skill but can't call the tools The ClawHub skill teaches OpenClaw about Route4me, but the calls run through the ClawLink plugin and your connected account. Make sure Route4me 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 - [OpenClaw DocuSign integration](https://claw-link.dev/openclaw/docusign) — Send, sign, and manage agreements and envelopes - [Connect Trello](https://claw-link.dev/openclaw/trello) — Manage boards, lists, and cards - [OpenClaw Moco integration](https://claw-link.dev/openclaw/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions.