Resources · Make integration

Biyo POS Make integrationAutomate Biyo POS with Make.

Can Make keep your Biyo POS catalog, customers and reports in step with the rest of your tools? The Biyo POS Make integration gives you 48 modules: 37 actions and 11 searches. This guide connects your account and walks you through a first working scenario.

Try the Biyo POS integration on MakeSee the 48 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Biyo POS Make integration do?

The Biyo POS Make integration lets Make read and write the data behind your registers: products, categories, customers, discounts, tax rates, stores, terminals, printers and orders. It can also run five of the Biyo POS summary reports, so their figures can travel to another tool without anyone exporting them by hand.

Customers who never have to be typed in twice. A person signs up in another app you already use, and Create a new Customer adds them to Biyo POS. Update a Customer then keeps the record current when their details change elsewhere.

Reports that land where the team reads them. Run a Sales Summary report or Run an Item Sales report pulls the figures, and the next module in the scenario sends them on to a spreadsheet or a chat channel of your choice.

A catalog that follows your supplier list. Create a new Product and Create a new Category turn rows from another source into items the register can sell, while List All Products helps you check what already exists first.

What the integration does not do: it has no trigger, so Biyo POS cannot start a scenario by itself. You start one on a schedule or from another app. Make's help page for this app also warns that it was AI-generated from the Biyo POS documentation, so verify anything important with Biyo POS directly.

New to the editor? The Make training covers the basics, and Make pricing explains how operations count. If you are weighing tools, read n8n vs Make.

Connect

How do you connect Biyo POS to Make?

  1. 01

    Generate an API key in Biyo POS

    Open your dashboard at yourstorename.biyo.co/dashboard, click the profile icon at the top right and pick API Keys. Click Generate, type a name for the key, click Save changes, then copy the value shown in the Key column.

  2. 02

    Add a Biyo POS module in Make

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

  3. 03

    Paste the key and save

    Paste the API key you copied and follow the on-screen instructions to finish. Once the connection exists, Make can list the Biyo POS objects it reads, so you pick them from a menu instead of typing IDs from memory.

First scenario

Build your first scenario: sign-ups become Biyo POS customers

GoalWhen someone signs up in another app you use, Make creates the matching customer in Biyo POS.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the + in the middle. A scenario is the automation you build, one module (one brick) after another.

  2. 02

    Start from the app that collects sign-ups

    Biyo POS has no trigger, so the first module comes from another app: search it by name, pick its trigger and connect your account. That module decides when the scenario starts.

  3. 03

    Add Create a new Customer

    Click the + on the right of the first module, search Biyo POS and choose Create a new Customer. Connect with your API key, then map the sign-up data into the fields Make displays.

  4. 04

    Test with Run once

    Click Run once and send one test sign-up. Open the bundle each module received (a bundle is one item passing between modules) and check that the customer now shows up in Biyo POS.

  5. 05

    Schedule it and switch it on

    If the first module is a scheduled trigger, set its interval: every 15 minutes by default, and 15 minutes is also the shortest gap on the Free plan. Then switch the scenario on.

Modules

What can Biyo POS do in Make?

Biyo POS gives you 48 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Biyo POS1

Create a new Category

ActionIn the docs only

Adds a category to your Biyo POS catalog, giving new products a section to sit in before anyone rings them up at the counter.

When to use it
a new product line shows up in a supplier file and needs its own place on the register.
Watch out
running the scenario twice creates two identical categories, so check with List All Categories first.
Biyo POS2

Create a new Customer

ActionIn the docs only

Turns a person from another tool into a customer record in Biyo POS, so staff find them at checkout without typing anything in.

When to use it
someone signs up for your loyalty list in a form or online shop, and you want them known at the till.
Watch out
if the same person may arrive twice, check with List All Customers upstream, or you risk two records for one customer.
Biyo POS3

Create a new Customer Group

ActionIn the docs only

Sets up a customer group in Biyo POS, a named bucket you can later fill with customers who share something, such as wholesale buyers or staff.

When to use it
a new segment appears in your CRM and the register should recognize it too.
Watch out
groups are usually created once; keep this module in a separate scenario from the one that adds customers.
Biyo POS4

Create a new Discount

ActionIn the docs only

Publishes a discount in Biyo POS from data prepared somewhere else, so a promotion planned in a spreadsheet reaches the registers without manual re-entry.

