Productivity · Integration
ServiceMax
Add ServiceMax to your product for your customers, and give your AI agents governed access to it.
ServiceMax is field service management organised around equipment rather than tickets, so the record that matters is the installed product at a site and the work orders raised against it. An embedded ServiceMax integration creates and updates those work orders, reads the installed base and its service history, reads service requests and technician assignments, and writes back what a technician actually did, including the parts consumed and the time recorded. Two things about the product shape the build. ServiceMax Core runs on the Salesforce platform, so every org carries its own custom fields, record types and validation rules and the API follows that org rather than a fixed schema. And field work happens where signal often does not, so a completion can arrive hours after the visit and your writes have to tolerate that ordering. fastn keeps each org's credentials per tenant and follows the platform changes.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own ServiceMax org so a fault your product detects is raised as a work order against the equipment it belongs to.
Read the installed products at a site so your product knows what is under contract before it commits an engineer to a visit.
Write completion detail back onto a work order, including parts consumed and time recorded, once the job closes.
Map the custom fields and record types that org has grown on the Salesforce platform as configuration held per tenant rather than logic you have to maintain.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent lists the work orders open at a site and says which are waiting on a part rather than an engineer.
An agent reads the service history of one installed product before it answers a warranty question.
An agent reschedules or reassigns a visit inside scoped permissions, with the change attributed to the org that authorised it.
Example prompt
What is still open on this site, and does the history of that chiller show the same fault coming back?
Set up ServiceMax in 4 steps
- 01Enable the ServiceMax connector in your fastn dashboard.
- 02Have each customer authorise their own ServiceMax org, since Core is reached through the Salesforce platform it runs on.
- 03Map the work order, installed product and service request fields that org uses, including its custom fields, then enable the actions you need.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the ServiceMax integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a ServiceMax integration without building it. Your customers connect their own ServiceMax 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 ServiceMax update is not your on-call problem.
- One integration serves your product and your agents. The same governed ServiceMax 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
ServiceM8
SimproWorks well with
SalesforceOften used alongside
Tools the same teams tend to run next to ServiceMax, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServiceServiceMax integration FAQ
How do I add a ServiceMax integration to my product?
Enable the ServiceMax connector in your fastn dashboard, then let each customer authenticate their own ServiceMax account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no ServiceMax client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own ServiceMax account?
Yes. Every connection is scoped to the individual customer, so each authorises their own ServiceMax 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 ServiceMax 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 lists the work orders open at a site and says which are waiting on a part rather than an engineer.
Who maintains the ServiceMax integration?
fastn does. When ServiceMax 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 ServiceMax automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in ServiceMax can trigger your workflows in return.
Does it adapt to each team's own ServiceMax setup?
Yes. However a team has configured ServiceMax, 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 ServiceMax integration?
A common starting point: let each customer connect their own ServiceMax org so a fault your product detects is raised as a work order against the equipment it belongs to. 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 ServiceMax integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding ServiceMax does not change your per-connector cost. You can start free with 3 connected accounts.
Add ServiceMax to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.