Resources · Make integration

Uniqode Make integrationAutomate Uniqode with Make.

Can your QR codes create and update themselves while you do something else? The Uniqode Make integration gives you 9 modules: 3 triggers and 6 actions. This guide is for teams already on Uniqode who want to connect the account, build a first scenario and pick the right module.

Try the Uniqode integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Uniqode Make integration do for you?

The Uniqode Make integration links your Uniqode account to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick such as a trigger or an action. Once connected, Make can watch Uniqode for new items and create, fetch or change QR codes for you, without anyone copying data by hand.

A personal QR code for every form answer. Watch Form Response starts the scenario when someone fills in a Uniqode form, and Create a Dynamic QR Code produces a code for that person. An events team can use this to hand out a unique code per registration.

A follow-up whenever a code is scanned. Watch QR Code Scan picks up scans, so a marketing team can log them in a spreadsheet or alert a salesperson through another app.

Codes that change with your data. Update a Dynamic QR Code edits an existing dynamic code, which suits a retailer that changes a promotion without reprinting labels. Get QR Code reads a code back when a later step needs its details.

Know the limits first. The doc gives no description for these modules, so what each one does is read from its name, and the Uniqode side requires a paid Pro plan or above. For anything the 9 modules skip, Make an API Call reaches the rest of the Uniqode API. The same app may also have an n8n node; the n8n vs Make comparison helps you choose, and the Make pricing page explains what each plan allows. If you are new to the editor, the Make training covers the basics.

Connect

How do you connect your Uniqode account to Make?

  1. 01

    Copy your API key in Uniqode

    In Uniqode, open Settings from the main dashboard navigation, click the API section and copy the key shown on screen. Keep it at hand, Make asks for it in the next step.

  2. 02

    Open the connection window in Make

    Log in to Make, add any Uniqode module to your scenario and click Create a connection. A connection is your Uniqode account linked to Make once, then reused by every Uniqode module.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when several accounts exist. Paste the API key you copied, or follow the on-screen instructions, then save. Make can now read your Uniqode data.

First scenario

Build your first scenario: a QR code for every form response

GoalWhen someone answers a Uniqode form, Make creates a dynamic QR code for that response.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the big + to add the first module. This first module is the one that starts everything.

  2. 02

    Add Watch Form Response

    Search for Uniqode, pick Watch Form Response and click Create a connection to link your account with the API key, or select the connection you already made.

  3. 03

    Fill in the trigger

    Complete the trigger fields. Once the connection exists, Make lists what it can read from your account, so you choose from a menu instead of typing identifiers from memory.

  4. 04

    Add Create a Dynamic QR Code

    Click the + on the right of the trigger, pick Create a Dynamic QR Code and map data from the form answer into its fields. Each answer, called a bundle, flows into this action.

  5. 05

    Test with Run once

    Submit a test answer in your form, then click Run once. Make runs the scenario one time and shows the bundles each module received, so you can check the new code before going further.

  6. 06

    Schedule and switch it on

    Open the clock on the first module to set the schedule (every 15 minutes by default for a new scenario), then switch the scenario on. Make will now check for new answers at that pace.

Triggers

Which Uniqode triggers start a scenario?

3 modules start a scenario when something happens in Uniqode. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Uniqode as soon as it happens.

Uniqode1Watch Form Response

Watch Form Response

triggerIn the docs only

This trigger gives you each new answer to a Uniqode form as a bundle, so the rest of the scenario can act on it. The doc lists the module without a description, so its behavior is read from its name: it watches form responses.

How it fires
scheduled. Make checks Uniqode on the scenario's schedule, not the moment the answer lands.
When to use it
a feedback or sign-up form attached to a QR code, where every answer should reach your CRM or a spreadsheet.
Watch out
on the Free plan of Make, runs are at least 15 minutes apart, so answers arrive in batches.
Uniqode2Watch QR Code

Watch QR Code

triggerIn the docs only

Pick this one to react to QR codes in your Uniqode account rather than to what people do with them. Going by the name, it hands each code it finds to the next module, which helps keep another tool in sync with your library of codes.

How it fires
scheduled. Make polls Uniqode at the interval set on the scenario, shown by the clock badge.
When to use it
a colleague creates codes by hand in Uniqode and you want each one recorded in a shared sheet or announced in a team channel.
Watch out
avoid pairing it with a module that creates codes in the same scenario, or each new code could feed the next run.
Uniqode3Watch QR Code Scan

Watch QR Code Scan

triggerIn the docs only

Scans turn into data here: judging by its name, this trigger passes QR code scans to your scenario, so a printed code can set off a follow-up in another app. It is the module to choose when the physical world should drive the automation.

