Resources · Make integration

LimbleCMMS Make integrationAutomate LimbleCMMS with Make.

Can Make keep your LimbleCMMS work orders and spare parts in sync with the rest of your tools? The LimbleCMMS Make integration gives you 20 modules: one instant trigger, 12 actions and 7 searches. This guide shows maintenance and operations leads how to connect the account and build a first working scenario.

Try the LimbleCMMS integration on MakeSee the 20 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the LimbleCMMS Make integration do for your maintenance team?

The LimbleCMMS Make integration links your maintenance account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, creates, updates or searches something. With it, tasks, parts, instructions and asset fields move between LimbleCMMS and your other apps without anyone copying them by hand.

Turn outside requests into work orders. A request logged in a form tool or a helpdesk can feed Create a Task, then Add an Instruction gives the technician the checklist straight away. Nobody retypes the request, and the work order starts complete.

React the moment a task moves. Watch Task Changes is an instant trigger: LimbleCMMS calls Make as soon as the task events you pick happen. Pair it with List Parts Usage to see which parts a finished job consumed, and pass that to your purchasing sheet or your team chat.

Keep the parts catalog clean. List Parts, Update a Part and Update a Field let a stock file or an ERP export correct part details and asset fields in one pass, instead of editing records one by one.

What the listed modules do not cover, Make an API Call can reach through the same connection. The official Make documentation for this app is marked as AI-generated from the LimbleCMMS docs, so double-check anything critical with the vendor. If you are weighing tools, read n8n vs Make; to price the operations your scenarios will use, see Make pricing; and if a run fails, Make troubleshooting walks through the usual fixes.

Connect

How do you connect LimbleCMMS to Make?

  1. 01

    Copy your API credentials in LimbleCMMS

    In LimbleCMMS, open Advanced Settings, then Configuration and API Settings. Copy the Client ID and the Client secret shown on screen. You need an active Limble account and an API key to see these values.

  2. 02

    Add a LimbleCMMS module in Make

    In your scenario, add any LimbleCMMS module and click Create a connection. The Connection name field is optional; a clear label such as the site name helps when several teams share Make.

  3. 03

    Paste the credentials and save

    Enter the Client ID and Client secret you copied, or follow the on-screen instructions, then save. That connection, meaning your LimbleCMMS account linked to Make once, is reused by every LimbleCMMS module afterward.

First scenario

Build your first scenario: requests that become LimbleCMMS work orders

GoalWhen a maintenance request lands in another app, Make creates the LimbleCMMS task and attaches its instruction.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app where requests arrive (a form, a helpdesk, a sheet) as the first module, since LimbleCMMS has no trigger for incoming requests.

  2. 02

    Add Create a Task

    Click the + to the right of the first module, search LimbleCMMS and choose Create a Task. Connect the account, then map the request title and description from the previous module into the task.

  3. 03

    Attach the checklist with Add an Instruction

    Add Add an Instruction after it and map the task created one step earlier. Each bundle, one request flowing through, now produces a work order with its first instruction in place.

  4. 04

    Test with Run once

    Submit a sample request, then click Run once. Open the bubbles above each module to read what it received, and check in LimbleCMMS that the task and its instruction look right.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default, 1 minute at best on paid plans) and turn the scenario on. Each module run counts as one operation on your plan.

Triggers

What starts a LimbleCMMS scenario?

1 module starts a scenario when something happens in LimbleCMMS. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by LimbleCMMS as soon as it happens.

LimbleCMMS1Watch Task Changes

Watch Task Changes

Instant trigger

In Make“Triggers for the specified task-related events.”

Get a scenario that wakes up by itself whenever a work order changes in LimbleCMMS, so the rest of your stack hears about it without anyone checking the app. You choose which task-related events count, and each one arrives in Make as a bundle.

How it fires
instant, LimbleCMMS calls Make through a webhook as soon as the event happens; there is no polling interval to wait for.
When to use it
alerting a supervisor, logging completed jobs in a spreadsheet or pulling the parts a job consumed.
Watch out
avoid updating the same task later in that scenario, or the change can fire the trigger again.
Modules

Every LimbleCMMS module, and when to pick it

LimbleCMMS gives you 19 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

LimbleCMMS1

Add an Instruction

Action

In Make“Adds an instruction to a task.”

Hand the technician a ready-made step on an existing work order, so the task arrives with its checklist instead of a bare title. It adds one instruction per run to the task you point it at.

