Resources · Make integration

Linkbreakers Make integrationAutomate Linkbreakers with Make.

Every QR code scan can start work in your other tools. The Linkbreakers Make integration offers 7 modules: 1 trigger, 5 actions and 1 search. This guide shows marketers how to link a workspace, build a first scenario and pick the right module.

Try the Linkbreakers integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Linkbreakers Make integration do for you?

The Linkbreakers Make integration connects your Linkbreakers workspace to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, acts or searches. Here, those bricks spot new QR code scans and create, update, read or delete your codes without opening the dashboard.

Scans that reach your team. Watch QR Code scanned picks up new scans, and Get a QR Code adds the full record of the code, so a trade show badge or a flyer turns into a line in the tool your sales team already reads.

Codes created from your catalog. When a product or an event appears in another app, Create a QR Code Entity produces its code, and Update a QR Code Entity keeps it in line when the campaign changes. List QR Codes and Delete a QR Code Entity handle the cleanup when an offer ends.

Visitors you can name. Identify a Visitor is the module to look at when a scan should be tied to a known person; the documentation says little about it, so test it before building on it.

What Make does not give here: there is no Make an API Call module for Linkbreakers, and the trigger is scheduled rather than instant, so scans arrive in batches at each check. The documentation itself warns that its content was generated from the vendor's docs and may contain mistakes. If you are weighing tools, the n8n vs Make comparison and the Make review set the context, and Make pricing explains how operations are counted.

Connect

How do you connect Linkbreakers to Make?

  1. 01

    Create a workspace token

    In Linkbreakers, open the workspace dashboard, click Workspace tokens, then Create Token. Give it a name you will recognize later, click Create and copy the key shown in the dialog.

  2. 02

    Open a connection in Make

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

  3. 03

    Paste the key and save

    Paste the key you copied from Linkbreakers, or follow the instructions Make shows on screen. Once saved, the module can read your workspace and you can fill its fields.

First scenario

Your first scenario with Linkbreakers and Make

GoalWhen someone scans one of your QR codes in Linkbreakers, Make fetches the full record of that code so the scan can be passed on with its details.

  1. 01

    Start a blank scenario

    On the Scenarios page, create a new scenario and click the + in the middle of the editor to add the first module.

  2. 02

    Add the scan trigger

    Search for Linkbreakers, pick Watch QR Code scanned and click Create a connection with the token you prepared. Fill the fields Make shows once the connection works.

  3. 03

    Fetch the scanned code

    Click the + on the right of the trigger, add Get a QR Code and map the code from the data the trigger returns, so Make reads the code that was just scanned. Run once shows you which item holds it.

  4. 04

    Test with Run once

    Scan one of your codes with your phone, then click Run once. Open the bubbles above each module to read the bundles they received: one bundle is one scan passing from module to module.

  5. 05

    Schedule and switch it on

    Click the clock on the first module to set Scheduling. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Then switch the scenario on.

Triggers

What starts a Linkbreakers scenario

1 module starts a scenario when something happens in Linkbreakers. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Linkbreakers as soon as it happens.

Linkbreakers1Watch QR Code scanned

Watch QR Code scanned

triggerIn the docs only

This trigger gives your scenario a starting point each time someone scans one of your Linkbreakers codes: every new scan arrives in Make as a bundle, one item handed to the next module.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, so a scan shows up at the next check rather than the moment it happens.
When to use it
codes printed on event badges or product packaging, where each scan should reach your CRM or alert a salesperson.
Watch out
the documentation lists this module without a description and its scheduled type is inferred from its name, so check it on a real scan with Run once before relying on it.
Modules

What the Linkbreakers modules do

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

Linkbreakers1

Create a QR Code Entity

ActionIn the docs only

New codes appear in your Linkbreakers workspace straight from a scenario, so you stop producing them one at a time in the dashboard.

When to use it
a new product, event or campaign lands in another app and needs its own code, built from the data mapped from that earlier module.
Watch out
every run creates one more code, so test with Run once on a single bundle before switching the scenario on.
Linkbreakers2