When to use it
marketing approves an offer in its planning sheet and the cashiers need it ready to apply.
Watch out
a discount goes live on real sales; test with Run once on a clearly named test discount before mapping live values.
Biyo POS5

Create a new Modifier

ActionIn the docs only

Adds a modifier in Biyo POS, the kind of option a cashier attaches to an item at the moment of sale, like an extra shot or a size change.

When to use it
your menu source gains a new add-on and every register should offer it the same way.
Watch out
modifiers pile up quickly; List All Modifiers helps you spot one that already covers the need.
Biyo POS6

Create a new Printer

ActionIn the docs only

Registers a printer in Biyo POS from a scenario, useful when printer setup follows a checklist kept in another tool rather than being done by hand.

When to use it
you open a new location and roll out its receipt and kitchen printers from a prepared list.
Watch out
a second run creates a second printer record; check List All Printers first if the scenario might repeat.
Biyo POS7

Create a new Product

ActionIn the docs only

Puts a new sellable item in the Biyo POS catalog, taking its details from whichever tool holds your product list today.

When to use it
a buyer adds a row to the supplier sheet and the item must be scannable at checkout.
Watch out
map a category that already exists, or create it earlier in the flow with Create a new Category, otherwise the product lands unsorted.
Biyo POS8

Create a new Store

ActionIn the docs only

Opens a store record in Biyo POS, the container that terminals, printers and sales reports later attach to.

When to use it
a new branch is approved in your project tool and its setup should start from that single event.
Watch out
this is rarely repeated, so run it with Run once rather than leaving it on a schedule.
Biyo POS9

Create a new Tax Rate

ActionIn the docs only

Records a tax rate in Biyo POS so products can be charged correctly, with the rate defined once and reused across the catalog.

When to use it
your accountant publishes a new rate in a shared sheet and the registers have to follow.
Watch out
a wrong rate affects every sale that uses it; have someone confirm the figure in Biyo POS after the first run.
Biyo POS10

Create a new Terminal

ActionIn the docs only

Declares a new terminal in Biyo POS, meaning another register or device the team can sell from inside a store.

When to use it
extra checkout points are added for a busy season and the setup is tracked in a planning tool.
Watch out
pick the right store for the terminal; List All Stores gives you the choices if you are unsure.
Biyo POS11

List All Categories

SearchIn the docs only

Returns every category in your Biyo POS catalog, one bundle per category, so the rest of the scenario can compare, copy or tidy them.

When to use it
before creating a category, to check whether one with the same name is already there.
Watch out
each returned category feeds the next modules separately, and every module run on each bundle counts as one operation on your plan.
Biyo POS12

List All Customer Groups

SearchIn the docs only

Gives you all customer groups defined in Biyo POS, handy for picking the right group without hunting through the dashboard.

When to use it
you mirror your segments into another tool and need the up-to-date list of groups as a starting point.
Watch out
zero groups is a valid answer; the modules after it simply do not run in that case.
Biyo POS13

List All Customers

SearchIn the docs only

Pulls your Biyo POS customer base into the scenario, one bundle per person, ready to be copied into a CRM or a mailing tool.

When to use it
a first bulk copy of customers into another system, or a duplicate check before creating one.
Watch out
a large customer base means many bundles and many operations downstream, so test with Run once before scheduling it.
Biyo POS14

List All Discounts

SearchIn the docs only

Shows every discount set up in Biyo POS, so you can review promotions from a spreadsheet instead of clicking through each one.

When to use it
building an overview of active offers for the team that plans promotions.
Watch out
the list returns discounts as they are stored; every discount becomes its own bundle, so a long list means as many runs of the modules that follow.
Biyo POS15

List All Modifiers

SearchIn the docs only

Collects all the modifiers that cashiers can add to items, so you can audit options across the menu from one place.

When to use it
checking that the same add-on is not defined twice before a menu update goes out.
Watch out
every modifier arrives as its own bundle; plan for that before sending them one by one to a chat channel.
Biyo POS16

List All Orders

SearchIn the docs only

Brings the orders recorded in Biyo POS into Make, each order as a separate bundle you can send to accounting, a sheet or a dashboard.

When to use it
feeding sales into a bookkeeping tool that has no direct link with your registers.
Watch out
without a trigger, a scheduled run may pick up orders it already sent; keep a record of what was copied to avoid duplicates.
Biyo POS17

List All Printers

SearchIn the docs only

Returns the printers declared in Biyo POS, a quick way to see which devices each store relies on without logging in.

