ServiceM8
Manage jobs, clients, staff, scheduling and materials in ServiceM8, a field-service management platform for trades businesses.
About
ServiceM8 ships in the w6w first-party pack. It declares 18 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.servicem8- Version
- 0.1.1
- Author
- w6w
- Licence
- MIT
- Categories
- Customer Relationship Management · Calendar & Scheduling · Finance & Accounting
Overview
ServiceM8 manages the day-to-day of a field-service business — Jobs (Quotes, Work Orders and Completed jobs), Clients, staff scheduling, and the line items on a Job’s Quote or Invoice — over ServiceM8’s own REST API. Jobs and clients can be listed, read, created and updated, scheduling entries (job activities) can be listed and created, and quote/invoice line items and job notes can be added directly.
Because ServiceM8’s API key carries no scope restriction, every action available to this app is available to any connection, and creating or updating a record returns only an acknowledgement — reading the fields back always means a follow-up read of the same record by its id. Deleting a job archives it rather than erasing it; the record and its full history stay reachable afterward.
List actions expose ServiceM8’s own generic filter and cursor-based pagination rather than inventing per-field parameters the vendor doesn’t document. Attachments, webhook subscriptions and OAuth2 are left out, since each needs a wire format or a partner registration this integration can’t yet verify end to end.
Build with ServiceM8
Three routes to the same 18 actions. The Workflow tab is generated from ServiceM8's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Find Categories
category-list List Job Categories, with optional $filter/$sort and cursor pagination.
Find Clients
company-list List Clients (the Company resource), with optional $filter/$sort and cursor pagination.
Update Client
company-update Update fields on an existing Client. Only the fields you set here are sent.
Create Job
job-create Create a Job (Quote / Work Order). Returns only the new UUID — fetch the full record with Get Job if you need it back.
Find Jobs
job-list List Jobs — Quotes, Work Orders, Unsuccessful and Completed — with optional $filter/$sort and cursor pagination.
Create Job Activity
jobactivity-create Schedule a booking or record time against a Job. Returns only the new UUID.
Find Job Activities
jobactivity-list List Job Activities — scheduled bookings AND recorded time entries are both this resource; filter on activity_was_scheduled to distinguish them.
Create Job Material
jobmaterial-create Add a line item to a Job's Quote/Invoice. Returns only the new UUID.
Get Account Info
vendor-get The connected ServiceM8 account's own business profile — name, email, currency, business hours, invoice terms.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying ServiceM8's real ids.
{
"manifestVersion": "2",
"name": "servicem8-example",
"steps": [
{
"id": "company-create",
"uses": {
"app": "io.w6w.servicem8",
"action": "company-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"name": "<name>"
}
}
]
}Here are some of the things you can do
-
Create Client
performcompany-create -
Find Categories
searchcategory-list -
Get Client
readcompany-get -
Find Clients
searchcompany-list -
Update Client
performcompany-update
+13 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for ServiceM8, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to ServiceM8. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "company-create",
payload: {
name: "<value>",
// address: "<value>",
// billingAddress: "<value>",
// website: "<value>",
// isIndividual: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action company-create --payload '{"name":"<value>"}'Give an AI agent ServiceM8 — without giving it ServiceM8's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.servicem8#company-create",
"input": {
"name": "<name>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's ServiceM8 connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
ServiceM8's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. ServiceM8 itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
ServiceM8 declares its own checks, so its health is a property of the app rather than something the host guesses at.
ServiceM8 platform status
ServiceM8 API reachability
Unsigned GET https://api.servicem8.com/api_1.0/vendor.json. A 401 with ServiceM8's own plain-text "Authorization Required" body is the pass: it proves the API routed and answered. This says nothing about any credential.