Delete a QR Code Entity

ActionIn the docs only

A clean workspace once an offer ends: this module removes a QR code you no longer need, without a trip to the dashboard.

When to use it
an item is archived in the app where you manage your catalog, and its code should go with it.
Watch out
run it on one test code with Run once first, and place List QR Codes or a filter before it so the right code is targeted.
Linkbreakers3

Get a QR Code

ActionIn the docs only

You get the current record of one code you already know, so the modules that follow work with fresh information instead of guesses.

When to use it
right after Watch QR Code scanned, to pull the full record of the code that was just scanned before sending it to another app.
Watch out
it reads a single code, so map the reference from the previous module rather than typing a value by hand.
Linkbreakers4

Identify a Visitor

ActionIn the docs only

Going by its name, this action ties a visitor who reached you through a Linkbreakers code to an identity, which is how anonymous scans start to mean something.

When to use it
someone scans, then fills in a form in another app; now Linkbreakers can learn who that visitor is.
Watch out
the documentation gives no description of this module, so read the fields Make shows once connected and test with Run once.
Linkbreakers5

List QR Codes

SearchIn the docs only

A view of the codes in your workspace, delivered one bundle per code, lets a single run act on many codes at once.

When to use it
before a bulk update, or to find the code that matches a campaign you are about to close.
Watch out
as a search, it can return zero, one or many bundles, and every module after it runs once per bundle, which adds operations to your plan.
Linkbreakers6

Update a QR Code Entity

ActionIn the docs only

Your existing code stays the same code while its details change, so there is no need to create a fresh one for every correction.

When to use it
a campaign changes in the app where you plan it, and the matching Linkbreakers code should follow without manual edits.
Watch out
find the right code first with List QR Codes or Get a QR Code and map it, otherwise the update may hit the wrong one.
Need help

Need help automating Linkbreakers with Make?

A person reads every message.

FAQ

Linkbreakers and Make: common questions

01Is the Linkbreakers Make integration free?
Yes, on the Make side. Linkbreakers is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid plans lower the interval to 1 minute and remove the cap on active scenarios, with usage counted in operations per month. You still need an active Linkbreakers account; its own pricing page covers the subscription.
02What do you need to connect Linkbreakers to Make?
An active Linkbreakers account and a workspace token. In Linkbreakers, open the workspace dashboard, go to Workspace tokens, click Create Token, name it, click Create and copy the key from the dialog. In Make, add a Linkbreakers module, click Create a connection, optionally name it, and paste the key. That single connection then serves all 7 Linkbreakers modules in every scenario. Keep the token somewhere safe: the key is displayed in the creation dialog, so copy it before you close that window.
03Does the Linkbreakers Make integration react to scans in real time?
No. The only trigger, Watch QR Code scanned, is listed as scheduled: Make checks Linkbreakers on the scenario's schedule and collects the scans that happened since the last check. A new scenario runs every 15 minutes by default, and the Free plan does not go below that. Paid plans can check every minute. Note that the documentation does not describe the module, and its type is inferred from its name, so confirm it in the editor.
04What if a Linkbreakers module is missing in Make?
It depends on what is missing. The integration has 7 modules and no Make an API Call module, so you cannot send a custom request to Linkbreakers from Make. Start by checking whether List QR Codes followed by Update a QR Code Entity covers the need. Otherwise, another app in the scenario may hold the data you are after, or the team behind this page can look at your case. The documentation also warns it may contain mistakes, so test before trusting a field.
05Should you use Make or n8n for Linkbreakers?
It depends on where your automations already live. On Make, Linkbreakers gives you 7 ready modules, a scheduled scan trigger and a connection built from a workspace token, which is enough to route scans and manage codes without code. Many apps also have an n8n node, so if your team already builds in n8n, check whether Linkbreakers has one there before moving. Neither choice is ranked here: pick the tool your team already maintains.
Same platform

Other docs you might need on this stack.

Browse all integrations