Resources · Make integration

UniFi Access Make integrationAutomate UniFi Access with Make.

Stop creating door access by hand for every new person. The UniFi Access Make integration gives you 18 modules: one trigger, 13 actions and 4 searches. This guide is for office and IT managers, and it walks you through the connection and a first working scenario.

Try the UniFi Access integration on MakeSee the 18 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the UniFi Access Make integration automate?

The UniFi Access Make integration links your access control system to the rest of your tools. In Make you build a scenario (the automation itself, a chain of steps), and each step is a module: here, modules that create users, hand out NFC cards and PIN codes, or watch unlock events.

Badge ready on day one. When a new hire appears in your HR tool or a signed form, Create a User adds the person to UniFi Access, Add Access Policies to a User gives them the right doors, and Send UniFi Identity Invitations sends the invite. Nobody retypes a name.

A clean offboarding. When someone leaves, Update a User records the change on their profile, Delete an NFC Card cancels their badge, and List NFC Cards helps you check that nothing was forgotten.

A readable door log. Watch New Unlock Events picks up each unlock, Get a User adds the name behind it, and the result lands in a sheet or a team chat.

What Make cannot do here: the official documentation for UniFi Access is marked as limited, so Make gives no field list or troubleshooting notes for this app. Test every module with Run once before you rely on it, and keep the Make troubleshooting guide nearby. If you are still choosing a tool, the n8n vs Make comparison lays out the criteria, and the Make pricing page explains how operations are counted.

Connect

How do you connect UniFi Access to Make?

  1. 01

    Add a UniFi Access module

    Open your scenario, click the + and search for UniFi Access. Pick any module, then click Create a connection. A connection is your UniFi Access account linked to Make once, and every UniFi Access module reuses it.

  2. 02

    Name the connection

    This step is optional, but a clear name such as the site or the building helps a lot later, when several people share the same Make team and pick a connection from a list.

  3. 03

    Authorize and save

    Depending on what the screen asks, either approve Make on the UniFi Access page that opens, or paste the key that UniFi Access gives you. Then click Save, and the module is ready to fill in.

First scenario

Your first scenario: onboard a new hire in UniFi Access

GoalWhen a new hire shows up in another app, Make creates the person in UniFi Access and sends the UniFi Identity invitation.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module: the trigger of the app where new hires appear, such as your HR tool or a form.

  2. 02

    Add Create a User

    Click the + on the right of that first module, search for UniFi Access and pick Create a User. Link your connection, then map the new hire's details from the first module into the fields Make displays.

  3. 03

    Send the invitation

    Add Send UniFi Identity Invitations after it and map the user that Create a User just returned. Each bundle (one item passed between modules, here one person) gets its own invitation.

  4. 04

    Test with Run once

    Click Run once with a test person, then open each module to read the bundles it received. Check in UniFi Access that the user exists before going further.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Each module run on one bundle is an operation, the unit Make counts on your plan.

Triggers

What starts a UniFi Access scenario

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

UniFi Access1Watch New Unlock Events

Watch New Unlock Events

triggerIn the docs only

Turns every door unlock recorded by UniFi Access into a starting point for your scenario, so an entry can end up in a log, a report or a message without anyone copying it.

How it fires
scheduled, Make checks the app on the scenario's schedule, every 15 minutes by default, and picks up the unlocks it has not seen yet.
When to use it
you want a readable trace of who opened a sensitive room, stored where your team already looks.
Watch out
the doc names this module without describing it, so its scheduled type is read from its name. Check for the clock badge when you add it, then run it once and read the bundle before mapping anything.
Modules

What the UniFi Access modules can do

UniFi Access gives you 17 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

UniFi Access1

Add Access Policies to a User

ActionIn the docs only

Gives a person the doors and schedules they need by attaching existing access policies to their UniFi Access profile, straight from your scenario.

