Resources · Zapier integration

MaintainX Zapier integrationAutomate MaintainX with Zapier.

The MaintainX Zapier integration gives you 6 triggers, 9 actions and 2 searches to open work orders from other tools, react the moment a status changes, and keep assets and locations in step. Here is what each one does, what it costs and where it trips.

See the 17 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MaintainX Zapier integration actually does for you

MaintainX tracks reactive and preventive maintenance and the day-to-day running of a business. Connecting it to Zapier links that work to the rest of your tools: a work order or a status change in MaintainX can start work elsewhere, and an event in another app can create a work order, a request, an asset or a message in MaintainX without anyone retyping it.

Status updates the team sees where it already talks. Work Order Status Change fires as soon as a work order moves, and a Zap can post it in your team chat. Nobody has to open MaintainX to know a job is done.

Requests that turn into work orders. New Work Request catches each incoming request, and Create Work Order opens the matching job with its title already filled in.

An asset register kept in two places. New Asset reports every asset added in MaintainX, ready to be copied into the spreadsheet where you keep your equipment register.

Good news for the free plan: all six triggers are instant. MaintainX tells Zapier the moment something happens, so your plan's polling interval never slows them down.

What Zapier does not do here: there is no action to delete anything, and you cannot react to a new location or a new message, since no trigger covers them. If you are weighing platforms first, the n8n vs Zapier comparison sets out the criteria that matter.

Vocabulary

The Zapier words you will meet on this page

Seven terms come back on every Zapier page. Here they are in ordinary words.

Zap
The automation you build: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts your Zap. Once the Zap is on, Zapier waits for that event and nothing else.
Action
What the Zap does after it starts: the step that writes, sends or moves something in an app on your behalf.
Task
The unit Zapier bills. One action your Zap finishes successfully is one task; your plan counts those.
Instant vs polling
Instant: the app reports the event itself. Polling: Zapier checks on a timer. All MaintainX triggers are instant.
Filter
A step that lets the Zap carry on only when what arrived matches the condition you set, and stops it otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can use what it found.
Connection
Your MaintainX account linked to Zapier once, then reused by every step of every Zap that talks to MaintainX.
Cost

What MaintainX really costs in Zapier

MaintainX is not a premium app, so it works from the free plan. The bill is counted in tasks, and only finished actions count.

  • Free plan100 tasks a month, unlimited Zaps, two-step Zaps only
  • Premium appNo, MaintainX runs on the free plan
  • BilledEach successful action; triggers are free

The trigger never costs a task, so a status change arriving from MaintainX is free. Each action that succeeds counts once: a Zap that creates a work order and then comments on it uses two tasks per run. A failed action is not billed. The free plan stops at two steps, one trigger and one action; a filter, a search or a second action makes the Zap multi-step and needs a paid plan. The grid below is Zapier's polling interval by plan; it does not apply to MaintainX, whose six triggers are all instant.

Connect

Connect your MaintainX account to Zapier

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need a MaintainX account, plus access to any work order, asset or location you do not own but want the Zap to touch.

  2. 02

    Pick MaintainX

    Type MaintainX in the search box of the dialog, select it, then click Add connection. A new browser tab opens on the MaintainX side, where the rest happens.

  3. 03

    Sign in and grant access

    Log in to MaintainX in that tab and allow Zapier to reach the account. The connection is saved once, and every later Zap that uses MaintainX picks it from a menu.

First Zap

Your first MaintainX Zap, step by step

GoalWhen a work order changes status in MaintainX, post a message in your team chat, but only for the status you choose.

  1. 01

    Create the Zap

    Start a new Zap and pick MaintainX as the app that starts it, with Work Order Status Change as the event. Choose the connection you saved earlier.

  2. 02

    Test the trigger

    Run the trigger test. Zapier brings back the three most recent status changes from your account, so you map the next steps on a real work order.

  3. 03

    Add a filter

    Add a Filter from the plus icon and fill its three boxes: the field to look at, the rule, the value. Only matching changes go on. This makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add the chat message

    Add your team chat app as the action, pick the event that sends a message, and drop the work order title and new status into the text.

  5. 05

    Test, then publish

    Test the action once and check the message arrived. Then click Publish; the trigger is instant, so each status change goes through straight away from now on.

Triggers

MaintainX triggers: what can start a Zap

6 events start a Zap when something happens in MaintainX, and 6 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Asset

Instant trigger

In Zapier“Triggers when a new Asset is created in MaintainX”

Each asset created in MaintainX starts this Zap, with the asset's details attached. It is the event to watch when another tool keeps its own list of equipment.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you keep an equipment register in a spreadsheet and need every new asset listed there.
Watch out
the trigger has an option to return all asset information; switch it on if the next step needs more than the basics.
2

New Category on Work Order

