- Home
- Resources
- Integrations
- Barcodes
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 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.
How do you set up Barcodes in Make?
- 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.
- 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.
- 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.
Build your first scenario with Barcodes
GoalWhen another app sends a new record, Make passes its details to Generate barcode.
- 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.
- 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.
- 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.
- 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.
- 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.
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.
Generate barcode
ActionThis 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.
Actions
ActionIn the docs onlyOpen 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.
Need help automating Barcodes with Make?
A person reads every message.