When to use it
keeping an equipment inventory in a sheet that your operations team already maintains.
Watch out
this reflects what is declared in Biyo POS, not whether a printer is actually switched on in the shop.
Biyo POS18

List All Products

SearchIn the docs only

Exports your Biyo POS catalog into the scenario, one bundle per product, ready to sync with an online store or a pricing sheet.

When to use it
checking whether an item exists before Create a new Product, or mirroring the catalog elsewhere.
Watch out
a big catalog multiplies operations in every later module, so test on Run once and read the bundles before scheduling.
Biyo POS19

List All Stores

SearchIn the docs only

Lists the stores in your Biyo POS account, which is the starting point for any scenario that repeats the same task per location.

When to use it
running a report or a check for each store in turn, fed by this list.
Watch out
each store triggers its own run of the following modules, so a report per store costs one operation per store.
Biyo POS20

List All Tax Rates

SearchIn the docs only

Retrieves every tax rate configured in Biyo POS, so you can compare them with what your accountant expects without opening the dashboard.

When to use it
after a rate change, to confirm the registers carry the new figure and no leftover.
Watch out
the module reads rates, it does not tell you which products use them; pair it with List All Products for that.
Biyo POS21

List All Terminals

SearchIn the docs only

Returns all terminals registered in Biyo POS, the registers and devices your staff sell from, one bundle each.

When to use it
keeping a hardware list current for support, or finding a terminal before updating it.
Watch out
every terminal passes through the next modules as its own bundle, and each of those runs counts as an operation.
Biyo POS22

Make an API Call

ActionIn the docs only

Reaches any endpoint of the Biyo POS API from your scenario, with the same connection as the other modules, when none of the ready-made ones fits.

When to use it
you need something the 48 listed modules do not offer, as described in the Biyo POS API documentation.
Watch out
you write the request yourself, so read the Biyo POS API documentation for the exact path before testing with Run once.
Biyo POS23

Retrieve a Category

ActionIn the docs only

Fetches one category from Biyo POS by its identifier, so later modules can use its details without listing the whole catalog.

When to use it
a product arrives with a category reference and you want the category's name for a report.
Watch out
you need the category ID; if you only know the name, start with List All Categories.
Biyo POS24

Retrieve a Customer

ActionIn the docs only

Loads a single customer's record from Biyo POS, giving the next module fresh details for exactly that person.

When to use it
an order mentions a customer and you want their full profile before sending a thank-you message from another app.
Watch out
this module expects a customer ID, which usually comes from an order or from List All Customers earlier in the flow.
Biyo POS25

Retrieve a Customer Group

ActionIn the docs only

Reads one customer group from Biyo POS, which is useful when a record only carries the group's ID and you need to know what it stands for.

When to use it
labeling customers by segment in a spreadsheet that people outside the till can read.
Watch out
calling it once per customer costs an operation each time; if many customers share few groups, list the groups once instead.
Biyo POS26

Retrieve a Discount

ActionIn the docs only

Gets the details of one discount from Biyo POS, so a scenario can show or check an offer without pulling every promotion.

When to use it
before changing a discount with Update a Discount, to see what it currently holds.
Watch out
the discount ID has to come from somewhere; List All Discounts is the usual source when you start from a name.
Biyo POS27

Retrieve a Modifier

ActionIn the docs only

Pulls up one modifier from Biyo POS, the item option a cashier adds at the till, with its stored details.

When to use it
double-checking an add-on before a menu change goes out, or copying it into a menu tool.
Watch out
the module needs the modifier ID; List All Modifiers gives it to you when you only know the option by name.
Biyo POS28

Retrieve a Printer

ActionIn the docs only

Returns a single printer's record from Biyo POS, the useful half of any support scenario about a specific device.

When to use it
a store reports a printing issue in a helpdesk tool and the ticket should carry the printer's details.
Watch out
the data comes from Biyo POS settings, so it cannot confirm that the device itself is online.
Biyo POS29

Retrieve a Product

ActionIn the docs only

Looks up one product in Biyo POS and hands its details to the rest of the scenario, from price to category as stored in the catalog.

When to use it
an order line references a product and you want its full record for a stock or margin sheet.
Watch out
Retrieve needs the product ID; for a name or a code you only have, search with List All Products first.
Biyo POS30

Retrieve a Store

ActionIn the docs only

Reads the record of one store in Biyo POS, so messages and reports can name the right location instead of an ID.

