Resources · Make integration

Lightr. Make integrationAutomate Lightr. with Make.

Can Make handle your Lightr. orders so nobody retypes them? Yes: the Lightr. Make integration offers 23 modules, 16 actions and 7 searches, with no trigger. This guide links your account and walks you through a first scenario that creates and finalizes an order.

Try the Lightr. integration on MakeSee the 23 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Lightr. Make integration let you automate?

The Lightr. Make integration links your Lightr. account to Make, a no-code tool where you chain modules into a scenario. A scenario is the automation you build; a module is one brick of it, an action or a search of one app. Lightr. adds 23 of those bricks: actions on orders, receivers and organization addresses, plus searches for templates, presets, fonts and countries.

Orders that assemble themselves. When data lands in another app, a signed quote or a completed form, Create an Order opens the order in Lightr., Create a Receiver for an Order attaches the person it concerns, and Finalize an Order takes it to its last step. An office manager no longer copies names from one screen to the other.

A look before anything is final. Put Preview an Order between creation and finalization and send the preview to a colleague through an email or chat module, so a person sees the order before Finalize an Order runs.

An address book that stays accurate. List Organization Addresses, Update an Organization Address and Delete an Organization Address keep the addresses of your Lightr. organization in line with your CRM when a record changes there.

What Make does not do here: Lightr. has no trigger, the module that starts a scenario on its own, so yours starts from another app or from the clock on its first module, every 15 minutes by default. Make also flags its Lightr. documentation as limited, which is why each module below is explained from its name and its type, without field details. When a module is missing, Make an API Call reaches the rest of the Lightr. API with the same connection. To size your plan, read Make pricing; to weigh the other option, see n8n vs Make.

Connect

How do you connect Lightr. to Make?

  1. 01

    Add a Lightr. module

    In your scenario, click the +, search for Lightr. and pick any module, Create an Order for instance. In the module panel, click Create a connection. A connection is your Lightr. account linked to Make once, then reused by all 23 modules.

  2. 02

    Authorize Make

    Naming the connection is optional, but it helps when several Lightr. accounts are linked. Then approve Make on the Lightr. page that opens, or paste the key Lightr. gives you, depending on what the connection window asks for.

  3. 03

    Save and check

    Click Save. Back in the module, Make should now list what it can read from your account. If those lists stay empty, the authorization did not go through: open the connection again and repeat it.

First scenario

Build your first Lightr. scenario

GoalWhen a new entry appears in another app, Make turns it into a Lightr. order and finalizes that order.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the module of the app that holds your source data, a form or a spreadsheet, since Lightr. has no trigger of its own.

  2. 02

    Add Create an Order

    Click the + on the right of that first module, search for Lightr. and choose Create an Order. Click Create a connection if your account is not linked yet.

  3. 03

    Map your data

    Fill the fields of Create an Order with values from the first module. Each bundle, meaning one item passed along such as one form entry, becomes one order.

  4. 04

    Add Finalize an Order

    Use the next + to add Finalize an Order, then map the order that Create an Order returned, so the scenario finalizes the order it just made and no other.

  5. 05

    Test with Run once

    Click Run once. Make executes the scenario one time; open the bubble above each module to read the bundles it received, then check the new order in Lightr.

  6. 06

    Schedule and switch on

    Set the clock on the first module, every 15 minutes by default, and switch the scenario on. Each module run on one bundle is an operation, the unit Make counts on your plan.

Modules

What can each Lightr. module do?

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

Lightr.1

Create a Receiver for an Order

ActionIn the docs only

Attaches a receiver to an order that already exists in Lightr., so the person an order concerns is recorded on it without manual entry. It acts on one order per bundle.

When to use it
a contact comes in from your CRM or a signup form and has to join an order prepared earlier in the scenario.
Watch out
place Create an Order or Get an Order before it, so there is an order to map.
Lightr.2

Create an Order

ActionIn the docs only

Opens a new order in Lightr. from the data your scenario carries, which spares you from rebuilding each order by hand in the Lightr. interface.

When to use it
a purchase, a signed quote or a completed form in another app should become an order.
Watch out
the order it returns is what Finalize an Order, Preview an Order and Create a Receiver for an Order need next, so map it instead of typing it.
Lightr.3

Create an Organization Address

ActionIn the docs only

Stores a new address in your Lightr. organization, ready to be reused on later orders instead of being typed again.

