How to connect Slite to OpenClaw
Connect Slite to OpenClaw with ClawLink: paste your Slite key once and 16 tools work from chat. No MCP server to run, nothing stored on your machine.
SliteAPI KEYMCPYour company knowledge base, on autopilot.. Once connected, OpenClaw can read and act on Slite from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Slite 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 Slite setup: install one ClawHub skill, connect Slite in the browser, and OpenClaw can call real Slite 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 Slite.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Slite
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Slite?"
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:
openclaw plugins install clawhub:clawlink-pluginThen 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 Slite in the ClawLink dashboard — paste your Slite API key once.
Verify the connection by asking OpenClaw:
Use Slite to ask question 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Slite is connected in the dashboard, that agent calls the same 16 Slite tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Slite MCP for OpenClaw
Looking for a Slite MCP server for OpenClaw? ClawLink connects Slite to OpenClaw and exposes 16 Slite tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Slite integration works the same way.
What the OpenClaw Slite integration can do
16 Slite tools are ready for OpenClaw once the account is connected. The 15 below are the ones people reach for most; your agent can call all 16.
15 of 16 Slite tools for OpenClaw
| Tool | What it does |
|---|---|
Ask question slite_ask_question | Ask a question to your Slite notes in natural language |
Get authenticated user slite_get_authenticated_user | Retrieves information about the currently authenticated user |
Get note by ID slite_get_note_by_id | Retrieve a complete note by its ID including content in Markdown or HTML format |
Get note children slite_get_note_children | Retrieve note children by parent note ID |
List notes slite_list_notes | List notes from Slite with optional filtering by owner |
Search groups slite_search_groups | Search for groups by name in Slite |
Search notes slite_search_notes | Search notes based on a query with optional filters |
Search users slite_search_users | Search for users in Slite by email, name, or username |
Create note slite_create_note | Create a note from markdown or HTML content with optional template |
Flag note as outdated slite_flag_note_as_outdated | Set Outdated status on a note with a reason |
Update note slite_update_note | Update a note's content with markdown and/or title |
Update note archived state slite_update_note_archived_state | Update the archived state of a note in Slite |
Update note owner slite_update_note_owner | Update the owner of a note |
Update tile slite_update_tile | Update or create a tile within a Slite note with structured header and markdown content |
Verify note slite_verify_note | Set a note's verification status to Verified with optional expiration |
Try it: find the Slite tool you need
Browse the 15 Slite tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Slite to ask question and walk me through the result in plain English.
Pull the relevant data from Slite, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Slite, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Slite, 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 Slite working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Slite API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Slite 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 Slite. | 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 Slite actions to the runtime in a format your agent can reliably use. | 16 tools for Slite are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Slite 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 Slite in the browser, and the 16 tools above work from chat. There is no SDK and no config file, and the Slite key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Slite skill but can't call the tools
The ClawHub skill teaches OpenClaw about Slite, but the calls run through the ClawLink plugin and your connected account. Make sure Slite 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 Slite 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 Slite tools
Slite 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 Slite 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.
Slite 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 Slite has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Slite integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Slite: link your Slite account once in the browser and OpenClaw can call the Slite API through 16 ready-made tools — no custom code or token handling.
How do I add Slite to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Slite skill from ClawHub, then you click Connect in the dashboard to authorize Slite. OpenClaw calls the tools from the next message — no config files, and the Slite key you paste is stored server-side instead of in your environment.
How long does it take to connect Slite to OpenClaw?
About two minutes. Sign in, click Connect next to Slite in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Slite 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 Slite working from chat.
OpenClaw installed the Slite skill but can't call the tools
The ClawHub skill teaches OpenClaw about Slite, but the calls run through the ClawLink plugin and your connected account. Make sure Slite 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
Connect GitHub
Manage repositories, issues, pull requests, and workflows
PagerDuty tools
Manage incidents, on-call schedules, and services
SafetyCulture tools
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.