Resources · Make integration

Lumnio Make integrationAutomate Lumnio with Make.

What can the Lumnio Make integration take off your plate? It gives you 27 modules: 21 actions that create, read or update records, and 6 searches. This guide shows you how to connect your account and build a first working scenario without code.

Try the Lumnio integration on MakeSee the 27 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Lumnio Make integration let you automate?

The Lumnio Make integration links your Lumnio account to Make so that equipment, locations, issues, tasks and users can be created, looked up or updated by an automation instead of by hand. You build that automation, called a scenario, from bricks called modules, and none of it needs code.

Issues logged from outside Lumnio. A problem reported in a form or a chat tool can become a Lumnio record through Create issue, and later be corrected with Update issue by external ID when the source changes.

A clean asset register. When a new machine lands in your purchasing sheet, Search equipment checks that it is not already there, then Create equipment adds it. The same pair works for locations and equipment types.

People and work kept in step. A new hire in your HR tool can become a Lumnio account with Create user, and a planned job can turn into a checklist-style assignment through Create work instruction task.

Two limits to know up front. Lumnio has no trigger in Make, so a scenario starts from another app or from a schedule. And Make says its own documentation for Lumnio is limited, so field details come from what Make shows in the module once you are connected. If you are still choosing a tool, the n8n vs Make comparison sets out the criteria, Make pricing explains how operations are counted, and Make training walks through the editor from scratch.

Connect

How do you connect Lumnio to Make?

  1. 01

    Add a Lumnio module

    Inside a scenario, click the +, type Lumnio in the search box and pick any module. Its settings panel opens with a Create a connection button. A connection is your Lumnio account linked to Make once and reused by every Lumnio module.

  2. 02

    Name it and authorize

    Give the connection a name you will recognize later, such as the workspace it points to. Then either approve Make on the Lumnio page that opens, or paste the key Lumnio gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. The module now shows the connection in its dropdown, and Make can list the Lumnio objects it can read. If that list stays empty, the connection is not working yet and nothing else will run.

First scenario

Your first scenario: turn an outside report into a Lumnio issue

GoalWhen a problem is reported in another app, Make creates a matching issue in Lumnio.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app where reports land today, a form tool or a shared sheet, and its trigger module.

  2. 02

    Add Create issue

    Click the + on the right of that first module, search Lumnio and choose Create issue. Pick your connection, or click Create a connection if this is your first Lumnio module.

  3. 03

    Map the report

    Fill the fields Make shows by clicking into each one and picking data from the first module, such as the text of the report. Each report travels as a bundle, one item passed from module to module.

  4. 04

    Test with Run once

    Send one test report, then click Run once. Open the bubble above each module to read the bundles it received and check that the new issue appears in Lumnio.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Modules

What can each Lumnio module do?

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

Lumnio1

Create equipment

ActionIn the docs only

Adds a new piece of equipment to Lumnio, so a machine bought or installed somewhere else shows up in your asset list without retyping it.

When to use it
right after a purchase line or an installation record appears in another tool, as the step that registers the asset.
Watch out
run Search equipment first if the same item could arrive twice, or you will end up with duplicates.
Lumnio2

Create equipment type

ActionIn the docs only

Registers a new category of equipment, the family that individual machines belong to, so later records have somewhere to be filed.

When to use it
when a catalog maintained in a spreadsheet gains a model or family that Lumnio does not know yet.
Watch out
a duplicate type is easy to create under a slightly different name, so check with Search equipment types first.
Lumnio3

Create general task

ActionIn the docs only

Puts a plain task into Lumnio, the kind of job someone has to pick up, straight from an event in another app.

When to use it
a request comes in by email or form and simply needs an owner, without step-by-step instructions attached.
Watch out
if the job follows a procedure, Create work instruction task is the closer fit; a general task does not carry that structure.
Lumnio4

Create issue

ActionIn the docs only

Logs a problem in Lumnio from data that arrived elsewhere, so faults reported in a form, a chat or a sheet land in one place.

When to use it
as the action behind any reporting channel your team already uses, like the one in the first scenario above.
Watch out
each incoming bundle creates one issue, so a trigger that returns several rows produces several issues in one run.
Lumnio5

Create location

ActionIn the docs only

Adds a location to Lumnio, the place where your sites, buildings or areas are recorded.

When to use it
a new site is opened in your ERP or property list and should exist in Lumnio before anything is attached to it.
Watch out
if a later module in the same scenario refers to this location, keep Create location before it in the chain.
Lumnio6

Create user

ActionIn the docs only

Opens a Lumnio account for a person, which saves an admin from copying names out of the HR system one by one.

