Resources · Make integration

codeREADr Make integrationAutomate codeREADr with Make.

Keep your codeREADr barcode databases in sync without typing a single value by hand. The codeREADr Make integration gives you 9 modules: 7 actions and 2 searches. This guide shows what they do, how to link your account and how to build a first scenario.

Try the codeREADr integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the codeREADr Make integration do for you?

The codeREADr Make integration lets a Make scenario (the automation you build, a chain of modules) manage your codeREADr databases and the barcode values inside them. Each module is one brick of that chain: here, 7 actions that change data and 2 searches that read it. There is no trigger, so the scenario starts from another app or from a schedule.

A database that follows your catalog. When a product or ticket is created in another tool, Insert / Update a Barcode Value writes its code into the right codeREADr database, so the scanning team never works from a stale list.

A clean slate between two events. Once an event or a stock count is over, List Barcode Values of a Database lets you export what was stored, then Clear a Database empties it for the next round.

One database per project, created for you. When a new job starts in your project tool, Create a Database sets up its container, and Update a Database keeps its details aligned later on.

What Make does not do here: react on its own to a scan, since the app offers no trigger. For anything the 9 modules skip, Make an API Call reaches the rest of the codeREADr API with the same connection. The same app often exists as an n8n node too; the n8n vs Make comparison helps you pick, and the Make training covers the editor from zero. If a run fails, start with Make troubleshooting.

Connect

How do you connect codeREADr to Make?

  1. 01

    Copy your API key

    Log in to codeREADr, open the Settings section, then the API (or API Keys) tab. Copy the key shown on screen and keep it at hand for the next step.

  2. 02

    Add a codeREADr module

    In your Make scenario, click the + and search for codeREADr, pick a module, then click Create a connection. A connection is your codeREADr account linked to Make once, reused by every module of the app.

  3. 03

    Paste the key and save

    Give the link a clear label in Connection name if you like, it is optional. Paste the API key you copied, or follow the on-screen instructions, and save. Make can now read and write your databases.

First scenario

Your first scenario with the codeREADr Make integration

GoalWhen a new item shows up in another app, Make saves its barcode value in a codeREADr database.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to place the first module. Pick the app where new items appear, such as your product sheet or ticketing tool.

  2. 02

    Set up the starting module

    Connect that app and fill its fields. Once the connection exists, Make lists the sheets or objects it can read, so you choose from a menu instead of typing a path.

  3. 03

    Add the codeREADr action

    Click the + on the right, search for codeREADr and choose Insert / Update a Barcode Value. Link your account, pick the database, then map the code from the first module.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open each module to read the bundles it received (a bundle is one item passed along) and confirm the value landed in codeREADr.

  5. 05

    Schedule and switch on

    Open the clock on the first module: a new scenario checks every 15 minutes by default. Keep that or adjust it, then switch the scenario on so it keeps working without you.

Modules

What the codeREADr modules do

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

codeREADr1

Clear a Database

ActionIn the docs only

Empties a codeREADr database of its barcode values while the database itself stays in place, ready for the next batch.

When to use it
an event or a stock count is over and the codes are exported. Now the next round can start from nothing.
Watch out
treat it as final, since Make offers no undo, and run List Barcode Values of a Database first if you want a copy.
codeREADr2

Create a Database

ActionIn the docs only

Sets up a brand new database in your codeREADr account, so each project gets its own container of barcode values without a trip to the codeREADr interface.

When to use it
a new client, site or event is created in your CRM or project tool and needs its own list of valid codes.
Watch out
run it once per project, or a scenario that repeats will leave duplicates behind.
codeREADr3

Delete a Barcode Value

ActionIn the docs only

Removes one single barcode value from a database, leaving every other code where it was. It is the precise tool, compared with clearing the whole database.

When to use it
a ticket is refunded or a product is discontinued in your source app, and that code must stop being recognized.
Watch out
the removal cannot be reversed from Make, so double check the value you map before switching the scenario on.
codeREADr4

Delete a Database

ActionIn the docs only

Removes an entire codeREADr database, container included, which is the right move when a project is truly finished and its list has no further use.