Instant trigger

In Zapier“Triggers when a new category is added to a work order.”

Adding a category to a work order is what sets this one off. Categories are often how a team sorts jobs, so this trigger lets one kind of work start its own follow-up.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a work order tagged with a given category should alert a specific person or team.
Watch out
costs and time entries are only included if you tick the matching options; leave them off if the next app does not need them.
3

Work Order Change

Instant trigger

In Zapier“Triggered when there is a change on a Work Order.”

Any change on a work order starts this Zap, which makes it the widest of the MaintainX triggers. Zapier receives the work order as it stands after the change.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
another tool keeps a copy of your work orders and must stay in step with every edit.
Watch out
paired with Update Work Order on the same work order, it can restart itself in a loop; the option to return only filtered properties also narrows what you receive.
4

New Work Order

Instant trigger

In Zapier“Triggers when a new work order is created.”

This trigger starts each time a work order is created in MaintainX. You get the new job as it was opened, ready to pass on to whoever needs to know.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
every new job should appear in a shared calendar, a spreadsheet or a project tool used outside the maintenance team.
Watch out
a Zap that writes into the place its own trigger watches can set itself off again; check that before pairing this trigger with an action on work orders.
5

Work Order Status Change

Instant trigger

In Zapier“Triggers when a work order status is changed.”

Only status moves start this Zap: a work order going from one status to another. It is narrower than Work Order Change, and the one to pick when only progress matters.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
the requester or a manager should be told when a job reaches a status that matters to them.
Watch out
every status change fires it, so add a filter if only one status counts; costs and time entries come only if you tick those options.
6

New Work Request

Instant trigger

In Zapier“Triggers when a New Work Request is created”

A new work request in MaintainX starts this Zap. Requests have their own trigger, separate from New Work Order.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
each request should land in front of the person who triages them, or be turned straight into a work order.
Watch out
requests filed before the Zap is published are never sent; only new ones reach Zapier.
Actions

MaintainX actions: what a Zap can do there

MaintainX gives you 9 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Existing Categories to a Work Order

Action

In Zapier“Adds Existing Categories to a Work Order.”

Tags a work order with categories that are already set up in MaintainX. It does not create new categories.

When to use it
jobs coming from a given form or source should be sorted under the right category on arrival.
Watch out
a filter or a search placed before it makes the Zap multi-step, so it needs a paid plan.
2

Create Asset

Action

In Zapier“Creates an Asset in MaintainX”

Adds an asset to MaintainX under the name you give it, the only mandatory field.

When to use it
new equipment is recorded in a spreadsheet or a purchasing tool first, and MaintainX should follow.
Watch out
a Zap that writes where its own trigger looks can restart itself, so keep the source spreadsheet and the trigger apart.
3

Create Location

Action

In Zapier“Creates a location in MaintainX”

Creates a location in MaintainX from a name, which is required. Nobody has to retype the site name in MaintainX, and both systems use the same spelling.

When to use it
a new site or room is added in another system and maintenance needs it too.
4

Update Location

Action

In Zapier“Updates a Location in MaintainX”

Edits a location that already exists in MaintainX, so names and details stay aligned with the system they come from.

When to use it
a site is renamed in your main records and MaintainX should show the same name to technicians.
5

Create New Message

Action

In Zapier“Creates a new Message in a Conversation”

Sends a message into a MaintainX conversation. Both the conversation ID and the message content are mandatory.

When to use it
an alert from another system should reach the people who already talk in that MaintainX conversation.
Watch out
the conversation must exist first; the Zap does not create one.
6

Create Work Order Comment

Action

In Zapier“Creates a New Comment on a Work Order.”

Posts a comment on a work order identified by its work order ID, which is required. The history stays inside the job, where technicians look.

When to use it
a customer reply or a supplier update elsewhere should be visible on the job.
7

Create Work Order

Action

In Zapier“Creates a new Work Order.”

Opens a new work order in MaintainX. Only the title is mandatory, so a short line from a form or an email is enough to get a job on the board.

When to use it
a problem reported in another tool should become a job without anyone copying it over.
8

Update Work Order

Action

In Zapier“Updates an existing Work Order”

Changes an existing work order, picked by its work order ID, which is mandatory.

When to use it
a reply or approval in another tool should move the job forward in MaintainX.
Watch out
combined with Work Order Change on the same job, the update can restart the Zap; Find an Entity can bring the ID when no earlier step carries it.
9

Create Work Request

Action

In Zapier“Creates a new Work Request.”

Files a work request in MaintainX rather than a work order, which keeps the two kinds of entry apart in the app. The title is the one required field, so a short line from a form is enough.

When to use it
requests come from outside the maintenance team and should arrive as requests, not as ready-made work orders.
Searches

MaintainX searches

