Resources · Make integration

Loyverse Make integrationAutomate Loyverse with Make.

What if every sale, stock change and new customer in your till reached your other tools by itself? The Loyverse Make integration gives you 38 modules, 7 of them triggers. This guide connects your account and walks you through a first working scenario.

Try the Loyverse integration on MakeSee the 38 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Loyverse Make integration do for your shop?

The Loyverse Make integration links your point-of-sale account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single step such as a trigger, an action or a search. Loyverse brings 38 of them, covering receipts, items, stock, customers, staff, stores and POS devices.

Sales that reach your books. Watch Receipts picks up new and edited receipts, and the next module writes each sale wherever your bookkeeping lives. Get a Store adds the location name when you run several shops.

Low-stock alerts that go out on their own. Watch Updated Inventory Levels is the one instant trigger here: Loyverse calls Make as soon as a count changes. Add Get an Item and your alert names the product instead of showing a raw ID.

A catalog you maintain in one place. Keep product data in a spreadsheet, then let Create an Item, Update an Item and Upload an Image push it to the till.

Know the limits before you start. The other six triggers are scheduled, so Make only sees changes when it checks, every 15 minutes by default. Anything the listed modules skip goes through Make an API Call, with the same connection. Plans and their limits are laid out on Make pricing, and if you are weighing tools, n8n vs Make compares the two. New to the editor? Make training starts from zero.

Connect

How do you connect Loyverse to Make?

  1. 01

    Create an access token in Loyverse

    In the Loyverse Back Office, open Access Tokens and click Add access token. Give it a name you will recognize, set an expiration date only if you need one, click Save, then copy the token shown.

  2. 02

    Add a Loyverse module in Make

    In your scenario, add any Loyverse module and click Create a connection. A connection is your Loyverse account linked to Make once, then reused by every Loyverse module. The Connection name field is optional.

  3. 03

    Paste the token and save

    Paste the token you copied from Loyverse into the credentials Make asks for, or follow the on-screen instructions. Once it saves, Make can read your Loyverse data and list what the module needs.

First scenario

Build your first scenario: web signups become Loyverse customers

GoalWhen someone signs up through another app, such as your website form, Make creates the matching customer in Loyverse.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. The first module is the app where signups arrive, for example your form tool.

  2. 02

    Set up the signup source

    Pick that app's module that sees new signups and connect your account. Each signup travels through the scenario as a bundle, meaning one item passed from a module to the next.

  3. 03

    Add Create a Customer

    Click the + on the right, search Loyverse, choose Create a Customer and link your account with the token. Map the signup details into the customer fields Make shows.

  4. 04

    Test with Run once

    Submit a test signup, then click Run once. Open the bubbles to read what each module received, and check the new customer in the Loyverse Back Office.

  5. 05

    Schedule and switch it on

    On the first module, set the schedule (every 15 minutes by default) and switch the scenario on. From then on, each new signup lands in Loyverse without anyone retyping it.

Triggers

Which Loyverse events can start a scenario?

7 modules start a scenario when something happens in Loyverse. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Loyverse as soon as it happens.

Loyverse1Watch Customers

Watch Customers

Scheduled trigger

In Make“Triggers when customers are added or updated.”

Every customer added or edited in Loyverse reaches your scenario, so a loyalty signup made at the counter can flow into your email tool without anyone copying it. The docs only mention added and updated customers, so do not count on deletions here.

How it fires
scheduled. Make checks Loyverse on the scenario's schedule, every 15 minutes by default, and starts the run when it finds new or edited customers.
When to use it
cashiers register shoppers at checkout and marketing needs those contacts in another tool.
Watch out
new and edited customers come through the same trigger, so design the next module to handle both cases.
Loyverse2Watch Employees

Watch Employees

Scheduled trigger

In Make“Triggers when employees are added, updated, or deleted.”

Your staff list in another tool stays in line with Loyverse: hire someone, change their details or remove them, and the scenario hears about it. That makes it the trigger for anything built around who works in your shops.