When to use it
a job is archived in your project tool and you want codeREADr to stay as tidy as your other systems.
Watch out
nothing brings it back; if you only want to reuse the database, Clear a Database is the safer choice.
codeREADr5

Insert / Update a Barcode Value

ActionIn the docs only

Writes a barcode value into a database. As the name suggests, it adds the value when it is new and refreshes it when it is already there. This is the module most scenarios with this app are built around.

When to use it
every time an item is created or edited in your catalog, spreadsheet or ticketing app, so scanners check against current data.
Watch out
map the code from the previous module rather than typing it, or every run will write the same value.
codeREADr6

List Barcode Values of a Database

SearchIn the docs only

Reads the barcode values stored in one database and hands them to the next module, one bundle per value. Being a search, it may return zero, one or many results.

When to use it
before clearing a database. Send the codes to a spreadsheet first and you keep a record.
Watch out
every value counts. Each one runs the modules that follow, and each module run is one operation on your Make plan.
codeREADr7

List Databases

SearchIn the docs only

Returns the databases that exist in your codeREADr account, so a scenario can find the one it needs instead of relying on a hard-coded choice.

When to use it
before an insert or a cleanup, to spot the database that matches a project name coming from another app.
Watch out
as a search it can hand back several bundles; add a filter so only the matching database moves on to the next step.
codeREADr8

Make an API Call

ActionIn the docs only

Opens the rest of the codeREADr API to your scenario, using the connection you already created, for the cases the listed modules leave aside.

When to use it
you need a codeREADr feature that none of the other 8 modules covers, and the API documentation describes the endpoint.
Watch out
here you shape the request yourself, so keep the codeREADr API reference open while you fill it in.
codeREADr9

Update a Database

ActionIn the docs only

Changes the details of a database that already exists, so its settings follow the project it belongs to without recreating it.

When to use it
a project is renamed or reorganized in your source app and the matching codeREADr database should reflect it.
Watch out
pair it with List Databases to target the right one, since updating the wrong database is easy when names look alike.
Need help

Need help automating codeREADr with Make?

A person reads every message.

FAQ

Common questions about codeREADr and Make

01Is the codeREADr Make integration free?
Yes, on the Make side: codeREADr is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs no more often than every 15 minutes, stops an execution after 5 minutes and handles files up to 5 MB, with 512 MB of data transfer. Paid plans lower the interval to 1 minute and lift the active scenario cap. On the codeREADr side, the documentation says a paid codeREADr plan is required for production use, so check your subscription there.
02What does it take to connect codeREADr to Make?
An active codeREADr account and its API key. In codeREADr, open Settings, then the API or API Keys tab, and copy the key. In Make, add any codeREADr module, click Create a connection, optionally name it, and paste the key. That single connection then serves all 9 modules. For real production use, the codeREADr documentation also requires a paid codeREADr plan, which is worth confirming with codeREADr before you build anything.
03Does the codeREADr integration react in real time?
No, because codeREADr has no trigger module in Make, so it cannot start a scenario by itself. You begin with another app instead: a trigger from your catalog, spreadsheet or ticketing tool, then a codeREADr action. You can also start the scenario on a schedule, which is every 15 minutes by default for a new scenario and can go down to 1 minute on a paid plan. In both cases, the codeREADr modules run as soon as the scenario reaches them.
04What if a codeREADr module is missing in Make?
It depends on the task, but Make an API Call is usually the answer. That module reaches any endpoint of the codeREADr API while reusing the connection you already set up, so you are not limited to the 7 actions and 2 searches listed. Keep in mind that the Make documentation for this app notes it was generated with AI from the official codeREADr docs, so verify important details against codeREADr itself before relying on them.
05Make or n8n for codeREADr, which one fits?
It depends on the tool your team already runs. On Make, codeREADr offers 9 ready modules, including Make an API Call to cover the rest of its API, and it works from the Free plan. The same app often exists as an n8n node as well. If your other automations already live in one of the two tools, keeping codeREADr there is the simplest path, and the comparison page on this site walks through the other criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations