# How to connect Countdown API to OpenClaw (paste one key, 25 tools) > Connect Countdown API to OpenClaw with ClawLink: paste your Countdown API 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/countdown-api The usual route to Countdown API 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 Countdown API setup: install one ClawHub skill, connect Countdown API in the browser, and OpenClaw can call real Countdown API 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 Countdown API. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Countdown API** — 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 countdown-api # connect Countdown API (browser OAuth) npx -y @useclawlink/cli actions countdown-api # list available actions npx -y @useclawlink/cli run countdown-api --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 Countdown API in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Countdown API API key once. Verify the connection by asking OpenClaw: > Use Countdown API to collections get collection 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 Countdown API is connected in the dashboard, that agent calls the same 25 Countdown API 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). ## Countdown API MCP for OpenClaw Looking for a Countdown API MCP server for OpenClaw? ClawLink connects Countdown API to OpenClaw and exposes 25 Countdown API 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 Countdown API integration](https://claw-link.dev/hermes/countdown-api) works the same way. ## What the OpenClaw Countdown API integration can do 25 Countdown API tools are ready for OpenClaw once the account is connected. The 22 below are the ones people reach for most; your agent can call all 25. ### 22 of 25 Countdown API tools for OpenClaw | Tool | What it does | |---|---| | **Collections get collection** `countdown_api_collections_get_collection` | Retrieve details for a single collection by ID | | **Collections list collections** `countdown_api_collections_list_collections` | List all collections for the authenticated account | | **Core API send request** `countdown_api_core_api_send_request` | Fetch eBay autocomplete suggestions | | **Destinations list destinations** `countdown_api_destinations_list_destinations` | List all destinations configured for the account | | **Find collection requests** `countdown_api_find_collection_requests` | Find requests in a collection by custom_id or search query | | **Get account** `countdown_api_get_account` | Retrieve account usage and current platform status | | **List error logs** `countdown_api_list_error_logs` | List error logs from collection executions | | **Requests export CSV** `countdown_api_requests_export_csv` | Export all requests from a collection as downloadable CSV files | | **Requests export json** `countdown_api_requests_export_json` | Download all requests in a collection as JSON | | **Results get result set** `countdown_api_results_get_result_set` | Retrieve a collection run's result set payload | | **Results list result sets** `countdown_api_results_list_result_sets` | List result sets produced by a collection | | **Collections create collection** `countdown_api_collections_create_collection` | Create a new collection | | **Collections start collection** `countdown_api_collections_start_collection` | Start processing a collection's queued requests on the Countdown API | | **Collections update collection** `countdown_api_collections_update_collection` | Update an existing collection's settings | | **Create collection request** `countdown_api_create_collection_request` | Create new requests within a collection for bulk eBay data retrieval | | **Create destination** `countdown_api_create_destination` | Creates a cloud storage destination where batch result sets will be automatically uploaded | | **Requests update single request** `countdown_api_requests_update_single_request` | Modify parameters of an existing request in a collection | | **Results resend result set webhook** `countdown_api_results_resend_result_set_webhook` | Resend the webhook notification for a collection's result set | | **Stop all collections** `countdown_api_stop_all_collections` | Stop all collections | | **Stop collection** `countdown_api_stop_collection` | Stop (pause) a single collection’s processing by ID | | **Update destination** `countdown_api_update_destination` | Update a destination's configuration by ID | | **Clear all requests** `countdown_api_clear_all_requests` | Clears (removes) all pending requests from a collection | ## Example prompts **Collections Get Collection** > Use Countdown API to collections get collection and walk me through the result in plain English. **Collections List Collections** > Use Countdown API to collections list collections and walk me through the result in plain English. **Core Api Send Request** > Use Countdown API to core api send request and walk me through the result in plain English. **Destinations List Destinations** > Use Countdown API to destinations list destinations 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 Countdown API working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Countdown API API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Countdown API 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 Countdown API. | 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 Countdown API actions to the runtime in a format your agent can reliably use. | 25 tools for Countdown API are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Countdown API 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 Countdown API in the browser, and the 25 tools above work from chat. There is no SDK and no config file, and the Countdown API 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 Countdown API skill but can't call the tools The ClawHub skill teaches OpenClaw about Countdown API, but the calls run through the ClawLink plugin and your connected account. Make sure Countdown API 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 Countdown API 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 Countdown API tools Countdown API 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 Countdown API 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. ### Countdown API 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 Countdown API has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Countdown API integration? Yes. ClawLink is the fastest way to connect OpenClaw to Countdown API: link your Countdown API account once in the browser and OpenClaw can call the Countdown API API through 25 ready-made tools — no custom code or token handling. ### How do I add Countdown API to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Countdown API skill from ClawHub, then you click Connect in the dashboard to authorize Countdown API. OpenClaw calls the tools from the next message — no config files, and the Countdown API key you paste is stored server-side instead of in your environment. ### How long does it take to connect Countdown API to OpenClaw? About two minutes. Sign in, click Connect next to Countdown API in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Countdown API 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 Countdown API working from chat. ### OpenClaw installed the Countdown API skill but can't call the tools The ClawHub skill teaches OpenClaw about Countdown API, but the calls run through the ClawLink plugin and your connected account. Make sure Countdown API 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](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [Connect 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.