When to use it
sending a report to a manager and addressing it with the store's details.
Watch out
if the same store comes up for every bundle, retrieve it once at the start rather than on each pass.
Biyo POS31

Retrieve a TaxRate

ActionIn the docs only

Fetches one tax rate from Biyo POS by its ID, so a scenario can show which rate a product carries in plain terms.

When to use it
preparing a check sheet where each product sits next to the rate it is taxed at.
Watch out
the module name is written TaxRate in one word in Make; search for both spellings if it does not show up.
Biyo POS32

Retrieve a Terminal

ActionIn the docs only

Gets the details of one terminal from Biyo POS, so an alert or ticket can point to the exact register involved.

When to use it
a shift summary or an order mentions a terminal and your team needs to know which device it was.
Watch out
map the terminal ID from an earlier module such as List All Terminals instead of typing it by hand.
Biyo POS33

Retrieve an Order

ActionIn the docs only

Brings back one order from Biyo POS in full, useful when a refund, a claim or an invoice needs the exact sale.

When to use it
a customer quotes an order in a support ticket and the agent should see it without opening the register.
Watch out
the module needs the order ID; List All Orders is the way in when you start from something else.
Biyo POS34

Run a Modifier Sales Summary report

ActionIn the docs only

Produces the Biyo POS summary of how add-ons and item options sold, so you can see which extras customers really pick.

When to use it
after a menu change, to share with the team how the new options performed.
Watch out
read the bundle after Run once to see which figures come back before mapping them into another app.
Biyo POS35

Run a Sales Summary report

ActionIn the docs only

Generates the overall sales summary from Biyo POS and passes its figures to the next module, whether that is a sheet, an email or a chat message.

When to use it
sending sales totals to managers who never open the POS dashboard, from a scenario started on its schedule.
Watch out
run it with Run once first and read the bundle, to know exactly which figures the report contains before mapping them.
Biyo POS36

Run a Shifts Summary

ActionIn the docs only

Pulls the Biyo POS summary of staff shifts, so hours and register activity can reach payroll or a scheduling tool.

When to use it
closing a shift and sending its summary to the person who reconciles the cash drawer.
Watch out
check the bundle with Run once first, so the columns you map in the payroll sheet match what the summary really returns.
Biyo POS37

Run a Voided Items Summary report

ActionIn the docs only

Returns the summary of voided items from Biyo POS, the lines that were rung up and then cancelled at the till.

When to use it
flagging unusual cancellations to a store manager, for training or loss prevention.
Watch out
a high number is a signal, not proof of a problem; share it with context rather than as an automatic alert.
Biyo POS38

Run an Item Sales report

ActionIn the docs only

Breaks sales down by item in Biyo POS, which tells buyers what actually moves off the shelves and what sits there.

When to use it
feeding a reorder sheet where the purchasing team decides what to restock.
Watch out
the report can return many lines; each one going through later modules counts as an operation on your plan.
Biyo POS39

Update a Category

ActionIn the docs only

Changes an existing category in Biyo POS, so a rename or reorganization done in your planning tool shows up on the registers.

When to use it
the team renames a product section in the catalog sheet and wants the till to match.
Watch out
the update targets a category ID; map it from List All Categories or Retrieve a Category, never retype it.
Biyo POS40

Update a Customer

ActionIn the docs only

Edits a customer already stored in Biyo POS, keeping contact details at the counter aligned with the tool where customers update them.

When to use it
a client changes details in your online account area and the register should show the new version.
Watch out
fields left empty in the mapping may overwrite stored values; test on one customer with Run once before switching the scenario on.
Biyo POS41

Update a Customer Group

ActionIn the docs only

Edits a customer group that already exists in Biyo POS, so a loyalty tier renamed in your own files reads the same at the register.

When to use it
a form or a spreadsheet row says a tier has been renamed, and you want the register to show the new name without anyone editing it by hand.
Watch out
the module needs to know which group to touch, so place List All Customer Groups before it and map the right one.
Biyo POS42

Update a Discount

ActionIn the docs only

Rewrites one discount that already exists in Biyo POS, so you change a live promotion instead of stacking a second one next to it.

When to use it
your marketing team approves a new version of an offer in another tool, and the scenario pushes that decision to the store.
Watch out
an edit replaces what the discount said before; click Run once on a test discount and read the bundle before switching the scenario on.
Biyo POS43

Update a Modifier

ActionIn the docs only

