Resources · Make integration

Lightspeed eCom Make integrationAutomate Lightspeed eCom with Make.

Can Make run the back office of your Lightspeed eCom store for you? The Lightspeed eCom Make integration gives you 46 modules: one instant trigger, 36 actions and 9 searches. This page shows what each one does, how to link your store and how to build a first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Lightspeed eCom Make integration do for your store?

The Lightspeed eCom Make integration links your store to Make, a no-code tool where you build a scenario (the automation itself, a chain of modules). Each module is one brick: it listens for a store event, creates or updates a record, or searches your catalog, so products, orders and discounts move without copy and paste.

Support that never misses a signal. Watch Event wakes your scenario as soon as something happens in the store, and Create a Ticket opens a follow-up for the team with the details of that event.

A catalog that stays tidy. Search Products finds the items that match your filter, then Update a Product or Create a Tag fixes them one by one. Pair it with a spreadsheet tool such as Airtable and your supplier list can drive the store instead of the other way round.

Promotions you switch on and off from one place. Create a Discount launches the code, Update a Discount changes it, Delete a Discount removes it when the campaign ends. No need to reopen the admin panel each time.

Where the listed modules stop, Make an API Call reaches any endpoint of the Lightspeed eCom API with the same connection. The documentation behind this app is flagged as AI-generated by Make, so test each module before you trust it with live orders. The same store can also be automated with n8n; the n8n vs Make comparison lays out the differences. To learn the editor properly, the Make training starts from zero, and Make pricing explains how operations are counted.

Connect

How do you connect your Lightspeed eCom store to Make?

  1. 01

    Create an API key in Lightspeed eCom

    In your store, open Settings > Store Settings > Developers and click New API key. Name it, save, turn on the switch under SETTINGS, tick the permissions Make will need and save again.

  2. 02

    Copy the key and the secret

    Under DETAILS, copy the API key. Then click Show to reveal the API secret and copy it too. Keep both at hand: Make asks for them in the next step, and nothing else.

  3. 03

    Add the connection in Make

    Add any Lightspeed eCom module to your scenario and click Create a connection. A connection is your store linked to Make once, reused by every Lightspeed eCom module. Give it a name if you like, paste the key and the secret, and confirm.

First scenario

Your first scenario: turn a store event into a support ticket

GoalWhen an event occurs in Lightspeed eCom, Make opens a ticket so nobody on the team misses it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module.

  2. 02

    Set up Watch Event

    Search for Lightspeed eCom, pick Watch Event, click Create a webhook, then Create a connection with the key and secret from your store.

  3. 03

    Add Create a Ticket

    Click the + on the right of Watch Event, choose Create a Ticket and map the event data into it, so each ticket says what happened.

  4. 04

    Test with Run once

    Click Run once, then trigger an event in the store. Open the bubbles above each module to read the bundle (the item passed along) each one received.

  5. 05

    Switch it on

    When the ticket looks right, save and switch the scenario on. Being instant, Watch Event starts it on each event instead of waiting for a schedule.

Triggers

What starts a Lightspeed eCom scenario

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

Lightspeed eCom1Watch Event

Watch Event

Instant trigger

In MakeTriggers when an event occurs.

Watch Event is the only trigger of the app: it starts your scenario each time an event occurs in your Lightspeed eCom store and hands the details of that event to the next module as a bundle.

How it fires
instant, Lightspeed eCom calls Make through a webhook as soon as the event happens, so there is no schedule to set and no polling.
When to use it
whenever the store itself should decide when the work starts, for example to open a ticket or tag a record right after the event.
Watch out
Make asks you to click Create a webhook before Create a connection. Run once and read the first bundle before mapping anything, because only that bundle shows what the event really carries.
Modules

What the Lightspeed eCom modules can do

Lightspeed eCom gives you 45 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Lightspeed eCom1

Add a Product to a Checkout

Action

In MakeAdds products to the checkout.

This module drops a product into a checkout that already exists, so the cart your scenario prepares holds the goods a customer chose elsewhere.

When to use it
right after Create a Checkout, when an order taken by phone or chat has to become a real cart in the store.
Watch out
the checkout has to exist first; map it from the module that created it instead of typing it by hand.
Lightspeed eCom2

Create a Checkout

Action

In MakeCreates a new checkout.

Create a Checkout opens a brand new checkout in your store, the empty starting point that later modules fill and close.

When to use it
when a sale starts outside the storefront, say from a form or a sales call, and you still want it to follow the store's normal checkout path.
Watch out
an empty checkout sells nothing; chain Add a Product to a Checkout and Finish a Checkout after it.
Lightspeed eCom3