When to use it
a new office or a new client site is added in your CRM and Lightr. should know it too.
Watch out
run List Organization Addresses first when the same address may already exist, or duplicates will pile up.
Lightr.4

Delete an Organization Address

ActionIn the docs only

Removes an address from your Lightr. organization, so nobody picks an outdated one for a new order.

When to use it
a site closes or a client leaves, and the record disappears from your source app.
Watch out
a deletion cannot be taken back from the scenario; test with Run once on a single address you can afford to lose before switching the scenario on.
Lightr.5

Delete an order

ActionIn the docs only

Deletes one order in Lightr., which keeps your list free of test orders and cancelled requests.

When to use it
a request is cancelled in the app that created it, and the matching Lightr. order should go as well.
Watch out
map the order from Get an Order or List Order rather than a typed value, because a wrong order deleted stays deleted.
Lightr.6

Finalize an Order

ActionIn the docs only

Moves a Lightr. order to its finalized state, the step after creation and any edits. With it, one scenario carries an order from start to finish.

When to use it
the order and its receivers are complete and no further change is expected.
Watch out
Make's documentation does not say what Lightr. does after finalization, so try it on one order with Run once before real ones go through.
Lightr.7

Get a Preset

ActionIn the docs only

Fetches a single preset from your Lightr. account so its details can feed the next modules of the scenario.

When to use it
you already know which preset an order should follow and need its data in the flow, not a whole list.
Watch out
when the preset is not known yet, start with List Preset and pick it from the results.
Lightr.8

Get a Template

ActionIn the docs only

Brings one Lightr. template into the scenario, so you can check it or reuse its details before an order is created.

When to use it
each kind of order in your business matches a known template, and the scenario should read it before building the order.
Watch out
List Template is the module for browsing; Get a Template expects you to point at one template.
Lightr.9

Get a User

ActionIn the docs only

Looks up a Lightr. user and passes the result to the following modules, useful when a message or a log elsewhere should name that person.

When to use it
a report in a spreadsheet or a chat notification needs details of a Lightr. user.
Watch out
Make's documentation does not describe what a user record holds, so read the bundle after a Run once before mapping it.
Lightr.10

Get an Order

ActionIn the docs only

Reads one existing Lightr. order, so the rest of the scenario works on its current state rather than on what was known when it was created.

When to use it
a support ticket or an email refers to an order and you want its details in the flow.
Watch out
it returns a single order; to find orders you cannot point at directly, use List Order.
Lightr.11

Get an Organization Address

ActionIn the docs only

Pulls a single address stored in your Lightr. organization into the scenario, where later modules can map it.

When to use it
just before Update an Organization Address, to compare what Lightr. holds with what your CRM says.
Watch out
to find an address you cannot point at directly, run List Organization Addresses first.
Lightr.12

List Countries

SearchIn the docs only

Lists the countries Lightr. knows, giving the scenario a reference to check an address against.

When to use it
addresses come from a form where people type their country freely, and you want to match them to an entry of the Lightr. list.
Watch out
as a search, it returns one bundle per country, so every module placed after it runs once per country.
Lightr.13

List Fonts

SearchIn the docs only

Returns the fonts available in Lightr., so a scenario can check them without anyone opening the app.

When to use it
you want to see which fonts your account offers before filling an order, or keep that list in a shared sheet.
Watch out
each font arrives as its own bundle, and every module after it runs once per font, which adds operations.
Lightr.14

List Order

SearchIn the docs only

Searches your Lightr. orders and returns zero, one or several of them, one bundle each.

When to use it
you need several orders at once, to report on them in a spreadsheet or to update them together.
Watch out
Update an Order or Delete an order placed after it applies to every order found, so test with Run once and read the bundles first.
Lightr.15

List Organization Addresses

SearchIn the docs only

Collects the addresses saved in your Lightr. organization, one bundle per address, ready to compare or to copy elsewhere.

When to use it
before Create an Organization Address, to check the address is not already there, or to mirror the whole book in a spreadsheet.
Watch out
each address found runs the next module once. That adds up in operations on a large book.
Lightr.16

List Preset

SearchIn the docs only

Shows the presets stored in Lightr., which lets the scenario choose one from data instead of relying on a fixed choice.

When to use it
the preset depends on information from another app, and you want to pick it among the results.
Watch out
the search can come back empty; plan for that case before Create an Order relies on a preset.
Lightr.17

List Receivers by an Order

SearchIn the docs only

