How to connect SafetyCulture to Hermes Agent
Connect SafetyCulture to Hermes with ClawLink: paste your SafetyCulture key once and 255 tools work from chat. No MCP server to run, nothing stored on your machine.
SafetyCultureAPI KEYMCPSafetyCulture (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.. Once connected, Hermes Agent can read and act on SafetyCulture from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent SafetyCulture access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical SafetyCulture setup: pair once in the browser and your always-on Hermes agent can act on SafetyCulture for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into Hermes to install the plugin and pair your account.
Set up ClawLink for Hermes and tell me when it's ready.
1. Install the plugin:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
2. Start pairing. It prints an approval link, so show me the link and stop, don't wait:
hermes clawlink begin
3. I'll approve it in my browser, then reply "approved".
4. When I say approved, finish setup:
hermes clawlink finish
5. Then run `hermes clawlink test` and tell me whether ClawLink is ready.Setup
It takes three steps to connect Hermes to SafetyCulture.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect SafetyCulture
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with SafetyCulture?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin # prints an approval link — open it and approve
hermes clawlink finish # after approving in the browser
hermes clawlink testThen connect SafetyCulture in the ClawLink dashboard — paste your SafetyCulture API key once.
Verify the connection by asking Hermes:
Use SafetyCulture to add file owners bulk and walk me through the result in plain English.
Using a different agent?
The Hermes 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 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.
SafetyCulture MCP for Hermes
Looking for a SafetyCulture MCP server for Hermes Agent? ClawLink connects SafetyCulture to Hermes Agent and exposes 255 SafetyCulture tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw SafetyCulture integration works the same way.
What the Hermes Agent SafetyCulture integration can do
255 SafetyCulture tools are ready for Hermes Agent 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 Hermes
| 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 |
Try it: find the SafetyCulture tool you need
Browse the 30 SafetyCulture tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Use SafetyCulture to add file owners bulk and walk me through the result in plain English.
Use SafetyCulture to add incident collaborators and walk me through the result in plain English.
Before using SafetyCulture to archive asset, show me what will change and ask for confirmation.
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 Hermes Agent. 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 Hermes Agent 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 comparison.
Troubleshooting
Hermes paired but still can't use SafetyCulture
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
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.
FAQ
Is there a Hermes Agent SafetyCulture integration?
Yes. ClawLink is the fastest way to connect Hermes to SafetyCulture: link your SafetyCulture account once in the browser and Hermes Agent can call the SafetyCulture API through 255 ready-made tools — no custom code or token handling.
How do I connect SafetyCulture to Hermes with ClawLink?
Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect SafetyCulture in the dashboard and Hermes can use it 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 Hermes Agent?
About two minutes. Sign in, click Connect next to SafetyCulture in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want SafetyCulture working from chat.
Hermes paired but still can't use SafetyCulture
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
