How to connect Conveyor to OpenClaw
Connect Conveyor to OpenClaw with ClawLink: paste your Conveyor key once and 25 tools work from chat. No MCP server to run, nothing stored on your machine.
ConveyorAPI KEYMCPConveyor is a platform that automates security reviews by providing a Trust Center, AI-driven questionnaire automation, and integrations with various tools to streamline compliance processes.. Once connected, OpenClaw can read and act on Conveyor from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Conveyor 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 Conveyor setup: install one ClawHub skill, connect Conveyor in the browser, and OpenClaw can call real Conveyor 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 Conveyor.
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 Conveyor
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Conveyor?"
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 Conveyor in the ClawLink dashboard — paste your Conveyor API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Conveyor, 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Conveyor is connected in the dashboard, that agent calls the same 25 Conveyor tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Conveyor MCP for OpenClaw
Looking for a Conveyor MCP server for OpenClaw? ClawLink connects Conveyor to OpenClaw and exposes 25 Conveyor tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Conveyor integration works the same way.
What the OpenClaw Conveyor integration can do
25 Conveyor tools are ready for OpenClaw once the account is connected. The 23 below are the ones people reach for most; your agent can call all 25.
23 of 25 Conveyor tools for OpenClaw
| Tool | What it does |
|---|---|
Get access groups conveyor_get_access_groups | Retrieve all access groups for a program |
Get authorization request conveyor_get_authorization_request | Retrieves details of a specific authorization request from Conveyor Exchange by its ID |
Get authorization requests conveyor_get_authorization_requests | Retrieves authorization requests from Conveyor's Trust Center |
Get authorizations conveyor_get_authorizations | Retrieve authorizations from your Conveyor Trust Center |
Get connections conveyor_get_connections | Retrieve all connections |
Get documents conveyor_get_documents | Retrieves all documents from the Conveyor trust center |
Get folders conveyor_get_folders | Retrieves all folders from the Conveyor Exchange workspace |
Get interactions conveyor_get_interactions | Get all interactions (document interactions, q&a interactions) with optional filters |
Get interactions by connection ID conveyor_get_interactions_by_connection_id | Fetch interactions associated with a specific connection |
Get interactions by document ID conveyor_get_interactions_by_document_id | Fetch interactions associated with a specific document |
Get knowledge base questions conveyor_get_knowledge_base_questions | Retrieves knowledge base questions from Conveyor |
Get product lines conveyor_get_product_lines | Retrieves all product lines configured in Conveyor |
Get questionnaires conveyor_get_questionnaires | Retrieves all questionnaires from Conveyor with optional filters |
Post single question conveyor_post_single_question | Submit a single question to Conveyor's AI knowledge base and receive an immediate answer |
Patch document conveyor_patch_document | Update a Conveyor document's metadata |
Patch questionnaire request conveyor_patch_questionnaire_request | Update a questionnaire request in Conveyor |
Post authorization conveyor_post_authorization | Create a new authorization in Conveyor Exchange |
Post document conveyor_post_document | Upload a new document to Conveyor's Knowledge Library |
Post folder conveyor_post_folder | Create a new folder in Conveyor Exchange |
Post questionnaire conveyor_post_questionnaire | Submit a new questionnaire to Conveyor |
Post questionnaire request conveyor_post_questionnaire_request | Create a new questionnaire request in Conveyor |
Post review conveyor_post_review | Create a review in Conveyor with optional references to external VM unique IDs |
Patch authorization conveyor_patch_authorization | Update an existing authorization by revoking access or modifying Access Group assignments |
Try it: find the Conveyor tool you need
Browse the 23 Conveyor tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Conveyor, 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 Conveyor working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Conveyor API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Conveyor 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 Conveyor. | 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 Conveyor actions to the runtime in a format your agent can reliably use. | 25 tools for Conveyor are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Conveyor 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 Conveyor in the browser, and the 25 tools above work from chat. There is no SDK and no config file, and the Conveyor 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 Conveyor skill but can't call the tools
The ClawHub skill teaches OpenClaw about Conveyor, but the calls run through the ClawLink plugin and your connected account. Make sure Conveyor 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 Conveyor 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 Conveyor tools
Conveyor 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 Conveyor 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.
Conveyor 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 Conveyor 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 Conveyor integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Conveyor: link your Conveyor account once in the browser and OpenClaw can call the Conveyor API through 25 ready-made tools — no custom code or token handling.
How do I add Conveyor to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Conveyor skill from ClawHub, then you click Connect in the dashboard to authorize Conveyor. OpenClaw calls the tools from the next message — no config files, and the Conveyor key you paste is stored server-side instead of in your environment.
How long does it take to connect Conveyor to OpenClaw?
About two minutes. Sign in, click Connect next to Conveyor in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Conveyor 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 Conveyor working from chat.
OpenClaw installed the Conveyor skill but can't call the tools
The ClawHub skill teaches OpenClaw about Conveyor, but the calls run through the ClawLink plugin and your connected account. Make sure Conveyor 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
OpenClaw GitHub integration
Manage repositories, issues, pull requests, and workflows
PagerDuty
Manage incidents, on-call schedules, and services
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.