When to use it
onboarding, when a new hire is marked as starting in the tool that owns employee records.
Watch out
pair it with Search users so that a rehire or a resent form does not create a second account for the same person.
Lumnio7

Create work instruction task

ActionIn the docs only

Creates a task tied to a work instruction, as the module name says; Make's documentation does not describe what that instruction holds.

When to use it
an inspection or servicing job is scheduled in another planning tool and has a defined way of being done.
Watch out
Make documents few details for this module, so open it after connecting to see which instruction it expects before mapping anything.
Lumnio8

Get detail about me

ActionIn the docs only

Returns the Lumnio account that the connection is using, a quick way to confirm who Make is acting as.

When to use it
as the very first test after connecting, or to stamp the acting account onto a log row in another app.
Watch out
it tells you about the connected account only, never about other users; for them, use Get user by external ID or Search users.
Lumnio9

Get equipment by external ID

ActionIn the docs only

Fetches one piece of equipment when you already hold its external ID, the reference that ties the Lumnio record to another system.

When to use it
a meter reading or a ticket mentions an asset code, and you want the full Lumnio record before acting on it.
Watch out
no external ID on the record means nothing to find; fall back on Search equipment in that case.
Lumnio10

Get equipment type by external ID

ActionIn the docs only

Pulls a single equipment type from Lumnio by the external ID stored on it, handy when a catalog elsewhere uses its own codes.

When to use it
before updating a type, or when another module needs details about the family a machine belongs to.
Watch out
use the code stored on the record in Lumnio; a code that differs finds nothing, so check the result after Run once.
Lumnio11

Get issue by external ID

ActionIn the docs only

Retrieves one issue using the reference your other system gave it, so a scenario can read its current state.

When to use it
a customer or a colleague asks for news on a ticket from a helpdesk tool, and you want Lumnio's version before replying.
Watch out
only issues created with an external ID can be reached this way; older ones may need Search issues.
Lumnio12

Get location by external ID

ActionIn the docs only

Looks up one location from its external ID and hands its details to the next module in the scenario.

When to use it
a site code arrives from your property tool and you need to confirm Lumnio knows that place before attaching something to it.
Watch out
test an unknown code with Run once and read what the module returns before you build the next steps.
Lumnio13

Get task by external ID

ActionIn the docs only

Reads back a single task, general or work instruction, from the external ID you attached when it was created.

When to use it
your planning tool wants to know where a job stands, and the scenario checks Lumnio before updating the plan.
Watch out
to change the task afterwards, pick the update module that matches its kind; there is one for general tasks and one for work instruction tasks.
Lumnio14

Get user by external ID

ActionIn the docs only

Finds one Lumnio user through the employee reference kept in another system, often an HR identifier.

When to use it
assigning a task or an issue to a person when your source data only carries their staff code.
Watch out
users created by hand in Lumnio may have no external ID; Search users covers them.
Lumnio15

Make an API call

ActionIn the docs only

Lets you call any endpoint of the Lumnio API from your scenario, reusing the same connection, when none of the listed modules covers what you need.

When to use it
an object or an operation you need has no module of its own in the list above.
Watch out
Make's documentation for Lumnio is limited, so you will need the endpoint and its format from Lumnio itself.
Lumnio16

Search equipment

SearchIn the docs only

Browses your equipment and returns every match as its own bundle, zero, one or many.

When to use it
checking whether an asset exists before creating it, or listing machines to feed a report in a spreadsheet.
Watch out
each result runs the following modules once, which multiplies operations; keep your criteria tight when you only expect one.
Lumnio17

Search equipment types

SearchIn the docs only

Lists the equipment types that match your criteria, so a scenario can pick the right family without knowing its ID.

When to use it
just before Create equipment, to find the type a new machine should be filed under.
Watch out
an empty result is a valid answer, not an error; plan a route for it, such as creating the type first.
Lumnio18

Search issues

SearchIn the docs only

Pulls a set of issues out of Lumnio, one bundle per issue, ready to be copied, counted or sent elsewhere.

When to use it
building a digest of open problems in a sheet, or finding an older issue that was never given an external ID.
Watch out
on a scheduled scenario, the same issues come back at every run unless your criteria narrow them down.
Lumnio19

Search locations

SearchIn the docs only

Returns the sites and areas that match your search, handy when a record elsewhere names a place but carries no code.

When to use it
matching a free-text address from a form to an existing Lumnio location.
Watch out
a loose search can match several places; check the bundles after Run once before you wire an update behind it.
Lumnio20

Search tasks

SearchIn the docs only

