Resources · Make integration

Barcodes Make integrationAutomate Barcodes with Make.

Need a barcode inside an automation without opening another tool? The Barcodes Make integration is a built-in app with 2 action modules and nothing to connect. This page explains each module and walks you through a first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Barcodes Make integration do for you?

Barcodes is one of Make's built-in apps: it lives inside Make itself, so there is no outside account to link. You drop its modules into a scenario, the automation you build in Make as a chain of bricks, and it works on the data the previous brick passes along.

A barcode step inside a bigger flow. Barcodes has no trigger, so it never starts a scenario on its own. Another app, or the Make schedule, starts the run; Generate barcode then does its job on the data it receives, and the next module picks up the result.

An order or a record that needs a code. A typical pattern: a new row or record appears in the app you already use, and the scenario hands its details to Generate barcode. If your data sits in a base, the Airtable Make integration page shows how that side is set up.

A second module to explore. The Actions module has no official description in the documentation. Open it in the editor to see what it offers before you plan around it.

What Make does not document for this app: the fields, the output formats and any limit beyond the fact that no connection is required. When a detail matters, check it with Run once. Weighing another tool? The n8n vs Make comparison sets out the criteria, and Make training covers the editor basics.

Connect

How do you set up Barcodes in Make?

  1. 01

    Add the module

    Open your scenario, click the + where the next brick should go, type Barcodes in the search box and pick the module you need. Make places it in the chain right away.

  2. 02

    Skip the connection

    Most apps ask you to click Create a connection to link your account. Barcodes does not: the documentation states that no connection is needed, so you go straight to the module settings.

  3. 03

    Fill the fields

    Complete the settings the module shows. To reuse data from an earlier module, click a field and map a value from the list Make displays, instead of typing it by hand.

First scenario

Build your first scenario with Barcodes

GoalWhen another app sends a new record, Make passes its details to Generate barcode.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the first module from the app that holds your records, such as a spreadsheet or a store.

  2. 02

    Add Generate barcode

    Click the + to the right of that first module, search Barcodes and choose Generate barcode. No connection window appears, so you land directly on its settings.

  3. 03

    Map the data

    In the Generate barcode fields, map the values coming from the first module. Each bundle, meaning one item passed along such as one row, gets its own run of the module.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open the bubble above each module to read the bundles it received and check what Generate barcode returned.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run counts as one operation on your Make plan.

Modules

What each Barcodes module does

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

Barcodes1

Generate barcode

Action

This action gives your scenario a barcode built from the data you map into it, so a later module can store or send the result. It is the module whose name says exactly what it produces, which makes it the natural first pick.

When to use it
a record arrives from another app and needs a code attached before the next step.
Watch out
the documentation lists no fields or formats, so run it once and inspect the output bundle before you rely on it.
Barcodes2

Actions

ActionIn the docs only

Open this second action when Generate barcode does not cover what you need: it is the other entry point Make offers for this app. The documentation gives it no description, so its options show up only inside the editor.

When to use it
after checking its settings in a test scenario, when they match your case better than Generate barcode.
Watch out
do not guess what it does from the name; test it with Run once first.
Need help

Need help automating Barcodes with Make?

A person reads every message.

FAQ

Barcodes and Make: common questions

01Is the Barcodes Make integration free?
Yes. Barcodes is a standard built-in app, available from the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Usage is counted in operations, one per module run on one bundle, so each Generate barcode run uses one.
02What do you need to connect Barcodes to Make?
Nothing beyond a Make account. According to the documentation, Barcodes works without any connection, so there is no login, no key and no authorization window. You add the module from the editor, fill its fields and move on. That also means there is no account of your own to manage or renew later. If a module asks for data, it comes from the modules placed before it in the scenario, mapped field by field.
03Does Barcodes have a trigger in Make?
No. Both Barcodes modules are actions, so the app cannot start a scenario by itself. Something else has to start the run. Either you put a trigger from another app first, for example a new row in a spreadsheet, or you rely on the schedule of the first module, which a new scenario sets to every 15 minutes by default. Barcodes then runs as a step in the middle of the chain, on each bundle that reaches it.
04What if a Barcodes module is missing or too limited?
It depends on what you need. Barcodes has only 2 modules and no Make an API Call module, so you cannot send a custom request through this app. If Generate barcode and Actions do not cover your case, look for another app in Make that does the job, or ask for help: the team builds scenarios like this one for clients. Before deciding, test both modules with Run once, since the documentation does not describe their fields.
05Should you use Make or n8n for Barcodes?
It depends on your criteria rather than on a winner. On Make, Barcodes is a built-in app with 2 action modules and no connection, which keeps setup short for a scenario that already runs on Make. Many apps also have an n8n node; check whether this one does before comparing. Then weigh what matters to your team: the tool you already use, the other apps in the flow and who will maintain it. The comparison page linked above lists those criteria in detail.