How it fires
scheduled. Make queries Loyverse at the rhythm set on the scenario and picks up employees that were added, updated or deleted.
When to use it
an HR sheet or a scheduling app should mirror the team you manage in the Back Office.
Watch out
departures arrive too, so make sure a deleted employee is not recreated by mistake further down the scenario.
Loyverse3Watch Items

Watch Items

Scheduled trigger

In Make“Triggers when items are added, updated, or deleted.”

Catalog changes leave Loyverse on their own: a product added, edited or deleted in the Back Office becomes a signal your scenario can pass to an online store or a price sheet.

How it fires
scheduled. Make looks at your items each time the scenario's schedule comes round, then runs with whatever changed.
When to use it
the till is where your team edits products, and other channels should follow it rather than being updated by hand.
Watch out
avoid pairing it with Update an Item on the same products, because your own edit counts as an update and can start the scenario again.
Loyverse4Watch Payment Types

Watch Payment Types

Scheduled trigger

In Make“Triggers when payment types are added, updated, or deleted.”

You learn when a way to pay changes in Loyverse, whether a payment type is added, renamed or removed, so the tools that reconcile your takings keep the same list as the till.

How it fires
scheduled. On each run of the scenario's schedule, Make asks Loyverse for payment types that were created, updated or deleted.
When to use it
your bookkeeping sorts sales by payment method and a new option at the counter should appear there as well.
Watch out
a deletion also triggers a run, so check what kind of change arrived before the next module writes anything.
Loyverse5Watch Receipts

Watch Receipts

Scheduled trigger

In Make“Triggers when receipts are added, updated, or deleted.”

Each sale rung up in Loyverse can start a scenario, which is the backbone of most setups: sales flowing into a spreadsheet, an accounting app or a daily summary for the owner.

How it fires
scheduled. Make checks Loyverse whenever the scenario's schedule comes due and catches receipts that were added, updated or deleted.
When to use it
you want every transaction recorded outside the till, without exporting files by hand.
Watch out
an edited receipt shows up again, so look for it in your destination first instead of adding a second line for the same sale.
Loyverse6Watch Stores

Watch Stores

Scheduled trigger

In Make“Triggers when stores are added, updated, or deleted.”

Opening, changing or closing a location in Loyverse becomes an event your other tools can act on, which matters most when you run more than one shop.

How it fires
scheduled. Make polls Loyverse on the scenario's schedule and returns stores that were added, updated or deleted since it last looked.
When to use it
a reporting sheet or a staff directory lists your stores and must follow what the Back Office says.
Watch out
these events are rare, so a scenario built on this trigger may stay quiet for a long time; that is normal, not a broken connection.
Loyverse7Watch Updated Inventory Levels

Watch Updated Inventory Levels

Instant trigger

In Make“Triggers when an inventory level is updated.”

Stock moves reach your scenario the moment they happen, which makes this the trigger for low-stock alerts and reorder requests that cannot wait for a scheduled check.

How it fires
instant. Loyverse calls Make through a webhook as soon as an inventory level is updated. When you add the module, click Create a webhook, then Create a connection.
When to use it
your buyer should hear about a stock drop right away, with Get an Item added to name the product.
Watch out
it is the only instant trigger of the seven; keep Update Inventory Levels out of the same scenario, or your own change will fire it again.
Modules

What can Make do in Loyverse?

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

Loyverse1

Create a Customer

Action

In Make“Creates a new customer.”

A shopper who signs up online or books through another tool ends up in your Loyverse customer base, ready for your cashiers to find at checkout.

When to use it
a form on your website collects new customers who should exist in the till before their first visit.
Watch out
if the same person may already be registered, run List Customers first, or you will end up with two records.
Loyverse2

Create an Item

Action

In Make“Creates a new item.”

New products reach your register without manual entry: the module adds an item to the Loyverse catalog from data mapped out of an earlier step.

When to use it
a supplier sends a product list in a spreadsheet and each new line should become an item you can sell.
Watch out
another size or color of a product you already sell belongs in Create an Item Variant, not in a near-duplicate item.
Loyverse3

Create an Item Variant

Action

In Make“Creates a new variant of an item.”

