Resources · Make integration

CodeQR - Link and QR Analytics Make integrationAutomate CodeQR - Link and QR Analytics with Make.

What if every new campaign URL got its own CodeQR link and QR code without anyone copying and pasting? The CodeQR - Link and QR Analytics Make integration offers 8 modules: 1 trigger, 6 actions and 1 search. Below, you connect your account and build a first scenario step by step.

Try the CodeQR - Link and QR Analytics integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the CodeQR - Link and QR Analytics Make integration let you automate?

The CodeQR - Link and QR Analytics Make integration links your CodeQR account to Make, a no-code tool where you chain apps into a scenario, meaning the automation you build. Each brick of that scenario is a module: here, 1 trigger that starts it, 6 actions that create, fetch or delete links and QR codes, and 1 search.

A link and a code for every new entry. When a record shows up in another app, such as a new product or an event registration page, Create a Link adds the matching link to CodeQR and Create a QR Code produces the code that goes on the flyer. Nobody retypes a URL.

A tidy account when offers end. Search Link finds the links tied to a finished promotion, then Delete a Link or Delete a QR Code removes them, so the dashboard only shows what is still live.

Reacting to what CodeQR reports. Watch Webhook Events starts a scenario from the events CodeQR sends back, and the next module passes each one to the tool your team already reads.

Know the limit before you build: Make states that its documentation for this app is limited because little public information exists about CodeQR. Field names and behaviors appear in the editor once your connection is set, not on the doc page. When a task goes beyond the listed modules, Make an API Call reaches the rest of the API. The same app may also exist as an n8n node; the n8n vs Make comparison helps you pick, and the Make training covers the editor basics if this is your first scenario.

Connect

How do you connect CodeQR - Link and QR Analytics to Make?

  1. 01

    Add a CodeQR module

    In your scenario, click the +, search for CodeQR - Link and QR Analytics and pick any of its modules. A connection is your CodeQR account linked to Make once, then reused by every CodeQR module. Click Create a connection.

  2. 02

    Name it and authorize

    Give the connection a name if you like, which helps when several accounts are linked. Then either authorize Make on the CodeQR page that opens, or paste the key CodeQR gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. The module now shows your connection, and Make can list what it reads from your account. If the fields stay empty, the connection did not go through: open it again and repeat the authorization.

First scenario

Your first scenario with CodeQR - Link and QR Analytics

GoalWhen a new entry appears in another app, Make creates a CodeQR link for it, then a QR code.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where your new entries land, a spreadsheet or a form tool for instance, and choose the module that watches new items.

  2. 02

    Add Create a Link

    Click the + on the right of the first module, search CodeQR - Link and QR Analytics and pick Create a Link. Click Create a connection if you have not linked your account yet.

  3. 03

    Map the URL

    Fill the fields Make shows for the module and map the URL from the first module into them. Mapping means clicking a value from the previous bundle, one item passed between modules, instead of typing it.

  4. 04

    Chain Create a QR Code

    Add Create a QR Code after the link module and map the data it needs from the two modules before it. The scenario now turns each new entry into one link and one code.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario one time; open the bubble above each module to read the bundles it received and confirm the link and the code appear in CodeQR.

  6. 06

    Schedule and switch on

    Open the clock on the first module: a new scenario runs every 15 minutes by default, and 15 minutes is also the shortest gap on the Free plan. Set it, then switch the scenario on.

Triggers

What starts a CodeQR - Link and QR Analytics scenario

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

CodeQR - Link and QR Analytics1Watch Webhook Events

Watch Webhook Events

triggerIn the docs only

You get a scenario that starts on its own from the events CodeQR reports, each one passed to the next module as a bundle you can send. It is the only CodeQR module able to open a scenario.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default for a new scenario.
When to use it
your team wants to hear about CodeQR activity where it already works, without opening the CodeQR dashboard.
Watch out
Make's documentation does not describe this module, and its type here comes from its name only. Look at the badge on the module in the editor (a clock means scheduled, a lightning bolt means instant) before you rely on its timing.
Modules