When to use it
right after Create a Task, to append the safety or inspection step your team always repeats.
Watch out
it needs the task identifier, so map it from the module that created or found the task.
LimbleCMMS2

Attach a Field

Action

In Make“Attaches a suggested field to an asset or part.”

Give an asset or a part a field it did not show yet, picked from the fields LimbleCMMS suggests, so the record carries the information your team tracks.

When to use it
when a new asset enters the system and should display the same fields as its siblings.
Watch out
attaching adds the field; filling its value is the job of Update a Field in a later module.
LimbleCMMS3

Create a Part

Action

In Make“Creates a new part.”

Add a new spare part to your LimbleCMMS inventory straight from another tool, so the catalog stays aligned with what purchasing actually orders.

When to use it
a supplier sheet or purchase order introduces a reference that does not exist yet in LimbleCMMS.
Watch out
run List Parts before it when the source can resend the same item, or you end up with duplicate parts.
LimbleCMMS4

Create a Task

Action

In Make“Creates a new task (work order).”

Open a work order in LimbleCMMS from any event Make can see, which removes the retyping between the place a problem is reported and the place it gets fixed.

When to use it
a request form, an email or a sensor alert handled by another app should become a task for the maintenance team.
Watch out
every run creates one task, so filter out test entries and repeats before this module.
LimbleCMMS5

Delete a Part

Action

In Make“Deletes a part.”

Remove a part record from LimbleCMMS when it no longer belongs in the catalog, keeping searches and stock views free of dead references.

When to use it
a supplier discontinues an item and your master list flags it as retired.
Watch out
a deletion cannot be undone from Make, so place a filter before it and test with Run once on a dummy part first.
LimbleCMMS6

Delete a Task

Action

In Make“Deletes a task (work order).”

Wipe a work order from LimbleCMMS entirely, which keeps boards clean when a request turns out to be a duplicate or was opened by mistake.

When to use it
the request that created the task is cancelled in the source app before anyone starts the job.
Watch out
treat a deletion as final; updating the task is often the safer choice.
LimbleCMMS7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reach any endpoint of the LimbleCMMS API from your scenario with the connection you already set up, which covers whatever the listed modules leave out.

When to use it
you need a LimbleCMMS object or operation that no listed module names.
Watch out
you write the request yourself, so keep the LimbleCMMS API documentation open and test the call with Run once before relying on it.
LimbleCMMS8

Remove an Instruction

Action

In Make“Removes an instruction from a task.”

Take a step off a work order when it no longer applies, so technicians do not waste time on an instruction that was added by a rule that changed.

When to use it
a task was downgraded and the extra inspection step should vanish from its checklist.
Watch out
pair it with List Instructions to target the right instruction, since a task often carries several.
LimbleCMMS9

Update a Field

Action

In Make“Updates the value of an asset (or part) field.”

Write a new value into a field of an asset or a part, so readings, locations or supplier details stay current without opening each record.

When to use it
a meter reading or an inventory count arrives from another system and should land on the matching asset.
Watch out
the field must already be on the record; attach it first with Attach a Field if it is missing.
LimbleCMMS10

Update an Instruction

Action

In Make“Updates an instruction on a task.”

Rewrite an instruction already sitting on a task, which fixes a wording or a value without deleting and recreating the step.

When to use it
a procedure document changes and open work orders should show the corrected step.
Watch out
it needs both the task and the instruction, so fetch them first with List Tasks and List Instructions.
LimbleCMMS11

Update a Part

Action

In Make“Updates information about a part (e.g. quantity).”

Change the details of an existing part, quantity included, so the stock level in LimbleCMMS follows what actually sits on the shelf.

When to use it
a delivery is received in your purchasing tool and the part count should rise accordingly.
Watch out
check with Run once whether the module expects the new total, and if so compute it in Make before this module.
LimbleCMMS12

Update a Task

Action

In Make“Updates a task (work order).”

Edit a work order that already exists, which lets another app push status or detail changes into LimbleCMMS without manual follow-up.

When to use it
a contractor confirms a visit in their own tool and the task should reflect it.
Watch out
inside a scenario started by Watch Task Changes, updating that same task can fire the trigger again; add a filter to stop the loop.
LimbleCMMS13

List Fields

Search

In Make“Retrieves the fields of an asset or part.”

See which fields an asset or a part carries, so the next module knows what it can fill or compare.

When to use it
before Update a Field, to confirm the field exists on that record, or to export asset details to a spreadsheet.
Watch out
as a search, it returns zero, one or several bundles; each bundle runs the following modules once.
LimbleCMMS14