Create a Checkout by Quote

Action

In MakeCreates a checkout based on an existing quote.

Starting from a quote that already sits in the store, this module turns it into a checkout, so the customer pays for exactly what was offered.

When to use it
for B2B deals where a quote gets approved first and the customer should pay without anyone retyping the lines.
Watch out
it only works from an existing quote; if you have none, pick Create a Checkout instead.
Lightspeed eCom4

Create a Custom Status

Action

In MakeCreates a new custom status.

With Create a Custom Status you add a new status to the store, a label that describes a step your standard statuses do not cover.

When to use it
when you set up a new process, such as a made-to-order line, and want the status created the same way in every store you run.
Watch out
this module creates the status without applying it to an order; to move an order along, look at Update an Order.
Lightspeed eCom5

Create a Discount

Action

In MakeCreates a new discount.

Launching a promotion from a scenario is what Create a Discount is for: it adds a new discount to the store in one operation (one run of one module, the unit Make counts on your plan).

When to use it
when campaigns are planned in a spreadsheet or a CRM and you want each line to become a live discount.
Watch out
the discount lands in your real store, so try it first with Run once on a test line.
Lightspeed eCom6

Create a Group

Action

In MakeCreates a new group.

A new group lands in your store each time this module runs, which saves you building segments one by one in the admin panel.

When to use it
when a customer segment is defined elsewhere, a wholesale list for instance, and the store needs a matching group.
Watch out
run Search Groups first if the scenario may repeat, otherwise you end up with several groups under the same name.
Lightspeed eCom7

Create a Product

Action

In MakeCreates a new product.

Create a Product adds an item to your catalog straight from the scenario, fed by whatever source holds your product data.

When to use it
when new references arrive from a supplier file or a product sheet and you would rather not key them in twice.
Watch out
nothing stops duplicates on its own; check with Search Products before creating, and add a filter between the two modules.
Lightspeed eCom8

Create a Subscription

Action

In MakeCreates a new subscription.

Here a new subscription is recorded in Lightspeed eCom for you, without anyone opening the store to add it.

When to use it
when people sign up somewhere else, at a trade fair or through a partner form, and should appear in the store's subscriptions too.
Watch out
you cannot know in advance what a subscription holds; open the module in Make and check the fields it lists before mapping.
Lightspeed eCom9

Create a Tag

Action

In MakeCreates a new tag.

Tags are how you sort things in the store, and Create a Tag adds a new one without leaving your scenario.

When to use it
when a new season, collection or campaign needs its own label before products get sorted under it.
Watch out
create the tag once, early in the flow; a scenario that runs it on every bundle creates the same tag again and again.
Lightspeed eCom10

Create a Tax

Action

In MakeCreates a new tax.

Create a Tax registers a new tax in your store, handy when you roll the same setup out to several shops.

When to use it
when you open a new store or a new market and want the tax setup copied from a reference store instead of typed.
Watch out
taxes touch every price; compare the result with List Taxes and a test order before you switch the scenario on.
Lightspeed eCom11

Create a Ticket

Action

In MakeCreates a new ticket.

Create a Ticket opens a new ticket in Lightspeed eCom, so a request or an alert becomes something the team can track and close.

When to use it
behind Watch Event, or behind a contact form from another app, whenever a customer issue should not live only in an inbox.
Watch out
map a clear subject from the incoming bundle; a ticket that only says the event happened helps nobody.
Lightspeed eCom12

Delete a Discount

Action

In MakeDeletes an existing discount.

Delete a Discount removes a discount from the store for good, the clean way to close a promotion once it is over.

When to use it
when a campaign ends in your planning tool and the code should disappear from the store at the same moment.
Watch out
a delete cannot be undone from Make; if you only want to pause the offer, Update a Discount is the safer pick.
Lightspeed eCom13

Delete a Group

Action

In MakeDeletes an existing group.

Old segments pile up, and Delete a Group clears one out of your store in a single step.

When to use it
when a wholesale program or a one-off event group is retired in your CRM and the store should follow.
Watch out
there is no undo; look the group up with Get a Group first so you delete the right one.
Lightspeed eCom14

Delete a Product

Action

In MakeDeletes an existing product.

This module takes a product out of your catalog permanently, driven by your scenario instead of a manual clean-up.

When to use it
when a supplier drops a reference for good and it must vanish from the store too.
Watch out
a product deleted by mistake is gone; put a filter before this module, and test it with Run once on a dummy product.
Lightspeed eCom15

Delete a Tag

Action

In MakeDeletes an existing tag.

