MaintainX
Work orders, assets, locations, parts, users, vendors and meters in MaintainX.
About
MaintainX ships in the w6w first-party pack. It declares 20 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.maintainx- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Productivity · IoT & Hardware · Project Management
Overview
MaintainX is a maintenance and operations platform: technicians and managers run work orders, track the assets and locations those orders are about, stock the spare parts they consume, and log meter readings that trigger preventive maintenance.
This app lets a workflow work with that data. Create a work order when a monitoring alert fires, move it through its statuses, comment on it, and list the open ones; look up assets, locations, parts, users, teams and vendors to enrich or route a request; register new assets and locations as equipment is commissioned; and push meter readings in batches from a sensor feed.
An API key from a MaintainX Premium or Enterprise plan is the only credential needed. Accounts that span several organizations can pick the organization per action. Health checks follow MaintainX’s own status page for the REST API.
Build with MaintainX
Three routes to the same 20 actions. The Workflow tab is generated from MaintainX'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.
List Users
user-list List users, optionally only those a work order can be assigned to, or by email.
List Work Orders
workorder-list List work orders, filtered by status, priority, asset, location, assignee or date.
Set Work Order Status
workorder-status-set Move a work order to OPEN, IN_PROGRESS, ON_HOLD, DONE or CANCELED.
Update Work Order
workorder-update Change fields on an existing work order; only the fields you set are sent.
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 MaintainX's real ids.
{
"manifestVersion": "2",
"name": "maintainx-example",
"steps": [
{
"id": "asset-create",
"uses": {
"app": "io.w6w.maintainx",
"action": "asset-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"name": "<name>"
}
}
]
}Here are some of the things you can do
-
Create Asset
performasset-create -
Get Asset
readasset-get -
List Assets
searchasset-list -
Create Location
performlocation-create -
Get Location
readlocation-get
+15 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 MaintainX, 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 MaintainX. 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: "asset-create",
payload: {
name: "<value>",
// description: "<value>",
// serialNumber: "<value>",
// barcode: "<value>",
// locationId: "<value>",
// parentId: "<value>",
// criticalityId: "<value>",
// teamIds: "<value>",
// vendorIds: "<value>",
// assetTypes: "<value>",
// manufacturerName: "<value>",
// modelName: "<value>",
// externalId: "<value>",
// extraFields: "<value>",
// organizationId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action asset-create --payload '{"name":"<value>"}'Give an AI agent MaintainX — without giving it MaintainX'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.maintainx#asset-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 MaintainX 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
MaintainX'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. MaintainX itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
MaintainX declares its own checks, so its health is a property of the app rather than something the host guesses at.
MaintainX API status
Better Stack status page for status.getmaintainx.com. The verdict is the `REST API` component; the app, GraphQL API and website components are reported as detail. Unsigned.