2 search steps look for data that already exists in MaintainX, so a later step can use it.

A search step looks something up before the next steps run. MaintainX has two, and three settings decide what happens when the lookup goes differently than planned.

1

List Assets

Search

In Zapier“Lists assets in MaintainX”

Brings back assets from MaintainX so the next steps can use them, for instance to copy an asset's details into a message or a spreadsheet row.

When to use it
a Zap needs an asset that no earlier step carried.
Watch out
several assets can come back; set the multiple-results option deliberately.
2

Find an Entity

Search

In Zapier“Find an Entity by a specified field.”

Looks up one MaintainX item by a field you pick, after you choose its entity type, the only mandatory field.

When to use it
you need a work order ID for Update Work Order or a comment, and the trigger did not provide it.
Watch out
adding a search makes the Zap multi-step, so it needs a paid plan.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the dependent steps are skipped. Switch it on and the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. MaintainX does not offer that variant, so you will not see it on these two searches.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or pass all of them on at once.
When it breaks

When a MaintainX Zap breaks

Zapier lists no help article and no app-specific limit for MaintainX. What goes wrong comes from how Zapier itself works.

Four situations account for most surprises. None throws a dramatic error; they show up as missing jobs or a task count that climbs too fast. If one has you stuck, the Zapier troubleshooting page is the place to start.

  • Old work orders are never sent

    A Zap only reacts to what happens after you publish it. Work orders, requests and assets from before that moment stay in MaintainX; moving the backlog is a separate job.

  • The Zap keeps restarting itself

    Work Order Change followed by Update Work Order on the same job is the classic loop: each update can count as a change, so the Zap may fire again and burn through tasks.

  • A big batch is held back

    After a bulk import of assets or work orders, a trigger can return a huge batch at once. Zapier's flood protection may hold it back instead of running every item.

  • A search stops the Zap

    When Find an Entity or List Assets finds nothing, the default setting stops the Zap and skips the steps that needed the result. Decide that setting on purpose.
Need help

Need help automating MaintainX with Zapier?

A person reads every message.

FAQ

MaintainX and Zapier: questions people ask

01Is the MaintainX Zapier integration free?
Yes, as far as Zapier goes: MaintainX is not a premium app, so it works on the free plan. That plan gives you 100 tasks a month and unlimited Zaps, each limited to two steps, one trigger and one action. New Work Request followed by Create Work Order fits inside it. A filter, a search or a second action needs a paid plan. Your MaintainX subscription is a separate matter that this page does not cover.
02How many tasks does a MaintainX Zap use?
One task per action that succeeds, and nothing for the trigger. A Zap that posts a chat message on each status change uses one task per change. Add a comment on the work order and each change costs two. Watch Work Order Change in particular: every edit to a job fires it, so a busy board can run it very often. A search step makes the Zap multi-step, so it needs a paid plan. Failed actions are not billed.
03Does MaintainX trigger Zaps in real time?
Yes. All six MaintainX triggers are instant: the app tells Zapier as soon as a work order, a request or an asset is created or changes, and the Zap starts straight away. The polling intervals of the plans, such as 15 minutes on the free one, do not apply here. In the editor, a Zap built on an instant trigger shows a lightning bolt. Speed is the same on every plan; only the number of steps and tasks differs.
04What do you need to connect MaintainX to Zapier?
A MaintainX account, and access to any work order, asset or location you do not own but want the Zap to touch. In Zapier you open Apps, click + Add connection, pick MaintainX, sign in in the tab that opens and grant access. The connection is saved once and reused by every Zap. For several actions you also need an ID from an earlier step: a work order ID to update or comment, a conversation ID to post a message.
05Why does a MaintainX Zap keep firing on its own?
Because it writes into what its own trigger watches. The usual case is Work Order Change as the trigger and Update Work Order as the action on the same job: the update can count as a change, so the trigger may fire again, and again, using a task each time. Send the write somewhere else, use the narrower Work Order Status Change trigger, or add a filter that lets through only the changes you actually care about.
06What if the MaintainX operation you need is not in Zapier?
Then Zapier cannot do it for this app. There is no action to delete a work order, an asset or a location, and no trigger for new locations or new messages. Check the 17 operations on this page first: a search followed by an update often covers what you are after. If it is truly missing, the job stays inside MaintainX, or you look at another automation platform for that part of the workflow.
07Zapier, Make or n8n for MaintainX?
Decide on criteria rather than a ranking. On Zapier, MaintainX brings 17 ready-made operations, six instant triggers among them, and works from the free plan, which suits simple two-step Zaps. Count how many actions each event will run, since Zapier bills each one, and how many searches your scenario needs before it writes. Then check whether the other platform offers a ready-made MaintainX connector at all before comparing price models.
Same platform

Other docs you might need on this stack.

Browse all integrations