Everything the CodeQR - Link and QR Analytics modules can do

CodeQR - Link and QR Analytics gives you 7 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

CodeQR - Link and QR Analytics2

Create a QR Code

ActionIn the docs only

Each run hands you a fresh QR code in CodeQR, built from the data the previous module passed along, ready for a flyer, a badge or a menu.

When to use it
every record in another app, such as a new event or a new location, needs a code of its own.
Watch out
the module creates a code on every bundle it receives, so two runs on the same entry give two codes. Test on one bundle with Run once first.
CodeQR - Link and QR Analytics4

Delete a QR Code

ActionIn the docs only

Retired codes leave your account without manual cleanup, which keeps the list of active QR codes short and readable for the whole team.

When to use it
an event is over or a venue closes, and the code created for it has no reason to stay.
Watch out
deleting the code in CodeQR does nothing to copies already printed, and Make's documentation does not say what a scan shows afterward, so check that before removing codes in use.
CodeQR - Link and QR Analytics5

Make an API Call

ActionIn the docs only

With this module, the rest of the CodeQR API opens up to your scenario, through the connection you already created and without any second login.

When to use it
none of the seven other modules covers what you need, and you know which API endpoint does.
Watch out
you write the request yourself. Since Make's documentation for this app is limited, rely on what CodeQR publishes about its own API before you build.
CodeQR - Link and QR Analytics6

Retrieve a QR Code

ActionIn the docs only

Fetching one existing QR code gives the next modules its details, so you can send it on, store it or attach it without looking it up by hand.

When to use it
you already know which code you want, for instance one created earlier in the same scenario, and a later step needs it.
Watch out
it returns a single code. To look through links by criteria, Search Link is the module to pick.
Need help

Need help automating CodeQR - Link and QR Analytics with Make?

A person reads every message.

FAQ

Questions about CodeQR - Link and QR Analytics and Make

01Is the CodeQR - Link and QR Analytics Make integration free?
Yes, the app is a standard app, so it is available from the Make Free plan. That plan keeps 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the gap to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Make counts usage in operations, one module run on one bundle. What CodeQR itself charges is not covered here.
02What do you need to connect CodeQR - Link and QR Analytics to Make?
A CodeQR account and a Make account. Make's documentation lists no prerequisite for this app and gives no official connection steps, so the generic flow applies: add a CodeQR module, click Create a connection, name it if you like, authorize Make on the CodeQR page or paste the key CodeQR provides, then click Save. The same connection then serves all 8 modules of the app. If authorization fails, open the connection again and repeat the step.
03Does the CodeQR - Link and QR Analytics trigger react instantly?
Not as listed. Watch Webhook Events is presented as a scheduled trigger, which means Make checks CodeQR on the scenario's schedule: every 15 minutes by default, and never more often than every 15 minutes on the Free plan. Paid plans go down to 1 minute. That type comes from the module name alone, since the documentation does not describe it, so check the badge on the module when you add it.
04What if a CodeQR - Link and QR Analytics module is missing in Make?
Use Make an API Call. It reaches any endpoint of the CodeQR API with the connection you already have, which covers what the other 7 modules do not. Expect to build the request yourself: Make says its documentation for this app is limited because little public information exists, so field names and behaviors are best read in the editor once the connection works, or in what CodeQR publishes about its API.
05Make or n8n for CodeQR - Link and QR Analytics?
It depends on the tool your team already runs. On Make, the app brings 8 modules, one trigger among them, plus Make an API Call for the rest, and it works from the Free plan. The same app may also be available as an n8n node; check that before deciding. Pick the tool where your other automations already live, so connections and monitoring stay in one place, and compare the two editors on a small test scenario.
Same platform

Other docs you might need on this stack.

Browse all integrations