How to connect Servicem8 to OpenClaw (no API keys)

The usual route to Servicem8 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 Servicem8 setup: install one ClawHub skill, connect Servicem8 in the browser, and OpenClaw can call real Servicem8 actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.

Copy this prompt into OpenClaw, or open the Servicem8 skill on ClawHub.

Prompt for OpenClaw

Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Servicem8" (hith3sh/servicem8) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/servicem8
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Setup

It takes three steps to connect OpenClaw to Servicem8.

1
Install 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 Servicem8
One-click OAuth in the dashboard.
3
Use it from chat
Ask OpenClaw: "What can you do with Servicem8?"

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-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 Servicem8 in the ClawLink dashboard — a one-click OAuth approval, no API keys.

Verify the connection by asking OpenClaw:

List the relevant items in Servicem8, group them by priority, and recommend what OpenClaw should do next.

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 login

login opens the same browser approval and stores a credential locally. Once Servicem8 is connected in the dashboard, that agent calls the same 28 Servicem8 tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.

Servicem8 MCP for OpenClaw

Looking for a Servicem8 MCP server for OpenClaw? ClawLink connects Servicem8 to OpenClaw and exposes 28 Servicem8 tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Servicem8 integration works the same way.

What the OpenClaw Servicem8 integration can do

28 Servicem8 tools are ready for OpenClaw once the account is connected. The 25 below are the ones people reach for most; your agent can call all 28.

25 of 28 Servicem8 tools for OpenClaw

Tool	What it does
List all assets `servicem8_list_all_assets`	List all ServiceM8 assets
List all clients `servicem8_list_all_clients`	List all ServiceM8 clients
List all document templates `servicem8_list_all_document_templates`	List document templates
List all forms `servicem8_list_all_forms`	List all ServiceM8 forms
List all job notes `servicem8_list_all_job_notes`	List all job notes from ServiceM8
List all job queues `servicem8_list_all_job_queues`	List all job queues in ServiceM8
List all jobs `servicem8_list_all_jobs`	List all jobs
List all locations `servicem8_list_all_locations`	Lists all ServiceM8 locations
List all materials `servicem8_list_all_materials`	Retrieve all materials (products, labour rates, inventory items) from ServiceM8
List all tasks `servicem8_list_all_tasks`	Retrieves all tasks from a ServiceM8 account with optional filtering and cursor-based pagination
Retrieve client `servicem8_retrieve_client`	Retrieve details of a specific client by its UUID
Retrieve form `servicem8_retrieve_form`	Retrieve details of a specific form template by its UUID
Retrieve job `servicem8_retrieve_job`	Retrieve details of a specific job by its UUID
Retrieve job activity `servicem8_retrieve_job_activity`	Retrieve details of a specific job activity by its UUID
Retrieve job note `servicem8_retrieve_job_note`	Retrieve the full details of a specific job note by its UUID
Retrieve job payment `servicem8_retrieve_job_payment`	Retrieve a specific job payment record from ServiceM8 by its UUID
Retrieve job queue `servicem8_retrieve_job_queue`	Retrieve details of a specific job queue by its UUID
Retrieve location `servicem8_retrieve_location`	Retrieve a specific ServiceM8 location by its UUID
Retrieve material `servicem8_retrieve_material`	Retrieve detailed information about a specific material/product/service by its UUID
Retrieve staff member `servicem8_retrieve_staff_member`	Retrieve details of a specific staff member by their UUID
Create job note `servicem8_create_job_note`	Create a new job note in ServiceM8
Create job payment `servicem8_create_job_payment`	Create a new job payment in ServiceM8
Create jobs `servicem8_create_jobs`	Create a new Job in ServiceM8
Update job note `servicem8_update_job_note`	Update details of an existing job note
Update job payment `servicem8_update_job_payment`	Update an existing job payment record in ServiceM8

Try it: find the Servicem8 tool you need

Browse the 25 Servicem8 tools

Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.

Example prompts

List the relevant items in Servicem8, group them by priority, and recommend what OpenClaw should do next.

ClawLink vs. building it yourself

The alternative to ClawLink is usually manual OAuth app 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 Servicem8 working from chat.

	Manual	ClawLink
Connection flow	Register a Servicem8 app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift.	Users connect Servicem8 through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code.
Ongoing maintenance	You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Servicem8.	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 Servicem8 actions to the runtime in a format your agent can reliably use.	28 tools for Servicem8 are already exposed through ClawLink, so the agent can read and act from chat immediately.

ClawLink vs. Composio

Composio also exposes Servicem8 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 Servicem8 in the browser, and the 28 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.

Troubleshooting

OpenClaw installed the Servicem8 skill but can't call the tools

The ClawHub skill teaches OpenClaw about Servicem8, but the calls run through the ClawLink plugin and your connected account. Make sure Servicem8 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 Servicem8 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 Servicem8 tools

Servicem8 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 Servicem8 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.

Servicem8 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.

OAuth finished in the browser but the account is still missing

Try reconnecting Servicem8 and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.

FAQ

Is there a OpenClaw Servicem8 integration?

Yes. ClawLink is the fastest way to connect OpenClaw to Servicem8: link your Servicem8 account once in the browser and OpenClaw can call the Servicem8 API through 28 ready-made tools — no custom code or token handling.

How do I add Servicem8 to OpenClaw with ClawLink?

Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Servicem8 skill from ClawHub, then you click Connect in the dashboard to authorize Servicem8. OpenClaw calls the tools from the next message — no config files or API keys to manage.

How long does it take to connect Servicem8 to OpenClaw?

About two minutes. Sign in, click Connect next to Servicem8 in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

Why use ClawLink instead of wiring Servicem8 up myself?

OpenClaw installed the Servicem8 skill but can't call the tools

How to connect Servicem8 to OpenClaw

Setup

Install the plugin

Connect Servicem8

Use it from chat