# How to connect SafetyCulture to OpenClaw (paste one key, 255 tools) > Connect SafetyCulture to OpenClaw with ClawLink: paste your SafetyCulture key once and 255 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/safetyculture The usual route to SafetyCulture 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 SafetyCulture setup: install one ClawHub skill, connect SafetyCulture in the browser, and OpenClaw can call real SafetyCulture actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/safetyculture ## Setup It takes three steps to connect OpenClaw to SafetyCulture. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect SafetyCulture** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **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 safetyculture # connect SafetyCulture (browser OAuth) npx -y @useclawlink/cli actions safetyculture # list available actions npx -y @useclawlink/cli run safetyculture --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 SafetyCulture in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your SafetyCulture API key once. Verify the connection by asking OpenClaw: > Use SafetyCulture to add file owners bulk 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 SafetyCulture is connected in the dashboard, that agent calls the same 255 SafetyCulture 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). ## SafetyCulture MCP for OpenClaw Looking for a SafetyCulture MCP server for OpenClaw? ClawLink connects SafetyCulture to OpenClaw and exposes 255 SafetyCulture 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 SafetyCulture integration](https://claw-link.dev/hermes/safetyculture) works the same way. ## What the OpenClaw SafetyCulture integration can do 255 SafetyCulture tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 255. ### 30 of 255 SafetyCulture tools for OpenClaw | Tool | What it does | |---|---| | **Add file owners bulk** `safetyculture_add_file_owners_bulk` | Bulk add file owners to multiple files in Documents | | **Add incident collaborators** `safetyculture_add_incident_collaborators` | Add collaborators (assignees) to an incident in SafetyCulture | | **Archive asset** `safetyculture_archive_asset` | Archives an asset in your SafetyCulture organization | | **Archive document item** `safetyculture_archive_document_item` | Archive a document item (file or folder) in SafetyCulture | | **Get action assignees feed** `safetyculture_get_action_assignees_feed` | Retrieve the data feed for action assignees | | **Get actions** `safetyculture_get_actions` | List actions from SafetyCulture tasks API | | **Get asset** `safetyculture_get_asset` | Retrieve full details of an asset from SafetyCulture | | **Get asset by code** `safetyculture_get_asset_by_code` | Retrieve an asset's full details using its code | | **Get asset type** `safetyculture_get_asset_type` | Retrieves details of a specific asset type by ID | | **Get assets feed** `safetyculture_get_assets_feed` | Retrieve a data feed of all assets in your SafetyCulture organization | | **Get credential type** `safetyculture_get_credential_type` | Retrieve details of a specific credential type by ID | | **Get credentials settings** `safetyculture_get_credentials_settings` | Retrieve credential settings for your SafetyCulture organization | | **Get directory folder** `safetyculture_get_directory_folder` | Retrieves details of a specific directory folder by ID | | **Get directory folder users** `safetyculture_get_directory_folder_users` | Retrieves users associated with a directory folder, including both directly and indirectly | | **Get directory folder users associated** `safetyculture_get_directory_folder_users_associated` | Retrieve users directly associated to a folder | | **Get directory folder users inherited** `safetyculture_get_directory_folder_users_inherited` | Retrieves users indirectly associated (inherited) to a folder | | **Get directory organization labels** `safetyculture_get_directory_organization_labels` | Retrieve custom labels mapping for your SafetyCulture organization | | **Get directory parent folders** `safetyculture_get_directory_parent_folders` | Retrieves child folders for a specific parent folder by ID | | **Get documents** `safetyculture_get_documents` | Retrieve a paginated list of credentials from SafetyCulture | | **Get incident questions and answers** `safetyculture_get_incident_questions_and_answers` | Retrieve questions and answers for a specific incident (issue) in SafetyCulture | | **Get incidents categories detail fields** `safetyculture_get_incidents_categories_detail_fields` | Retrieve detail fields for a specific incident category | | **Get incidents count** `safetyculture_get_incidents_count` | Get the total count of incidents (issues) in SafetyCulture | | **Get incidents investigation** `safetyculture_get_incidents_investigation` | Retrieve a specific investigation from SafetyCulture | | **Get incidents osha establishm hours** `safetyculture_get_incidents_osha_establishm_hours` | Retrieve establishment hours from SafetyCulture OSHA service | | **Get incidents osha establishment employees** `safetyculture_get_incidents_osha_establishment_employees` | Retrieve establishment employee records from SafetyCulture OSHA | | **Get incidents osha establishments** `safetyculture_get_incidents_osha_establishments` | Retrieve an OSHA establishment record from SafetyCulture | | **Get integrations apps installation** `safetyculture_get_integrations_apps_installation` | Retrieve details of a specific app installation by its app ID and installation ID | | **Get investigation access** `safetyculture_get_investigation_access` | Retrieve access information for a specific investigation | | **Get investigation actions count** `safetyculture_get_investigation_actions_count` | Retrieve the count of actions linked to a specific investigation in SafetyCulture | | **Get investigation inspection count** `safetyculture_get_investigation_inspection_count` | Retrieve the count of inspections linked to a specific investigation | ## Example prompts **Add File Owners Bulk** > Use SafetyCulture to add file owners bulk and walk me through the result in plain English. **Add Incident Collaborators** > Use SafetyCulture to add incident collaborators and walk me through the result in plain English. **Archive Asset** > Before using SafetyCulture to archive asset, show me what will change and ask for confirmation. **Archive Document Item** > Before using SafetyCulture to archive document item, show me what will change and ask for confirmation. ## 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 SafetyCulture working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the SafetyCulture API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected SafetyCulture 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 SafetyCulture. | 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 SafetyCulture actions to the runtime in a format your agent can reliably use. | 255 tools for SafetyCulture are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes SafetyCulture 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 SafetyCulture in the browser, and the 255 tools above work from chat. There is no SDK and no config file, and the SafetyCulture 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 SafetyCulture skill but can't call the tools The ClawHub skill teaches OpenClaw about SafetyCulture, but the calls run through the ClawLink plugin and your connected account. Make sure SafetyCulture 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 SafetyCulture 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 SafetyCulture tools SafetyCulture 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 SafetyCulture 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. ### SafetyCulture 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 SafetyCulture has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw SafetyCulture integration? Yes. ClawLink is the fastest way to connect OpenClaw to SafetyCulture: link your SafetyCulture account once in the browser and OpenClaw can call the SafetyCulture API through 255 ready-made tools — no custom code or token handling. ### How do I add SafetyCulture to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink SafetyCulture skill from ClawHub, then you click Connect in the dashboard to authorize SafetyCulture. OpenClaw calls the tools from the next message — no config files, and the SafetyCulture key you paste is stored server-side instead of in your environment. ### How long does it take to connect SafetyCulture to OpenClaw? About two minutes. Sign in, click Connect next to SafetyCulture in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring SafetyCulture 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 SafetyCulture working from chat. ### OpenClaw installed the SafetyCulture skill but can't call the tools The ClawHub skill teaches OpenClaw about SafetyCulture, but the calls run through the ClawLink plugin and your connected account. Make sure SafetyCulture 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](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [OpenClaw PagerDuty integration](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [LaunchDarkly](https://claw-link.dev/openclaw/launch-darkly) — A feature management platform that helps teams build better software faster using feature flags.