Modifiers are the extras a cashier adds to an item, like a topping or a size. This module edits one of them, so the option offered at checkout matches your current menu.

When to use it
the kitchen changes a recipe in its own sheet and you want the matching modifier corrected in Biyo POS from that same event.
Watch out
modifier names often look alike; pull the exact record with Retrieve a Modifier or List All Modifiers first, then map it here.
Biyo POS44

Update a Printer

ActionIn the docs only

Changes what Biyo POS stores for one printer already declared in your account, so a receipt or kitchen printer record stays right without a trip to the dashboard.

When to use it
an equipment request in your ticketing tool is closed and the printer's record should reflect the swap the technician made.
Watch out
this edits a record in Biyo POS, it does not configure the device itself; test with Run once before the scenario goes live.
Biyo POS45

Update a Product

ActionIn the docs only

Edits one product already in the Biyo POS catalog, taking the correction from wherever the truth lives: a supplier file, a spreadsheet or a form.

When to use it
a supplier sends a new product description and you want the catalog fixed as soon as the file lands, with no copying between screens.
Watch out
the scenario must point at the right product, so look it up with List All Products or Retrieve a Product before this module.
Biyo POS46

Update a Store

ActionIn the docs only

Multi-site owners use this one to change the details of a store already set up in Biyo POS, from a single source instead of editing each location by hand.

When to use it
a location record changes in your CRM or your internal directory, and the matching Biyo POS store should say the same thing.
Watch out
a mapping error updates the wrong shop; get the store from List All Stores and check the bundle after Run once.
Biyo POS47

Update a Tax Rate

ActionIn the docs only

When a tax rule changes, this module edits the existing tax rate record in Biyo POS, so the rate stored in Biyo POS carries the new value instead of an outdated one.

When to use it
your accountant validates a new rate in a shared sheet and the scenario applies it to the point of sale from that approval.
Watch out
tax touches every sale that uses the rate, so try it on a test record with Run once and ask whoever handles your books to confirm.
Biyo POS48

Update a Terminal

ActionIn the docs only

A terminal is a register station in Biyo POS. This module edits one of them, which is handy when a device changes role or moves to another counter.

When to use it
your store manager logs a change of station in a form, and the scenario updates the terminal record so reports stay easy to read.
Watch out
pick the terminal with List All Terminals or Retrieve a Terminal first; guessing the record from its name alone often picks the wrong one.
Need help

Need help automating Biyo POS with Make?

A person reads every message.

FAQ

Biyo POS and Make: common questions

01Is the Biyo POS Make integration free?
Yes, on the Make side. Biyo POS is a standard app, available from the Free plan. That plan allows 2 active scenarios, a shortest interval of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. You still need an active Biyo POS account and its own subscription, which is priced by Biyo POS, not by Make.
02What do you need to connect Biyo POS to Make?
An active Biyo POS account and an API key. In your Biyo dashboard, open the profile icon at the top right, choose API Keys, click Generate, name the key and click Save changes. Copy the value from the Key column. In Make, add any Biyo POS module, click Create a connection, optionally name it, and paste the key. That one connection then serves all the Biyo POS modules in every scenario you build.
03Can a Biyo POS scenario start automatically when a sale happens?
Not directly. Biyo POS has no trigger module in Make, so it cannot start a scenario by itself. You have two options. Put a scheduled start on the first module: a new scenario runs every 15 minutes by default, and 15 minutes is the minimum on the Free plan, 1 minute on paid plans. Or open the scenario with a trigger from another app, then let Biyo POS modules such as List All Orders or Create a new Customer do the work.
04What if the Biyo POS module you need is missing in Make?
Use Make an API Call. It is part of the 48 Biyo POS modules and lets the scenario reach any endpoint of the Biyo POS API with the same connection, which covers what the listed modules leave out. You write the request yourself, so check the Biyo POS API documentation first. Make's help page for this app was AI-generated from Biyo POS documentation, so confirm important details with Biyo POS directly.
05Make or n8n for Biyo POS?
It depends on what you need to cover. On Make, Biyo POS comes with 48 ready-made modules, 37 actions and 11 searches, plus Make an API Call for the rest, all usable from the Free plan. Many apps also have an n8n node, so check whether one exists for Biyo POS and what it covers before deciding. Compare the modules you actually need and the way each tool counts usage, rather than picking on reputation.
Same platform

Other docs you might need on this stack.

Browse all integrations