When to use it
right after Create a User in an onboarding flow, or when someone changes team and needs a new set of rooms.
Watch out
the policy has to exist already; List Access Policies shows you which ones you can pick.
UniFi Access2

Assign NFC Card to User

ActionIn the docs only

Links a physical NFC card to a specific person, so the badge on the desk becomes their badge without a trip to the admin console.

When to use it
the card is already known to UniFi Access and you only need to hand it to the right user.
Watch out
the doc does not explain how this differs from Enroll a NFC Card, so test both with Run once on a spare card.
UniFi Access3

Assign a PIN Code to a User

ActionIn the docs only

Sets a PIN code on a user so they can open a keypad door without a badge, which is handy for contractors or anyone waiting for a card.

When to use it
pair it with Generate a PIN Code in the same scenario, then send the code to the person through another app.
Watch out
a PIN is sensitive, so route it only to channels the person alone can read.
UniFi Access4

Create a User

ActionIn the docs only

Adds a new person to UniFi Access from data that already lives somewhere else, which is the first brick of any onboarding scenario.

When to use it
a hiring form, an HR tool or a signed contract tells you someone is joining and you want their access profile ready.
Watch out
run it on a test person first and check the profile in UniFi Access before you switch the scenario on for real hires.
UniFi Access5

Delete an NFC Card

ActionIn the docs only

Removes an NFC card from UniFi Access, so a lost or returned badge stops being a key to your building.

When to use it
at the end of an offboarding flow, or when someone reports a lost card through a form.
Watch out
a delete cannot be undone from the scenario; put Get an NFC Card before it to confirm you hold the right card.
UniFi Access6

Enroll a NFC Card

ActionIn the docs only

Registers a new NFC card in UniFi Access so it can later be handed to a user, which saves you from adding a fresh stack of badges one by one.

When to use it
new blank cards arrive and need to exist in the system before anyone gets one.
Watch out
Make publishes no detail on the enrollment step, so try it on a single card with Run once before a whole batch.
UniFi Access7

Generate a PIN Code

ActionIn the docs only

Asks UniFi Access for a PIN code, so you never have to invent one or keep a spreadsheet of codes already in use.

When to use it
just before Assign a PIN Code to a User, mapping the generated code into that next module.
Watch out
the doc does not say whether generating a code also assigns it, so check the bundle it returns after Run once.
UniFi Access8

Get a User

ActionIn the docs only

Fetches one person's UniFi Access profile, so the modules that follow can use their details instead of a bare identifier.

When to use it
after Watch New Unlock Events, to put a real name on each unlock before it goes to a sheet or a chat.
Watch out
it needs to know which user you mean, so map the identifier from an earlier module rather than typing it.
UniFi Access9

Get an Access Policy

ActionIn the docs only

Reads a single access policy, so you can see in your scenario what that policy covers before you give it to anyone.

When to use it
in an approval flow, to show a manager the policy a request refers to before Add Access Policies to a User runs.
Watch out
it reads one policy you point to; to browse them all, List Access Policies fits better.
UniFi Access10

Get an NFC Card

ActionIn the docs only

Pulls the record of one NFC card, which tells your scenario what it is dealing with before it changes or removes anything.

When to use it
as a safety check right before Delete an NFC Card or Assign NFC Card to User.
Watch out
it reads one card you point to, so map its identifier from an earlier module and read the bundle after Run once.
UniFi Access11

List Access Policies

SearchIn the docs only

Brings back the access policies set up in UniFi Access, so a scenario can pick or report on them without anyone opening the console.

When to use it
to build a reference sheet of the policies your team can assign, or to find the one to hand to a new user.
Watch out
a search returns zero, one or several bundles, and each following module runs once per bundle.
UniFi Access12

List Devices

SearchIn the docs only

Returns the devices your UniFi Access setup knows about, giving you an inventory you can push to a sheet or a ticketing tool.

