Productivity · Integration
eMaint X5
Add eMaint X5 to your product for your customers, and give your AI agents governed access to it.
Embed an eMaint X5 integration so your customers can work their own work orders, work requests, assets, preventive maintenance schedules, and parts records from inside your product. Every maintenance team configures its own statuses, priorities, and custom fields, so those are mapped per customer as configuration rather than hard-coded by you. fastn handles per-tenant authorisation and API upkeep, so a customer with an unusual setup does not become a special case in your codebase.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers raise work orders in their own eMaint X5 account directly from your product.
Read asset records and maintenance history so your product shows the full service record for equipment.
Update work order status, assignee, and completion details so technicians do not switch tools to close a job.
Trigger your product when a work order is created, assigned, or completed.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads open work orders and maintenance history before answering a question about an asset.
An agent creates or updates a work order within governed permissions, with the action logged.
An agent reacts to a completed work order and runs the next follow-up step.
Example prompt
List open work orders on this asset that are past their due date and show who they are assigned to.
Set up eMaint X5 in 4 steps
- 01Open the eMaint X5 connector from your fastn dashboard.
- 02Have each customer authenticate their own eMaint X5 account.
- 03Map the work order statuses, asset records, and custom fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the eMaint X5 integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an eMaint X5 integration without building it. Your customers connect their own eMaint X5 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 an eMaint X5 update is not your on-call problem.
- One integration serves your product and your agents. The same governed eMaint X5 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
Jira
ClickUpWorks well with
ServiceNowOften used alongside
Tools the same teams tend to run next to eMaint X5, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServiceeMaint X5 integration FAQ
How do I add an eMaint X5 integration to my product?
Enable the eMaint X5 connector in your fastn dashboard, then let each customer authenticate their own eMaint X5 account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no eMaint X5 client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own eMaint X5 account?
Yes. Every connection is scoped to the individual customer, so each authorises their own eMaint X5 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 eMaint X5 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 reads open work orders and maintenance history before answering a question about an asset.
Who maintains the eMaint X5 integration?
fastn does. When eMaint X5 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 eMaint X5 automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in eMaint X5 can trigger your workflows in return.
Does it adapt to each team's own eMaint X5 setup?
Yes. However a team has configured eMaint X5, 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 eMaint X5 integration?
A common starting point: raise work orders in their own eMaint X5 account directly from your product. 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 eMaint X5 integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding eMaint X5 does not change your per-connector cost. You can start free with 3 connected accounts.
Add eMaint X5 to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.