# How to connect 7shifts to OpenClaw (paste one key, 10 tools) > Connect 7shifts to OpenClaw with ClawLink: paste your 7shifts key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/7shifts The usual route to 7shifts 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 7shifts setup: install one ClawHub skill, connect 7shifts in the browser, and OpenClaw can call real 7shifts 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 7shifts. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect 7shifts** — 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 7shifts # connect 7shifts (browser OAuth) npx -y @useclawlink/cli actions 7shifts # list available actions npx -y @useclawlink/cli run 7shifts --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 7shifts in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your 7shifts API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from 7shifts, summarize it in plain English, and point out anything that needs attention. ### 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 7shifts is connected in the dashboard, that agent calls the same 10 7shifts 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). ## 7shifts MCP for OpenClaw Looking for a 7shifts MCP server for OpenClaw? ClawLink connects 7shifts to OpenClaw and exposes 10 7shifts 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 7shifts integration](https://claw-link.dev/hermes/7shifts) works the same way. ## What the OpenClaw 7shifts integration can do 10 7shifts tools are ready for OpenClaw once the account is connected. The 9 below are the ones people reach for most; your agent can call all 10. ### 9 of 10 7shifts tools for OpenClaw | Tool | What it does | |---|---| | **Get department** `7shifts_get_department` | Return one department by company and department ID | | **Get user assignments** `7shifts_get_user_assignments` | Return one user's assigned locations, departments, and roles in a single read | | **List companies** `7shifts_list_companies` | Return companies available to the connected access token, including the company IDs needed by | | **List departments** `7shifts_list_departments` | List one page of departments in a company, optionally filtered by location or modification | | **List locations** `7shifts_list_locations` | List one page of locations in a company and return location IDs used to filter schedules | | **List shifts** `7shifts_list_shifts` | List one page of scheduled shifts for a company with employee, location, department, role | | **List users** `7shifts_list_users` | List employees and administrators in a 7shifts company, with optional status, name, and one | | **Create department** `7shifts_create_department` | Create a department at a company location, optionally make it the location's default | | **Update department** `7shifts_update_department` | Replace a department's name and default setting | ## Example prompts **Get Department** > Pull the relevant data from 7shifts, summarize it in plain English, and point out anything that needs attention. **Get User Assignments** > Pull the relevant data from 7shifts, summarize it in plain English, and point out anything that needs attention. **List Companies** > List the relevant items in 7shifts, group them by priority, and recommend what OpenClaw should do next. **List Departments** > List the relevant items in 7shifts, group them by priority, and recommend what OpenClaw should do next. ## 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 7shifts working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the 7shifts API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected 7shifts 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 7shifts. | 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 7shifts actions to the runtime in a format your agent can reliably use. | 10 tools for 7shifts are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes 7shifts 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 7shifts in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the 7shifts 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 7shifts skill but can't call the tools The ClawHub skill teaches OpenClaw about 7shifts, but the calls run through the ClawLink plugin and your connected account. Make sure 7shifts 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 7shifts 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 7shifts tools 7shifts 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 7shifts 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. ### 7shifts 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 7shifts has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw 7shifts integration? Yes. ClawLink is the fastest way to connect OpenClaw to 7shifts: link your 7shifts account once in the browser and OpenClaw can call the 7shifts API through 10 ready-made tools — no custom code or token handling. ### How do I add 7shifts to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink 7shifts skill from ClawHub, then you click Connect in the dashboard to authorize 7shifts. OpenClaw calls the tools from the next message — no config files, and the 7shifts key you paste is stored server-side instead of in your environment. ### How long does it take to connect 7shifts to OpenClaw? About two minutes. Sign in, click Connect next to 7shifts in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring 7shifts 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 7shifts working from chat. ### OpenClaw installed the 7shifts skill but can't call the tools The ClawHub skill teaches OpenClaw about 7shifts, but the calls run through the ClawLink plugin and your connected account. Make sure 7shifts 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 - [Greenhouse](https://claw-link.dev/openclaw/greenhouse) — Manage jobs, candidates, applications, and interviews - [Ashby](https://claw-link.dev/openclaw/ashby) — Ashby delivers an applicant tracking system for modern teams, offering features like job postings, candidate management, and data-driven hiring insights to streamline the recruitment process. - [OpenClaw Lever integration](https://claw-link.dev/openclaw/lever) — Manage candidates, opportunities, interviews, and requisitions