Integration
Connect Exist to MaintainX
When New Attribute Value fires in Exist, your agent runs Add Existing Categories to a Work Order in MaintainX. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Exist and MaintainX to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Exist can start in MaintainX
When New Attribute Value in Exist
then Add Existing Categories to a Work Order in MaintainX
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Exist and MaintainX
Triggers and actions 1 trigger · 45 actions
- New Attribute Value
Triggers when a new daily value is recorded for the chosen Exist attribute, such as steps or mood.
- Acquire Attributes
Takes ownership of one or more Exist attributes for this app so it can write their values, creating templated attributes the user doesn't have yet.
- Create Attributes
Creates one or more new attributes in the user's Exist account, from a template or as custom attributes, and returns which succeeded and which failed.
- Get Attribute Values
Returns the daily values recorded for one of the user's Exist attributes, newest first.
- Get Averages
Returns the most recent weekly average values for your Exist attributes, optionally filtered by group, attribute and date range, including historical averages.
- Get User Profile
Returns the authenticated Exist user's profile: name, avatar, timezone, local time and unit preferences.
- Increment Attribute Values
Adds amounts to the existing daily values of attributes your app owns in Exist, returning each attribute's new total.
- List Attributes
Returns the Exist user's attributes (without values), optionally filtered by group, name, or type.
- List Attributes with Values
Returns the user's Exist attributes together with their recent daily values.
- List Owned Attributes
Returns the user's attributes that your Exist client currently owns, without values. Can be filtered by group, attribute name, manual flag and more.
- Release Attributes
Releases your ownership of one or more Exist attributes so another service can provide their data, or they become inactive.
- Update Attribute Values
Saves daily total values for attributes you own in Exist, up to 35 at a time, replacing any value already stored for those days.
- Add Existing Categories to a Work Order
Adds Existing Categories to a Work Order.
- Add Part
Creates a new part (inventory item) in MaintainX.
- Add Purchase order
Creates a purchase order in MaintainX for a vendor, with its line items, costs and addresses.
- Add Vendor
Create a new vendor.
- Create Asset
Creates an Asset in MaintainX
- Create Location
Creates a location in MaintainX
- Create Work Order
Creates a new Work Order.
- Create Work Order Comment
Creates a New Comment on a Work Order.
- Create Work Request
Creates a new Work Request.
- Delete Asset
Deletes an asset in MaintainX by its ID.
- Delete Location
Delete a location by ID.
- Delete Part
Deletes a part from MaintainX by its ID.
- Delete Work Order
Delete a work order by ID.
- Delete Work Request
Deletes a work request in MaintainX by its ID.
- Find an Entity
Finds a MaintainX asset, location, part or work order by the external ID your other system assigned to it.
- Get Asset
Retrieve a single asset by ID.
- Get Location
Retrieves a single MaintainX location by its ID, including its custom fields.
- Get Part
Retrieves a single MaintainX part (inventory item) by its ID, including stock quantities, locations, vendors and custom fields.
- Get Purchase order
Retrieves a single MaintainX purchase order by its ID, including items, costs, addresses, attachments and custom fields.
- Get Vendor
Retrieve a single vendor by ID.
- Get Work Order
Retrieve a single work order by ID.
- Get Work Request
Retrieves a MaintainX work request by its ID, including its custom fields and its linked asset, location and work order.
- List Assets
Returns all assets in the MaintainX organization, optionally filtered by location, manufacturer, model or created/updated date range.
- List Locations
Returns all locations in the MaintainX organization, optionally narrowed to names starting with a given prefix.
- List Vendors
Lists the vendors in your MaintainX organization, including their custom field values.
- List Work Orders
Lists work orders in MaintainX, optionally filtered by title, status, priority, asset, location, part, vendor, assignee, team, category and created/updated dates.
- List Work Requests
List work requests with pagination/filters.
- Update Location
Updates a Location in MaintainX
- Update Part
Update fields on an existing part.
- Update Purchase order
Update fields on an existing purchase order.
- Update Vendor
Update fields on an existing vendor.
- Update Work Order
Updates an existing Work Order
- Update Work Order Status
Changes the status of a MaintainX work order.
- Update Work Request
Update fields on an existing work request.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Exist
Exist to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Exist to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Exist to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Exist to Google SheetsGoogle Sheets
Exist to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Exist to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into MaintainX
Questions
Exist and MaintainX, answered
What can start an automation from Exist?
Any of Exist's 1 trigger in the catalog, including New Attribute Value. Describe the moment in plain language and your agent picks the right one.
What can your agent do in MaintainX when something happens in Exist?
Any of MaintainX's 34 actions, including Create Asset, Create Location, Create Work Order and Create Work Order Comment. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from MaintainX to Exist?
MaintainX has no triggers in the catalog today, so automations start in Exist. If you need the other direction, ask: your agent reads MaintainX's API documentation and adds it.
Do I have to build a connector for Exist or MaintainX?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.