# How to connect OneTapCheckIn to OpenClaw (paste one key, 19 tools) > Connect OneTapCheckIn to OpenClaw with ClawLink: paste your OneTapCheckIn key once and 19 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/onetapcheckin The usual route to OneTapCheckIn 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 OneTapCheckIn setup: install one ClawHub skill, connect OneTapCheckIn in the browser, and OpenClaw can call real OneTapCheckIn 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 OneTapCheckIn. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect OneTapCheckIn** — 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 onetapcheckin # connect OneTapCheckIn (browser OAuth) npx -y @useclawlink/cli actions onetapcheckin # list available actions npx -y @useclawlink/cli run onetapcheckin --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 OneTapCheckIn in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your OneTapCheckIn API key once. Verify the connection by asking OpenClaw: > Use OneTapCheckIn to find lists 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 OneTapCheckIn is connected in the dashboard, that agent calls the same 19 OneTapCheckIn 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). ## OneTapCheckIn MCP for OpenClaw Looking for a OneTapCheckIn MCP server for OpenClaw? ClawLink connects OneTapCheckIn to OpenClaw and exposes 19 OneTapCheckIn 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 OneTapCheckIn integration](https://claw-link.dev/hermes/onetapcheckin) works the same way. ## What the OpenClaw OneTapCheckIn integration can do 19 OneTapCheckIn tools are ready for OpenClaw once the account is connected. The 17 below are the ones people reach for most; your agent can call all 19. ### 17 of 19 OneTapCheckIn tools for OpenClaw | Tool | What it does | |---|---| | **Find lists** `onetapcheckin_find_lists` | Get one list by exact ID or search the connected organization's lists | | **Find participants** `onetapcheckin_find_participants` | Get one participant by exact ID or search attendance records by list, profile, status, text, or | | **Find profiles** `onetapcheckin_find_profiles` | Get one profile by ID or search profiles by identity, list, passport, or check-in code | | **Get organization** `onetapcheckin_get_organization` | Return the organization associated with the connected API key | | **Get profile custom fields** `onetapcheckin_get_profile_custom_fields` | Return the organization's configured profile custom-field definitions so an agent can use valid | | **List alerts** `onetapcheckin_list_alerts` | Return one page of organization alert and automation rules together with outbound check-in | | **List passports** `onetapcheckin_list_passports` | List one page of standard passports for exactly one profile or participant | | **Add participants** `onetapcheckin_add_participants` | Add one or more existing profiles to one or more lists without checking them in | | **Create list** `onetapcheckin_create_list` | Create an event/check-in list | | **Create profile** `onetapcheckin_create_profile` | Create one person profile without adding it to a list | | **Create profiles** `onetapcheckin_create_profiles` | Create 1 to 25 person profiles in input order using one provider request per profile | | **Update list** `onetapcheckin_update_list` | Partially update a list | | **Update participant** `onetapcheckin_update_participant` | Update metadata on one participant record without performing check-in or checkout | | **Update participant attendance** `onetapcheckin_update_participant_attendance` | Check in, check out, undo check-in, or undo checkout for one known participant | | **Update participant attendance batch** `onetapcheckin_update_participant_attendance_batch` | Apply one shared check-in, checkout, undo check-in, or undo checkout operation to 1 to 25 | | **Update profile** `onetapcheckin_update_profile` | Partially update one profile | | **Remove participant** `onetapcheckin_remove_participant` | Remove one participant record from its list | ## Example prompts **Find Lists** > Use OneTapCheckIn to find lists and walk me through the result in plain English. **Find Participants** > Use OneTapCheckIn to find participants and walk me through the result in plain English. **Find Profiles** > Use OneTapCheckIn to find profiles and walk me through the result in plain English. **Get Organization** > Pull the relevant data from OneTapCheckIn, 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 OneTapCheckIn working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the OneTapCheckIn API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected OneTapCheckIn 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 OneTapCheckIn. | 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 OneTapCheckIn actions to the runtime in a format your agent can reliably use. | 19 tools for OneTapCheckIn are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes OneTapCheckIn 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 OneTapCheckIn in the browser, and the 19 tools above work from chat. There is no SDK and no config file, and the OneTapCheckIn 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 OneTapCheckIn skill but can't call the tools The ClawHub skill teaches OpenClaw about OneTapCheckIn, but the calls run through the ClawLink plugin and your connected account. Make sure OneTapCheckIn 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 OneTapCheckIn 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 OneTapCheckIn tools OneTapCheckIn 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 OneTapCheckIn 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. ### OneTapCheckIn 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 OneTapCheckIn has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw OneTapCheckIn integration? Yes. ClawLink is the fastest way to connect OpenClaw to OneTapCheckIn: link your OneTapCheckIn account once in the browser and OpenClaw can call the OneTapCheckIn API through 19 ready-made tools — no custom code or token handling. ### How do I add OneTapCheckIn to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink OneTapCheckIn skill from ClawHub, then you click Connect in the dashboard to authorize OneTapCheckIn. OpenClaw calls the tools from the next message — no config files, and the OneTapCheckIn key you paste is stored server-side instead of in your environment. ### How long does it take to connect OneTapCheckIn to OpenClaw? About two minutes. Sign in, click Connect next to OneTapCheckIn in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring OneTapCheckIn 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 OneTapCheckIn working from chat. ### OpenClaw installed the OneTapCheckIn skill but can't call the tools The ClawHub skill teaches OpenClaw about OneTapCheckIn, but the calls run through the ClawLink plugin and your connected account. Make sure OneTapCheckIn 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 - [Cal.com](https://claw-link.dev/openclaw/cal) — Schedule and manage bookings through Cal.com - [Bookingmood](https://claw-link.dev/openclaw/bookingmood) — Bookingmood provides flexible, commission-free booking software for rental businesses of all sizes, enabling seamless integration with your website. - [Connect Eventbrite](https://claw-link.dev/openclaw/eventbrite) — Create and manage events, tickets, and attendees