Delete a Tag removes a tag you no longer need, so the list stays short enough to use.

When to use it
after a seasonal collection ends, once its products have been retagged or archived.
Watch out
run Search Tags first to confirm the exact tag; a similar name is easy to hit by mistake, and a deleted tag does not come back on its own.
Lightspeed eCom16

Delete a Tax

Action

In MakeDeletes an existing tax.

Delete a Tax takes a tax off the store, which is useful when a rate or a region no longer applies.

When to use it
when you tidy the tax setup of several stores at once from one reference list.
Watch out
removing a tax changes how prices are computed; check with Get a Tax which one you target, and keep this module out of any untested flow.
Lightspeed eCom17

Delete a Ticket

Action

In MakeDeletes an existing ticket.

Deleting a ticket is the whole job of this module: the ticket leaves the store's list for good.

When to use it
to clear test tickets or spam that a form let through, rather than resolved requests the team may need to look back at.
Watch out
a deleted ticket is gone for good; for a real request, move it forward with Update a Ticket instead.
Lightspeed eCom18

Finish a Checkout

Action

In MakeValidates and finishes a checkout.

Finish a Checkout validates the checkout and closes it, the last step that turns a prepared cart into a completed sale.

When to use it
at the end of a flow that started with Create a Checkout and Add a Product to a Checkout, once everything is in place.
Watch out
validation can refuse an incomplete checkout; if the module errors, open the bundle after Run once to see what is missing.
Lightspeed eCom19

Get a Discount

Action

In MakeRetrieves a single discount.

Get a Discount returns the full details of one discount you already know, ready to map into the next module.

When to use it
before sending a promo code to a customer or a partner, to check it still exists and show what it offers.
Watch out
it reads one discount only; to find a discount without knowing which one, start with Search Discounts.
Lightspeed eCom20

Get a Group

Action

In MakeRetrieves a single group.

One group, all its details: that is what Get a Group fetches when you already know which group you mean.

When to use it
to confirm a group before a delete or an update, or to copy its settings into a report.
Watch out
without a known group this module has nothing to read; put Search Groups in front when you only have a name.
Lightspeed eCom21

Get an Invoice

Action

In MakeRetrieves a single invoice.

Get an Invoice pulls one invoice out of the store so the rest of the scenario can file it, send it or copy its amounts.

When to use it
when your accounting tool needs the invoice behind a sale the scenario already knows about.
Watch out
it returns a single invoice; to go through a batch of them, Search Invoices is the module to start with.
Lightspeed eCom22

Get an Order

Action

In MakeRetrieves a single order.

With Get an Order the scenario reads one order in full, so a later module can work with its contents instead of a bare reference.

When to use it
when another tool holds only the order reference and you need the rest, for a shipping label or a thank-you message.
Watch out
it reads, it never changes anything; to edit the order afterwards, add Update an Order.
Lightspeed eCom23

Get a Product

Action

In MakeRetrieves a single product.

This module fetches a single product with its details, so the scenario works on fresh store data rather than an old copy.

When to use it
before posting a product to a marketplace or a newsletter, to make sure what you publish matches the store.
Watch out
variants have their own search, Search Variants; look there when a product comes in several versions.
Lightspeed eCom24

Get a Tag

Action

In MakeRetrieves a single tag.

Get a Tag reads one tag and returns what the store knows about it, a small check that saves mistakes further down.

When to use it
in a clean-up flow, to confirm a tag is the right one before Update a Tag or Delete a Tag acts on it.
Watch out
it needs a tag you can already point to; with only a word in mind, run Search Tags first.
Lightspeed eCom25

Get a Tax

Action

In MakeRetrieves a single tax.

Get a Tax returns one tax with its settings, the reference point before you copy or change it.

When to use it
when a second store should match the tax setup of the first one, and you want to read the source before writing.
Watch out
to see every tax of the store rather than one, List Taxes is the right module.
Lightspeed eCom26

Get a Ticket

Action

In MakeRetrieves a single ticket.

Get a Ticket brings back one ticket in full, so you can pass its details to a chat tool or a report.

When to use it
when an alert in another app mentions a ticket and the team needs its content without opening the store.
Watch out
it only reads; any change goes through Update a Ticket.
Lightspeed eCom27

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Make an API Call is the way out when no listed module does what you need: it calls any endpoint of the Lightspeed eCom API with the connection you already set up.

When to use it
for an object or an operation missing from the other modules, once you have found it in the Lightspeed eCom API documentation.
Watch out
here you write the request yourself, and the API key only reaches what its permissions allow.
Lightspeed eCom28

Update a Discount

Action