How it fires
scheduled. Make asks Uniqode for new scans each time the scenario runs on its schedule.
When to use it
a code on a flyer or product box, where each scan should be logged for the marketing team or trigger an alert.
Watch out
every scan counts as at least one operation, meaning one module run that Make bills on your plan, so a popular code eats credits fast.
Modules

What can the Uniqode actions do?

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

Uniqode1

Create a Dynamic QR Code

ActionIn the docs only

Here you get a new dynamic QR code in Uniqode from data that arrived earlier in the scenario. As the name suggests, a dynamic code can be edited after printing, so pick it whenever the destination might change later.

When to use it
one code per registration, product or location, created as soon as the record exists elsewhere.
Watch out
the doc gives no field list, so look at what Make shows in the module before planning the mapping.
Uniqode2

Create a Static QR Code

ActionIn the docs only

A static QR code is what this module produces, the fixed kind you set once and print. Choose it over the dynamic version when the content will never change and you have no reason to edit the code later.

When to use it
a batch of labels whose destination is final, generated from rows in a sheet.
Watch out
if you might need to change the target someday, the dynamic module is the safer pick, since Update a Dynamic QR Code is named for dynamic codes only.
Uniqode3

Get QR Code

ActionIn the docs only

With this action you pull the details of one existing QR code into the scenario so later modules can use them. It reads rather than changes anything, which makes it a safe step to add while you explore.

When to use it
a trigger or another app gives you a code reference and the next step needs the full record, for example to fill an email or a sheet.
Watch out
it works on one code per run, so feed it the identifier mapped from an earlier bundle.
Uniqode4

Make an API Call

ActionIn the docs only

This module opens the rest of the Uniqode API to your scenario, using the same connection as the other modules. It is the fallback when none of the named modules covers what you need.

When to use it
an operation that exists in the Uniqode API but has no dedicated module in Make.
Watch out
you write the request yourself, so keep the Uniqode API documentation open; the Make troubleshooting guide helps when a call returns an error.
Uniqode5

Update a Dynamic QR Code

ActionIn the docs only

Change a dynamic QR code that is already printed, without reprinting it: that is the point of this action, going by its name. The scenario sends the new values and the code people scan keeps working.

When to use it
a campaign ends, a menu changes or a landing page moves, and the codes in the field should follow.
Watch out
do not trigger this scenario with Watch QR Code on the same code, or one edit could start the next run.
Uniqode6

Upload a File

ActionIn the docs only

Send a file from the scenario to your Uniqode account with this module, typically one produced or downloaded by an earlier step. It saves you from downloading and re-uploading documents by hand.

When to use it
a brochure or menu stored in another app that should become available in Uniqode.
Watch out
on the Free plan of Make, files are capped at 5 MB, and the doc does not say which formats Uniqode accepts.
Need help

Need help automating Uniqode with Make?

A person reads every message.

FAQ

Questions about the Uniqode Make integration

01Is the Uniqode Make integration free?
Partly. On the Make side, Uniqode is a standard app, so it is available from the Free plan, which allows 2 active scenarios, runs at least 15 minutes apart, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid Make plans lower the interval to 1 minute and remove the cap on active scenarios. On the Uniqode side, the doc requires a paid Pro plan or above, so the account you connect is not free.
02What do you need to connect Uniqode to Make?
You need an active Uniqode account on a paid Pro plan or above, and its API key. Find the key in Uniqode under Settings, then the API section, and copy it. In Make, add a Uniqode module, click Create a connection, optionally give the connection a name, and paste the key. That connection is then reused by every Uniqode module in your scenarios, so you only do this once per account.
03Do the Uniqode Make integration triggers fire instantly?
No. All 3 Uniqode triggers are scheduled: Make checks Uniqode each time the scenario runs on its schedule, shown by the clock badge on the module. A new scenario runs every 15 minutes by default. On the Free plan, 15 minutes is also the shortest gap between two runs, while paid plans go down to 1 minute. If you need faster reactions, shorten the schedule on a paid plan rather than expecting a webhook.
04What if a Uniqode module is missing in Make?
Use Make an API Call. It calls any endpoint of the Uniqode API with the connection you already set up, so it covers what the 9 listed modules do not. You write the request yourself from the Uniqode API documentation. Keep in mind that the doc gives no description for the modules, so test each one with Run once and read the bundles it returns before building a longer scenario on top of it.
05Should you use Make or n8n for Uniqode?
It depends on the tool your team already knows. Make offers 9 Uniqode modules, a visual editor where each module is a brick, and Make an API Call for the rest of the API. The same app often has an n8n node too, so check what each side lists before committing. If your other automations already run in Make, adding Uniqode there keeps every scenario in one editor you already know.
Same platform

Other docs you might need on this stack.

Browse all integrations