Gives you every receiver attached to a given order, so you see who an order concerns without opening Lightr.

When to use it
before Finalize an Order, to check that all receivers are there, or to copy them into a shared sheet.
Watch out
it needs an order to start from, mapped from Create an Order, Get an Order or List Order.
Lightr.18

List Template

SearchIn the docs only

Browses the templates of your Lightr. account and hands each one to the scenario as a separate bundle.

When to use it
you are setting up the scenario and want to see which templates exist, or you keep a catalog of them in another tool.
Watch out
when the template is already known, Get a Template does the job in one run instead of one run per result.
Lightr.19

Make an API Call

ActionIn the docs only

Calls any endpoint of the Lightr. API from the scenario, with the same connection as the other modules, which covers what the listed modules leave out.

When to use it
the Lightr. API offers an operation you need and no module on this page matches it.
Watch out
you rely on the Lightr. API reference here, and Make's own documentation for this app is limited, so test each call with Run once.
Lightr.20

Preview an Order

ActionIn the docs only

Asks Lightr. for a preview of an order, which gives a person something to check before the order goes further.

When to use it
a colleague approves orders, and the preview can reach them through an email or messaging module.
Watch out
Make's documentation does not describe what the preview contains, so run it once and read the bundle before mapping it.
Lightr.21

Replicate an Order

ActionIn the docs only

Creates a copy of an existing Lightr. order, which saves you from rebuilding an order that is almost identical.

When to use it
the same order has to go out again for a new request, with the original as its base.
Watch out
the copy is a new order; to add a receiver to it, place Create a Receiver for an Order after this module and map the copy.
Lightr.22

Update an Order

ActionIn the docs only

Changes an order that already exists in Lightr., so a correction made in your source app reaches the order too.

When to use it
details change after the order was created, and deleting it to start over would lose work.
Watch out
run it before Finalize an Order; the documentation does not say whether a finalized order can still be edited.
Lightr.23

Update an Organization Address

ActionIn the docs only

Edits an address saved in your Lightr. organization, keeping it in line with the record your team maintains in another tool.

When to use it
a client moves and your CRM gets the new address first.
Watch out
map the address from Get an Organization Address or List Organization Addresses, so the update lands on the right one and not on a lookalike.
Need help

Need help automating Lightr. with Make?

A person reads every message.

FAQ

Lightr. and Make: common questions

01Is the Lightr. Make integration free?
Yes. Lightr. is a standard app in Make, so it works from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Make counts usage in credits, one operation per module run on one bundle. Any cost on the Lightr. side is a separate matter.
02What do you need to connect Lightr. to Make?
A Lightr. account and a Make account. Make's documentation lists no other prerequisite for Lightr. and gives no official connection steps, so the generic path applies: add a Lightr. module, click Create a connection, name it if you like, approve Make on the Lightr. page or paste the key Lightr. provides, then click Save. That single connection then serves all 23 modules. If the lists inside a module stay empty after saving, the authorization did not complete and has to be redone.
03Can a Lightr. scenario start on its own?
Not from Lightr. itself, because the app has no trigger module in Make, neither scheduled nor instant. A trigger is the first module, the one that starts a scenario. Two workarounds exist. Open the scenario with a trigger from another app, a form or a spreadsheet for example, and add the Lightr. modules after it. Or place a Lightr. search such as List Order first and set the clock on that module: Make runs it every 15 minutes by default, or at the interval you choose, with 15 minutes as the minimum on the Free plan.
04What if a Lightr. module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Lightr. API from the scenario with the connection already in place, so nothing new needs authorizing. It covers operations the 16 actions and 7 searches do not offer. Keep in mind that Make flags its Lightr. documentation as limited, for lack of public information about the app, so check the Lightr. API reference and test each call with Run once before switching the scenario on. If the constraint comes from Make itself, compare plans: execution time and minimum interval differ between Free and paid.
05Make or n8n for the Lightr. integration?
It depends on the actions your process needs. In Make, Lightr. comes with 23 ready modules around orders, receivers, addresses, templates, presets and fonts, plus Make an API Call for the rest, all behind one connection. On the n8n side, first check whether a Lightr. node exists and which operations it covers, since this page documents Make only. The fair criterion is coverage: choose the tool whose modules match your steps, then weigh plan limits such as active scenarios and minimum interval. No ranking of the two tools holds for every team.
Same platform

Other docs you might need on this stack.

Browse all integrations