List Instructions

Search

In Make“Retrieves the list of instructions on a task.”

Read the checklist of a work order, instruction by instruction, so you can review, copy or correct it elsewhere.

When to use it
a completed task should leave a trace of each step in a report or an audit document.
Watch out
an empty checklist returns no bundle, and the rest of the scenario then stops for that run.
LimbleCMMS15

List Parts

Search

In Make“Retrieves a filtered list of parts.”

Pull the parts that match your filters, which gives a live view of the catalog to compare with a supplier list or a stock file.

When to use it
checking whether a reference already exists before Create a Part, or feeding a reorder sheet.
Watch out
each matching part is its own bundle and counts operations downstream, so filter tightly.
LimbleCMMS16

List Parts Usage

Search

In Make“Retrieves part usage history for the specified parts or tasks.”

Retrieve the usage history of parts, by part or by task, so you know what each job actually consumed.

When to use it
after Watch Task Changes reports a task change, to send the consumed parts to purchasing or cost tracking.
Watch out
choose between filtering by parts and filtering by tasks according to the question you are asking, or the result mixes unrelated jobs.
LimbleCMMS17

List Tasks

Search

In Make“Retrieves a filtered list of tasks (work orders).”

Fetch the work orders that match a filter, which is the starting point for reports, reminders or bulk corrections.

When to use it
building a digest of open tasks for a manager, or finding the task to update when another app only knows its details.
Watch out
a broad filter returns many bundles, and every later module runs once per task.
LimbleCMMS18

List Teams

Search

In Make“Retrieves a filtered list of teams.”

Get the teams defined in LimbleCMMS, filtered as needed, so assignments in other tools use the same groups.

When to use it
routing a new request to the right crew, or mirroring team names into a planning sheet.
Watch out
team names can change in LimbleCMMS, so map identifiers rather than labels when you pass a team to another module.
LimbleCMMS19

List Users

Search

In Make“Retrieves a filtered list of users.”

Look up the users of your LimbleCMMS account, so notifications and assignments reach real people rather than a guessed name.

When to use it
matching the requester's email from a form with a LimbleCMMS user before creating the task.
Watch out
when no user matches, the search returns nothing, so plan a fallback route for unknown requesters.
Need help

Need help automating LimbleCMMS with Make?

A person reads every message.

FAQ

LimbleCMMS and Make: common questions

01Is the LimbleCMMS Make integration free?
Yes, on the Make side. LimbleCMMS is a standard app, available from the Free plan. That plan allows 2 active scenarios, a 15 minute minimum between scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute and remove the active scenario cap. Every module run is one operation, counted on your monthly credits. You still need your own active Limble account, which LimbleCMMS bills separately.
02What do you need to connect LimbleCMMS to Make?
An active Limble account with an API key, and a Make account. In LimbleCMMS, go to Advanced Settings, Configuration, then API Settings, and copy the Client ID and Client secret. In Make, add a LimbleCMMS module, click Create a connection, optionally name it, and paste both values. For the instant trigger Watch Task Changes, click Create a webhook first, then create the connection in the same window. One connection serves all 20 LimbleCMMS modules.
03Does the LimbleCMMS trigger in Make react in real time?
Yes. Watch Task Changes is an instant trigger: LimbleCMMS calls Make through a webhook as soon as a selected task event happens, so there is no schedule to wait for. It is the only trigger of the app. Parts, fields, teams and users have no trigger; to react to them, start the scenario on a schedule (every 15 minutes by default) and use a search such as List Parts to read the current state.
04What if a LimbleCMMS module you need is missing in Make?
Use Make an API Call. It sends any request to the LimbleCMMS API with the connection you already created, so it can reach objects and operations that the 12 actions and 7 searches do not cover. You write the request yourself, following the LimbleCMMS API documentation. Also note that the Make documentation page for this app is labeled as AI-generated from the vendor docs, so confirm important details with LimbleCMMS before building on them.
05Should you automate LimbleCMMS with Make or n8n?
It depends on the tool your team already runs. On Make, LimbleCMMS brings 20 ready modules, including an instant trigger on task changes and a universal API call module, all usable from the Free plan. n8n often offers a node for the same app, so check its catalog for LimbleCMMS before deciding. Compare which operations each tool exposes for your use case rather than picking on reputation, and keep your scenarios where the rest of your automations already live.
Same platform

Other docs you might need on this stack.

Browse all integrations