When to use it
when your facilities team wants the device list kept somewhere they already work, refreshed whenever the scenario runs.
Watch out
every device becomes its own bundle, so a long list multiplies the operations of the modules after it.
UniFi Access13

List NFC Cards

SearchIn the docs only

Collects the NFC cards registered in UniFi Access, which makes it easy to spot a badge that should have been removed.

When to use it
after an offboarding, to compare the remaining cards with your staff list in a sheet.
Watch out
one bundle per card; add an aggregator if you want a single summary rather than one message per badge.
UniFi Access14

List Users

SearchIn the docs only

Returns the people recorded in UniFi Access, so you can check your access list against the HR or payroll tool that holds the truth.

When to use it
an audit asks who still has access, and you want the answer in a sheet rather than on screen.
Watch out
every user becomes a bundle, so filter early before an action module runs once per person.
UniFi Access15

Make an API Call

ActionIn the docs only

Reaches any endpoint of the UniFi Access API with the connection you already set up, which covers what the ready-made modules leave out.

When to use it
the operation you need has no module of its own in this list.
Watch out
you write the request yourself, and the Make doc for this app gives no API details, so you need the UniFi Access API reference at hand.
UniFi Access16

Send UniFi Identity Invitations

ActionIn the docs only

Sends people their UniFi Identity invitation from the scenario, so a new user gets it as soon as their profile exists.

When to use it
as the last step of onboarding, right after Create a User and Add Access Policies to a User.
Watch out
an invitation lands in someone's inbox, so test Run once on your own test user, never on a real colleague.
UniFi Access17

Update a User

ActionIn the docs only

Changes an existing UniFi Access profile from your scenario, so a move, a new role or a departure shows up without a manual edit.

When to use it
your HR tool records a change and you want UniFi Access to follow it.
Watch out
it acts on one user, so find the right one first with Get a User or List Users and map its identifier.
Need help

Need help automating UniFi Access with Make?

A person reads every message.

FAQ

UniFi Access and Make: common questions

01Is the UniFi Access Make integration free?
Yes, UniFi Access is a standard app in Make, so you can use it on the Free plan. That plan gives you 2 active scenarios, a scheduled run at most every 15 minutes, 5 minutes of execution 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 of execution. Usage is counted in operations, one per module run on one bundle.
02What do you need to connect UniFi Access to Make?
Your UniFi Access account and a Make account. The Make documentation for this app lists no prerequisites, so you follow the generic flow: add a UniFi Access module, click Create a connection, give it a name if you like, approve Make on the UniFi Access page or paste the key the app provides, then click Save. The connection is stored once and every UniFi Access module in your scenarios reuses it.
03Does the UniFi Access trigger react right away?
No. Watch New Unlock Events is a scheduled trigger: Make checks UniFi Access on the scenario's schedule, every 15 minutes by default, and picks up the unlocks it has not processed yet. On the Free plan 15 minutes is the shortest interval; paid plans go down to 1 minute. The doc does not describe this module, so that type is deduced from its name: the clock badge on the module confirms it. There is no instant trigger in this app, so a door unlock reaches your scenario at the next check, not the second it happens.
04What if a UniFi Access module you need is missing?
Use Make an API Call. It calls any endpoint of the UniFi Access API with the same connection as the other modules, so you are not limited to the 18 listed. Keep in mind that Make marks its documentation for this app as limited, with no field list and no troubleshooting notes, so you will need the UniFi Access API reference to write the request. Test it with Run once and read the returned bundle before building on it.
05Should you use Make or n8n for UniFi Access?
It depends on the tool your team already works in. On the Make side, you get 18 UniFi Access modules, including a scheduled trigger on unlock events and Make an API Call for anything else, all from a visual editor that you can start using on the Free plan. The same app often has an n8n node too, so check what exists there before deciding. Compare the modules you actually need on both sides rather than picking on reputation.
Same platform

Other docs you might need on this stack.

Browse all integrations