In MakeUpdates an existing discount.

Update a Discount changes a discount that is already live, without deleting it and starting over.

When to use it
when a promotion gets extended or adjusted in your planning sheet and the store should match it.
Watch out
the change is live as soon as the module runs; try it on a test discount with Run once before connecting it to real campaigns.
Lightspeed eCom29

Update a Group

Action

In MakeUpdates an existing group.

This module edits an existing group, keeping its place in the store while its details change.

When to use it
when a segment is renamed or redefined in your CRM and the store group has to follow.
Watch out
point it to the right group with Get a Group or Search Groups first; updating the wrong one is quiet and hard to spot.
Lightspeed eCom30

Update an Invoice

Action

In MakeUpdates an existing invoice.

Update an Invoice edits an invoice already stored in Lightspeed eCom, so a correction made elsewhere reaches the store too.

When to use it
when your accounting tool marks a change on an invoice and both sides should say the same thing.
Watch out
invoices matter to your accountant; test on a single invoice and read the result before running it on many.
Lightspeed eCom31

Update an Order

Action

In MakeUpdates an existing order.

Update an Order changes an existing order, for instance to move it forward when something happens outside the store.

When to use it
when your warehouse or carrier tool reports progress and the order should reflect it, possibly with a status made by Create a Custom Status.
Watch out
an order belongs to a real customer; check the mapping on one order with Run once first.
Lightspeed eCom32

Update a Payment Method

Action

In MakeUpdates a payment method.

Update a Payment Method changes one of the store's payment methods from the scenario, rather than through the settings screens.

When to use it
when you manage several stores and want a payment setting changed the same way everywhere.
Watch out
payment is the last place for a surprise; keep this module in a scenario you run on purpose and test on a store with no live traffic if you can.
Lightspeed eCom33

Update a Product

Action

In MakeUpdates an existing product.

Update a Product edits an item of your catalog, so the source you trust for product data keeps the store current.

When to use it
after Search Products, to fix a batch of items one bundle at a time, or when a supplier sheet changes a description.
Watch out
each product updated costs one operation; filter the search so only the items that really changed reach this module.
Lightspeed eCom34

Update a Subscription

Action

In MakeUpdates an existing subscription.

Update a Subscription edits a subscription the store already has, so a change made in another tool is not lost.

When to use it
when a subscriber changes their sign-up in your CRM or a form and the store should follow.
Watch out
you need the subscription the change belongs to; map it from an earlier module rather than guessing it.
Lightspeed eCom35

Update a Tag

Action

In MakeUpdates an existing tag.

Renaming or adjusting a tag without recreating it is the job of Update a Tag.

When to use it
when your naming changes, a collection gets a new name for example, and every store should carry the same wording.
Watch out
confirm the tag with Get a Tag first; two tags with close names are easy to mix up in a mapping.
Lightspeed eCom36

Update a Ticket

Action

In MakeUpdates an existing ticket.

Update a Ticket moves an existing ticket forward, so its state in the store follows what the team actually did.

When to use it
when the reply happens in another tool, a help desk or a chat, and the Lightspeed eCom ticket should not stay open by mistake.
Watch out
map the ticket from the scenario that created it or from Search Tickets, never by hand.
Lightspeed eCom37

List Taxes

Search

In MakeRetrieves a list of all tax objects from this shop.

List Taxes returns every tax set in the store, one bundle per tax, so you can review or copy the whole setup.

When to use it
for an audit sheet of the tax setup, or as the source when a new store should get the same taxes through Create a Tax.
Watch out
each tax becomes its own bundle, and every module after it runs once per tax.
Lightspeed eCom38

Search Discounts

Search

In MakeRetrieves a list of all discount objects from this shop.

Search Discounts lists the discount objects of the store, the starting point when you need to act on several promotions.

When to use it
to export all running codes to a sheet for the marketing team, or to find the ones Delete a Discount should remove.
Watch out
a search can return zero, one or many bundles; add a filter before any delete so only the intended discounts go through.
Lightspeed eCom39

Search Groups

Search

In MakeRetrieves a list of all group objects from this shop.

Search Groups brings back the groups of your store, handy when you know a group by name but not which record it is.

When to use it
before Create a Group, to check the group is not already there, or before Update a Group on a whole set.
Watch out
if nothing matches, the next modules do not run at all, which can look like a silent failure while testing.
Lightspeed eCom40

Search Invoices

Search

In MakeRetrieves a list of all invoice objects from this shop.

Search Invoices returns the invoices of the store as separate bundles, ready to be copied into another tool.

