# How to connect Shipday to OpenClaw (paste one key, 12 tools) > Connect Shipday to OpenClaw with ClawLink: paste your Shipday key once and 12 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/shipday The usual route to Shipday 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 Shipday setup: install one ClawHub skill, connect Shipday in the browser, and OpenClaw can call real Shipday actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Shipday. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Shipday** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **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 shipday # connect Shipday (browser OAuth) npx -y @useclawlink/cli actions shipday # list available actions npx -y @useclawlink/cli run shipday --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 Shipday in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Shipday API key once. Verify the connection by asking OpenClaw: > Use Shipday to check on demand availability 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 Shipday is connected in the dashboard, that agent calls the same 12 Shipday 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). ## Shipday MCP for OpenClaw Looking for a Shipday MCP server for OpenClaw? ClawLink connects Shipday to OpenClaw and exposes 12 Shipday 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 Shipday integration](https://claw-link.dev/hermes/shipday) works the same way. ## What the OpenClaw Shipday integration can do 12 Shipday tools are ready for OpenClaw once the account is connected. ### All 12 Shipday tools for OpenClaw | Tool | What it does | |---|---| | **Check on demand availability** `shipday_check_on_demand_availability` | Check on-demand delivery availability from third-party service providers | | **Get on demand estimate** `shipday_get_on_demand_estimate` | Get on-demand delivery estimates from third-party service providers for a specific order | | **Get on demand services** `shipday_get_on_demand_services` | Retrieve available third-party on-demand delivery service providers | | **Query delivery orders** `shipday_query_delivery_orders` | Query delivery orders with time-based filters and cursor pagination | | **Retrieve active orders** `shipday_retrieve_active_orders` | Retrieve all active delivery orders from Shipday system | | **Retrieve carriers** `shipday_retrieve_carriers` | Retrieve all carriers/drivers with profile and status details | | **Retrieve order details** `shipday_retrieve_order_details` | Retrieve detailed information for a specific delivery order by order number | | **Add a carrier** `shipday_add_a_carrier` | Add a new carrier/driver to the Shipday system with credentials | | **Edit delivery order** `shipday_edit_delivery_order` | Edit an existing delivery order in Shipday | | **Insert order** `shipday_insert_order` | Create a new delivery order in Shipday | | **Order ready to pickup** `shipday_order_ready_to_pickup` | Mark a delivery order as ready for pickup | | **Unassign order from driver** `shipday_unassign_order_from_driver` | Remove driver assignment from a delivery order | ## Example prompts **Check On Demand Availability** > Use Shipday to check on demand availability and walk me through the result in plain English. **Get On Demand Estimate** > Pull the relevant data from Shipday, summarize it in plain English, and point out anything that needs attention. **Get On Demand Services** > Pull the relevant data from Shipday, summarize it in plain English, and point out anything that needs attention. **Query Delivery Orders** > Use Shipday to query delivery orders and walk me through the result in plain English. ## 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 Shipday working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Shipday API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Shipday 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 Shipday. | 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 Shipday actions to the runtime in a format your agent can reliably use. | 12 tools for Shipday are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Shipday 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 Shipday in the browser, and the 12 tools above work from chat. There is no SDK and no config file, and the Shipday 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 Shipday skill but can't call the tools The ClawHub skill teaches OpenClaw about Shipday, but the calls run through the ClawLink plugin and your connected account. Make sure Shipday 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 Shipday 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 Shipday tools Shipday 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 Shipday 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. ### Shipday 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 Shipday has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Shipday integration? Yes. ClawLink is the fastest way to connect OpenClaw to Shipday: link your Shipday account once in the browser and OpenClaw can call the Shipday API through 12 ready-made tools — no custom code or token handling. ### How do I add Shipday to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Shipday skill from ClawHub, then you click Connect in the dashboard to authorize Shipday. OpenClaw calls the tools from the next message — no config files, and the Shipday key you paste is stored server-side instead of in your environment. ### How long does it take to connect Shipday to OpenClaw? About two minutes. Sign in, click Connect next to Shipday in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Shipday 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 Shipday working from chat. ### OpenClaw installed the Shipday skill but can't call the tools The ClawHub skill teaches OpenClaw about Shipday, but the calls run through the ClawLink plugin and your connected account. Make sure Shipday 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 - [Cloudcart](https://claw-link.dev/openclaw/cloudcart) — CloudCart is an e-commerce platform that enables businesses to create and manage online stores efficiently. - [Wix tools](https://claw-link.dev/openclaw/wix) — Manage sites, products, orders, and bookings - [OpenClaw Baselinker integration](https://claw-link.dev/openclaw/baselinker) — BaseLinker is a comprehensive e-commerce management platform that integrates with various marketplaces, online stores, carriers, and accounting systems to streamline order processing, inventory management, and sales automation.