You get one more version of a product you already sell, such as a new size, without rebuilding the item from scratch.

When to use it
a best seller comes in a new option and the till must offer it next to the existing ones.
Watch out
the variant hangs on an existing item, so the scenario needs that item first, from Create an Item, Get an Item or List Items.
Loyverse4

Create a POS

Action

In Make“Creates a new POS device.”

A new till shows up in Loyverse without a trip to the Back Office, because this module registers a POS device straight from your scenario.

When to use it
you track a store opening in a project sheet and want each device marked ready to be set up in Loyverse.
Watch out
run List POS beforehand when there is any chance the device already exists, so you do not register it twice.
Loyverse5

Create a Receipt

Action

In Make“Creates a new receipt by the store ID.”

Sales made outside the till still land in your Loyverse history, so reports cover everything you sold and not just the counter.

When to use it
orders taken at a market stall or through an online shop should appear alongside in-store sales.
Watch out
the receipt is created for a store ID, so fetch the right one with List Stores or Get a Store before this step.
Loyverse6

Delete a Customer

Action

In Make“Removes a customer by the customer ID.”

Your customer list loses a record as soon as the scenario says so, which keeps the base clean when someone should no longer be in it.

When to use it
a shopper asks for their data to be removed and your request form starts the cleanup.
Watch out
the module works from the customer ID; treat the deletion as final and test with Run once on a dummy customer.
Loyverse7

Delete an Image

Action

In Make“Removes an image of an item by the item ID.”

An outdated product photo comes off its item, found by the item ID, so nobody keeps selling from a picture that no longer matches the shelf.

When to use it
a product changes packaging and the old image has to go before the new one is added.
Watch out
this only removes; to swap a picture, follow it with Upload an Image in the next step.
Loyverse8

Delete an Item

Action

In Make“Removes an item by the item ID.”

Discontinued products leave the catalog without anyone opening the Back Office: the module removes the item that matches the ID you give it.

When to use it
your purchasing sheet marks a product as dropped and the till should stop offering it.
Watch out
check the ID with Get an Item before this step, and treat the removal as final.
Loyverse9

Delete a POS

Action

In Make“Deletes a POS device.”

Retired tills disappear from your Loyverse account, keeping the device list honest when hardware leaves service.

When to use it
a store closes or a register is replaced, and your equipment tracker records the change first.
Watch out
use List POS to pick the exact device, since deleting the wrong one hits a checkout your team still uses every day.
Loyverse10

Get a Customer

Action

In Make“Retrieves details of a customer by the customer ID.”

The full profile of one customer comes back when you already hold their ID, ready to personalize a message or fill a CRM record.

When to use it
an earlier step hands you a customer ID and the next one needs the person's details, not just a number.
Watch out
without the exact ID this module cannot help; start from List Customers and pick from what it returns.
Loyverse11

Get an Employee

Action

In Make“Retrieves details of an employee by the employee ID.”

You see who is behind an employee ID, with the details Loyverse keeps for that staff member, instead of an opaque code in your report.

When to use it
you build a sales summary per cashier and want the employee's details next to their figures.
Watch out
it returns one person only; for the whole team in a single search, List Employees is the better fit.
Loyverse12

Get an Item

Action

In Make“Retrieves details of an item by the item ID.”

Everything Loyverse holds about one product, fetched by its item ID and ready to map into an alert, a sheet or another app.

When to use it
a previous step gives you an item ID and your message should show the product rather than a code.
Watch out
an item ID and a variant ID are different things; this module wants the item ID.
Loyverse13

Get a Payment Type

Action

In Make“Retrieves details of a payment type by the payment type ID.”

One payment method's details, looked up by its payment type ID, so a report can say how a sale was paid in words your accountant understands.

When to use it
you log sales in a sheet and the payment column should read as a method, not an identifier.
Watch out
when you need every method at once, List Payment Types does it in one step.
Loyverse14

Get a POS

Action

In Make“Retrieves a specific POS device.”

Your scenario learns which register it is dealing with, since the module returns the details of one specific POS device.