Collects the tasks that fit your criteria, each one as its own bundle, so you can report on them or act on each.

When to use it
exporting assigned work to a planning sheet, or finding the job linked to an event that has just been cancelled.
Watch out
general and work instruction tasks each have their own update module, so check which kind you got back.
Lumnio21

Search users

SearchIn the docs only

Finds people in your Lumnio account and returns each match separately, useful when you know a name but not an ID.

When to use it
before Create user, to avoid a duplicate account, or to pick who receives a new task.
Watch out
two people can share a name; if several bundles come back, the next modules run for each of them.
Lumnio22

Update equipment by external ID

ActionIn the docs only

Changes an existing equipment record, found through its external ID, so the asset list follows what happens in your other tools.

When to use it
a machine is moved, renamed or retired in your inventory system and Lumnio should reflect it.
Watch out
test on a single record with Run once and check the result in Lumnio before switching the scenario on.
Lumnio23

Update equipment type by external ID

ActionIn the docs only

Edits one equipment type found by its external ID, so the family stays in line with the catalog it comes from.

When to use it
the product catalog renames a model line or corrects its description, and Lumnio should follow.
Watch out
a type can group many assets, so test the change on one type with Run once before switching the scenario on.
Lumnio24

Update general task by external ID

ActionIn the docs only

Brings a general task up to date from the reference your other system holds, so both sides show the same job.

When to use it
the request behind the task changes in your helpdesk or form tool and the owner in Lumnio needs the new version.
Watch out
it only reaches general tasks; a work instruction task needs its own update module.
Lumnio25

Update issue by external ID

ActionIn the docs only

Modifies an issue already in Lumnio, located by the external ID it was given, so its record keeps pace with the source.

When to use it
the person who reported a fault adds details or closes the request on their side.
Watch out
if the issue was never created with an external ID, this module cannot reach it; find it with Search issues instead.
Lumnio26

Update location by external ID

ActionIn the docs only

Corrects or refreshes a location using the code your other system uses, so both keep the same name and details.

When to use it
a site changes name or address in your property database.
Watch out
run a Get location by external ID first when you are not sure the code exists, so a typo does not stop the scenario.
Lumnio27

Update work instruction task by external ID

ActionIn the docs only

Updates a guided task tied to a work instruction, reached through its external ID, so a rescheduled or reassigned job stays accurate.

When to use it
a maintenance planner moves an inspection, and the change should reach the person who carries it out in Lumnio.
Watch out
Make gives few details for this module; open it after connecting to see which fields can change.
Need help

Need help automating Lumnio with Make?

A person reads every message.

FAQ

Lumnio and Make: common questions

01Is the Lumnio Make integration free?
Yes, Lumnio is a standard app in Make, so it works on the Free plan. That plan keeps two scenarios active at once, runs scheduled scenarios at most every 15 minutes, stops a run after 5 minutes, and caps files at 5 MB with 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, allow unlimited active scenarios and runs of up to 40 minutes. Usage is counted in operations, one per module run on one bundle.
02What do you need to connect Lumnio to Make?
A Lumnio account and a Make account. Make's documentation lists no special prerequisite for Lumnio and gives no dedicated connection steps, so the standard route applies: add any Lumnio module, click Create a connection, name it if you like, then either authorize Make on the Lumnio page or paste the key Lumnio gives you, and click Save. The connection is then reused by every Lumnio module in your scenarios, so this setup only happens once per account.
03Can a Lumnio scenario start on its own without a trigger?
Yes, but the start has to come from somewhere else, because Lumnio has no trigger module in Make. The first option is a trigger from another app, such as a new form entry, which then feeds the Lumnio actions. The second is a schedule: a scenario can open on a Lumnio search, like Search issues, and Make runs it on the clock of the first module, every 15 minutes by default on a new scenario. The scenario above uses the first option.
04What if the Lumnio module you need is missing in Make?
Use Make an API call. It reaches any endpoint of the Lumnio API from the scenario with the same connection, which covers what the listed modules leave out. The catch is documentation: Make says its guide for Lumnio is limited because little public information exists about the app, so the endpoint names and formats have to come from Lumnio directly. Test such a call with Run once before switching the scenario on.
05Should you use Make or n8n with Lumnio?
It depends on what your team already runs. On the Make side, Lumnio offers 27 modules, a connection set up once, and a scenario you can test with Run once before switching it on. Many apps also have an n8n node, so if Lumnio is one of them, the useful question is which tool already hosts your other automations and which editor your team reads comfortably. Keeping related flows in one place makes them easier to maintain. The n8n vs Make comparison linked above goes through the criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations