Productivity · Integration
ServiceM8
Add ServiceM8 to your product for your customers, and give your AI agents governed access to it.
ServiceM8 runs the day for trade and field service businesses, so its records describe work in the world rather than tickets in a queue: a job for a client at an address, job activities that are the scheduled visits against it, the staff member dispatched, the materials used, and the forms and photographs captured while somebody was standing there. An embedded ServiceM8 integration lets your product create a job and put it on the schedule, then read back what happened once the visit is done, which is where most of the useful detail appears. Every business configures its own job categories, queues, badges and forms, so those are mapped per customer rather than assumed. fastn holds the per-tenant credentials, paginates the reads and keeps the connector current.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own ServiceM8 account so jobs your product generates reach the field without anyone retyping them.
Create a job with its client, address and description, then schedule the job activity so it lands in somebody's day.
Read job status, materials used and staff assigned so your product shows what was actually done on site.
Read the forms and photographs captured during a visit, so evidence from the field is available in your product.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which jobs are scheduled today and which have no staff member assigned yet.
An agent creates or reschedules a job within governed permissions, with the write attributed to the tenant that authorised it.
An agent reads a completed job's notes, materials and forms before answering what a visit involved.
Example prompt
Which jobs were completed this week without a form attached, and which are still unscheduled?
Set up ServiceM8 in 4 steps
- 01Enable the ServiceM8 connector in your fastn dashboard.
- 02Have each customer authorise their own ServiceM8 account with OAuth.
- 03Map the job, job activity, client, staff and materials fields your product uses, including that business's own queues, badges and forms.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the ServiceM8 integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a ServiceM8 integration without building it. Your customers connect their own ServiceM8 account inside your product and work their work items, assignees and due dates there, with no per-customer code on your side.
- Handle the part that actually costs time: every team configures its own fields, statuses and workflow stages. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a ServiceM8 update is not your on-call problem.
- One integration serves your product and your agents. The same governed ServiceM8 connection powers in-product features and gives AI agents scoped, audited access, so you keep work items in step with what happens in your product without wiring it twice.
Used by these teams
Compare with
SafetyCultureWorks well with
Xero
QuickBooksOften used alongside
Tools the same teams tend to run next to ServiceM8, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServiceServiceM8 integration FAQ
How do I add a ServiceM8 integration to my product?
Enable the ServiceM8 connector in your fastn dashboard, then let each customer authenticate their own ServiceM8 account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no ServiceM8 client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own ServiceM8 account?
Yes. Every connection is scoped to the individual customer, so each authorises their own ServiceM8 account and only ever sees their own work items, assignees and due dates. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this ServiceM8 integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports which jobs are scheduled today and which have no staff member assigned yet.
Who maintains the ServiceM8 integration?
fastn does. When ServiceM8 changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product create and update work in ServiceM8 automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in ServiceM8 can trigger your workflows in return.
Does it adapt to each team's own ServiceM8 setup?
Yes. However a team has configured ServiceM8, whether that is custom fields, statuses and workflow stages or its own calendars and working hours, those are mapped per customer, so an unusual setup works without custom code from you.
What can I build with the ServiceM8 integration?
A common starting point: let each customer connect their own ServiceM8 account so jobs your product generates reach the field without anyone retyping them. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the ServiceM8 integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding ServiceM8 does not change your per-connector cost. You can start free with 3 connected accounts.
Add ServiceM8 to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.