When to use it
you keep an equipment list outside Loyverse and want each device's record checked against the source.
Watch out
you must point at a particular device; if you do not know which one yet, List POS shows them all.
Loyverse15

Get a Receipt

Action

In Make“Retrieves details of a receipt by the receipt number.”

A single sale comes back in full, found by its receipt number, which helps when a customer calls about a purchase or a refund needs checking.

When to use it
a support ticket quotes a receipt and the scenario should attach the sale to it.
Watch out
unlike most lookups on this page, it asks for the receipt number, not an ID.
Loyverse16

Get a Store

Action

In Make“Retrieves details of a store by the store ID.”

One location's details, fetched by store ID, so alerts and reports carry the right shop name when you run several.

When to use it
a stock alert or a sales line should say which store it concerns before it reaches the team.
Watch out
Create a Receipt also needs a store ID, so this lookup is a good way to confirm you hold the right one first.
Loyverse17

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Whatever the ready-made modules leave out stays within reach: you call any endpoint of the Loyverse API, using the connection you already set up.

When to use it
you need an operation that none of the listed modules offers and do not want a second tool for it.
Watch out
you write the request yourself, so keep the Loyverse API documentation open while you build and test with Run once.
Loyverse18

Update a Customer

Action

In Make“Updates a customer by the customer ID.”

Corrections made elsewhere reach the till: the module edits a customer record by its customer ID, so cashiers see current details.

When to use it
customers change their details in your online account area and Loyverse should follow.
Watch out
in a scenario started by Watch Customers, your own update counts as an edit and can bring the same customer back on the next check.
Loyverse19

Update an Item

Action

In Make“Updates an Item by the item ID.”

Product changes made in your master sheet flow into Loyverse, edited by item ID, so the catalog never drifts from your reference file.

When to use it
your team manages product data outside the till and wants one place to make changes.
Watch out
if only one size or color changes, Update a Variant touches that version without affecting the rest of the item.
Loyverse20

Update a POS

Action

In Make“Updates a POS device.”

Device records in Loyverse stay aligned with your equipment list, because the scenario can edit a POS device's details for you.

When to use it
a register moves to another counter or store and the change is logged in your asset sheet first.
Watch out
locate the device with List POS or Get a POS before editing, so the change lands on the right till.
Loyverse21

Update a Variant

Action

In Make“Updates a variant of an item by the variant ID.”

One version of a product changes and the others stay as they are: the module edits a variant by its variant ID.

When to use it
only the large size of a product needs a correction and the rest of the range is fine.
Watch out
stock counts have their own module, Update Inventory Levels; use that one for quantities.
Loyverse22

Update Inventory Levels

Action

In Make“Updates inventory levels by the item variants ID.”

Your stock counts in Loyverse follow deliveries and transfers recorded elsewhere, adjusted by item variant ID rather than typed in at the counter.

When to use it
a delivery is received in your purchasing tool and the shelves in Loyverse should reflect it.
Watch out
it works on variants, not items, so have the variant IDs ready; and never feed it from Watch Updated Inventory Levels on the same stock.
Loyverse23

Upload an Image

Action

In Make“Uploads a new image of an item by the item ID.”

Products get their picture automatically: the module attaches a new image to the item you point at by its ID.

When to use it
your photographer drops product shots in a shared folder and each one should end up on the matching item.
Watch out
on the Make Free plan, files are capped at 5 MB, so heavy photos may need resizing first.
Loyverse24

List Customers

Search

In Make“Retrieves details of a list of customers.”

Your customer base comes out as a set of bundles your scenario can work through one by one, for an export, a check or a cleanup.

When to use it
before Create a Customer, to see whether a person is already registered.
Watch out
a search can return zero, one or many customers; each one flowing onward costs an operation in the modules after it.
Loyverse25

List Employees

Search

In Make“Retrieves details of a list of employees.”

The whole team comes out as a list, giving your payroll or scheduling tool the same starting point as the Back Office.

When to use it
you set up a new staff tool and want to seed it with everyone at once instead of creating people by hand.
Watch out
each employee is a separate bundle, so the next module runs once per person.
Loyverse26

List Inventory Levels

Search