When to use it
when your accountant wants invoices in a shared spreadsheet or folder instead of downloading them one by one.
Watch out
a broad search on a busy store means many bundles, and each module after it counts one operation per invoice.
Lightspeed eCom41

Search Orders

Search

In MakeRetrieves a list of all order objects from this shop.

Pull the orders of your Lightspeed eCom shop into your scenario, each one arriving as a bundle, the unit of data Make hands from one module to the next.

When to use it
pick it when you need to review many orders at once, such as pushing them into a spreadsheet; if you already hold one order ID, Get an Order is the lighter choice.
Watch out
a search can return zero, one or many bundles, so test with Run once before adding the next module.
Lightspeed eCom42

Search Products

Search

In MakeRetrieves a list of all product objects from this shop.

This module gives you the product catalog of your store as a stream of bundles, ready to be copied into another tool or checked one by one. It is the starting point for any catalog export.

When to use it
a merchandiser who wants the full product range in Google Sheets or a PIM starts here, while Get a Product fits a single known item.
Watch out
the search covers every product of the shop, so the operation count of your scenario grows with your catalog.
Lightspeed eCom43

Search Tags

Search

In MakeRetrieves a list of all tag objects from this shop.

Here you obtain every tag defined in the shop, handy to check which labels already exist before your scenario creates a new one. That check keeps your tag list clean.

When to use it
place it just before Create a Tag, so the scenario reuses an existing label instead of adding a duplicate; Get a Tag suits the case where the ID is already known.
Watch out
when nothing matches, the module sends no bundle and the modules after it receive nothing to work with.
Lightspeed eCom44

Search Tickets

Search

In MakeRetrieves a list of all ticket objects from this shop.

With this search, the support tickets of your Lightspeed eCom shop land in Make as bundles, so a customer service lead can see them outside the back office. Each ticket then feeds whatever module comes next.

When to use it
reach for it to build a digest of tickets for your team chat or to log them in a helpdesk sheet; Update a Ticket then acts on one of them.
Watch out
the result may hold several tickets, so map the ticket ID carefully before any update.
Lightspeed eCom45

Search Variants

Search

In MakeRetrieves a list of all variant objects from this shop.

Variants are the sizes, colors or versions of a product, and this module lists them for you as separate bundles. It shows the real sellable items behind each product page.

When to use it
choose it over Search Products when your work happens at variant level, such as syncing each size with a warehouse sheet.
Watch out
one product can hold many variants, so a single run may produce far more bundles, and more operations, than you expect.
Need help

Need help automating Lightspeed eCom with Make?

A person reads every message.

FAQ

Lightspeed eCom and Make: frequent questions

01Is the Lightspeed eCom Make integration free?
Yes, Lightspeed eCom is a standard app in Make, so its modules work from the Free plan. That plan limits you to 2 active scenarios, runs of 5 minutes at most, files up to 5 MB and 512 MB of data transfer, with scheduled runs no closer than 15 minutes apart. Watch Event is instant, so that interval does not slow it down. Paid plans lift the limits and count usage in credits. You still need a Lightspeed eCom account of your own, which Make does not provide.
02What do you need to connect Lightspeed eCom to Make?
An active Lightspeed eCom account and an API key with its secret. Create the key in Settings, Store Settings, Developers, turn it on, tick the permissions Make should have and copy both values. In Make, add a Lightspeed eCom module, click Create a connection, name it if you want and paste the two values. For Watch Event, click Create a webhook first. The permissions you tick decide what the modules can reach later.
03Does the Lightspeed eCom trigger in Make react in real time?
Yes. Watch Event is an instant trigger: Lightspeed eCom calls Make through a webhook as soon as the event occurs, and the scenario starts without waiting for a schedule. That is the lightning badge on the module in the editor. It is also the only trigger the app has. To start a flow on a schedule instead, open it with another module, such as Search Orders, and set the clock on that first module; a new scenario runs every 15 minutes by default.
04What if the Lightspeed eCom module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Lightspeed eCom API with the connection you already created, so an object or action missing from the listed modules is still within reach. You write the request yourself, based on the Lightspeed eCom API documentation. Make also warns that the documentation of this app is AI-generated and may contain mistakes, so check anything critical with Lightspeed eCom and test each module with Run once.
05Should you use Make or n8n for Lightspeed eCom?
It depends on the tool your team already works in. On the Make side, this page can vouch for 46 modules, one instant trigger and Make an API Call for the rest, all available from the Free plan. The same store often has an n8n node as well, and the facts collected here do not rank one above the other. Compare the modules each tool offers for the objects you actually use, orders, tickets or discounts, and pick the editor your team will keep maintaining.