In Make“Retrieves a list of inventory levels by the item variant IDs.”

Stock for the variants you name, gathered in one search, so a check or a report does not need a lookup per product.

When to use it
before promoting a product, you want to confirm there is enough on the shelves.
Watch out
it asks for item variant IDs, so keep them at hand before this step.
Loyverse27

List Items

Search

In Make“Retrieves details of a list of items.”

The catalog lands in your scenario, ready to copy into a spreadsheet, audit or feed to an online shop.

When to use it
you connect a new sales channel and it needs the full product range as a starting point.
Watch out
a large catalog produces many bundles, and every module after this one uses an operation for each of them.
Loyverse28

List Payment Types

Search

In Make“Retrieves details of a list of payment types.”

All the payment methods set up in Loyverse come back together, handy for building a mapping table in your bookkeeping.

When to use it
your accountant wants the list of methods the till accepts, kept in the same sheet as the sales.
Watch out
if you already hold one ID, Get a Payment Type returns just that method and keeps the scenario lighter.
Loyverse29

List POS

Search

In Make“Retrieves a list of POS devices.”

Every POS device on your account appears in one list, the quickest way to see what hardware Loyverse knows about.

When to use it
you need a device ID before Update a POS or Delete a POS, or you audit tills across stores.
Watch out
the list includes every device, so filter on the one you want before acting on it.
Loyverse30

List Receipts

Search

In Make“Retrieves details of a list of receipts.”

A batch of sales comes back at once, which suits catch-ups and reports better than a trigger that only sees new receipts.

When to use it
you connect your accounting tool for the first time and want past sales in it too.
Watch out
each receipt becomes a bundle; with a busy till, that can mean many operations further down the scenario.
Loyverse31

List Stores

Search

In Make“Retrieves details of a list of stores.”

All your locations in one search, so the scenario can repeat the same work for each shop without you naming them.

When to use it
you build a per-store report and want every location covered, including ones opened later.
Watch out
a single-shop account returns one bundle, which is fine; the scenario simply runs its next steps once.
Need help

Need help automating Loyverse with Make?

A person reads every message.

FAQ

Loyverse and Make: frequently asked questions

01Is the Loyverse Make integration free?
Yes. Loyverse is a standard app in Make, available from the Free plan, so you pay nothing on the Make side to start. The Free plan has limits: 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, Enterprise) lift those limits and count usage in credits, meaning operations, per month. You still need an active Loyverse account on the Loyverse side.
02What do you need to connect Loyverse to Make?
An active Loyverse account and an API access token. In the Loyverse Back Office, open Access Tokens, click Add access token, name it, add an expiration date only if you want one, save, and copy the token. In Make, add any Loyverse module, click Create a connection and paste that token. The connection is then shared by every Loyverse module in your scenarios. For the instant trigger, click Create a webhook before Create a connection.
03Do Loyverse triggers in Make work in real time?
Only one does. Watch Updated Inventory Levels is instant: Loyverse calls Make through a webhook as soon as a stock level changes. The six others, Watch Customers, Watch Employees, Watch Items, Watch Payment Types, Watch Receipts and Watch Stores, are scheduled, so Make checks Loyverse on the scenario's schedule. A new scenario runs every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval; paid plans go down to 1 minute.
04What if a Loyverse module is missing in Make?
Use Make an API Call. It calls any endpoint of the Loyverse API with the connection you already have, so you are not stuck with the 38 ready-made modules. You build the request yourself, which takes a little more care than filling in a standard module, so test it with Run once before switching the scenario on. The Make documentation for Loyverse lists no other limits, and it notes that its content is generated from the official Loyverse documentation.
05Should you use Make or n8n for Loyverse?
It depends on where your automations already live. On Make, Loyverse comes with 38 modules, seven triggers including one instant, and Make an API Call for the rest, all usable from the Free plan. Apps like Loyverse often have an n8n node too, so check what that node covers before you choose. If your team already runs scenarios in Make, adding Loyverse there keeps everything in one place; the comparison page linked above lays out the differences between the two tools.
Same platform

Other docs you might need on this stack.

Browse all integrations