Resources · Make integration

Unifire Make integrationAutomate Unifire with Make.

Can Make pick up what lands in your Unifire account and pass it on? The Unifire Make integration has 2 modules: one trigger that watches new assets and one API call. This page covers the API key, a first scenario and when each module fits.

Try the Unifire integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Unifire Make integration let you automate?

The Unifire Make integration links your Unifire account to Make, so a scenario (the automation you build in Make, a chain of modules) can pick up new Unifire assets at each scheduled check and then act on it. It rests on two modules, a scheduled trigger and a Make an API Call module, both using one API key.

Hand new assets to the rest of your stack. Watch New Assets starts the scenario when Unifire holds something new. From there, you add a module of another app after it: a message to your team, a row in a sheet, a task in your project tool. Each item that flows between modules is called a bundle.

Reach parts of Unifire that have no module. The catalog is short, so Make an API Call does the heavy lifting. It calls any endpoint of the Unifire API with the same connection, which means you do not paste your key twice. You need the endpoint name from the Unifire API documentation, which this page does not reproduce.

Chain the two. A typical content team setup watches for a new asset, then calls the API to fetch or update something about it before passing the result on.

Know the limits before you build. Make's documentation for this app is marked as AI-generated from Unifire's own docs and may contain mistakes, and it gives no description of either module. Test every step with Run once before you rely on it. If you hesitate between tools, the n8n vs Make comparison lays out the differences, and our Make review covers the editor in depth. For a hand with the build, see the Make agency.

Connect

How do you connect your Unifire account to Make?

  1. 01

    Copy your API key in Unifire

    Log in to Unifire and open the dashboard. Click Settings, then pick the API section of the workspace settings and copy the key shown there. You need an active Unifire account for this key to exist.

  2. 02

    Add a Unifire module in Make

    In your scenario, add any Unifire module and click Create a connection. A connection is your Unifire account linked to Make once, then reused by every Unifire module. The Connection name field is optional; a clear name helps later.

  3. 03

    Paste the key and save

    Paste the API key you copied into the credentials field, or follow the instructions Make shows on screen, and save. The module now lists what it can read from Unifire, and you can fill in the rest of its settings.

First scenario

Build your first scenario with Unifire

GoalWhen a new asset shows up in Unifire, Make calls the Unifire API to act on it.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the big + in the middle of the canvas. That + is where your first module, the trigger, goes.

  2. 02

    Pick Watch New Assets

    Search for Unifire, choose Watch New Assets and click Create a connection to link your account with the API key. Then fill in the fields the module asks for.

  3. 03

    Add Make an API Call

    Click the + on the right of the trigger and add the Unifire Make an API Call module. It reuses the connection. Map data from the trigger into the call so each new asset gets handled.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received. Open them to check the trigger picked up an asset and the call answered as expected.

  5. 05

    Set the schedule and switch it on

    Click the clock on the first module. A new scenario checks every 15 minutes by default, and the Free plan cannot go lower. Pick your interval, then switch the scenario on.

Triggers

Which Unifire trigger starts a scenario?

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

Unifire1Watch New Assets

Watch New Assets

triggerIn the docs only

This trigger gives your scenario a starting point inside Unifire: each new asset it finds becomes a bundle that the next modules can use. Make's documentation lists it by name only, so its type comes from that name and its fields are shown by the module itself once connected.

How it fires
scheduled, Make checks the app on the scenario's schedule and picks up what is new since the last check.
When to use it
any flow that should react once Unifire has produced something, such as alerting a colleague or storing a copy elsewhere.
Watch out
run it once and read the bundle before mapping anything, since the documentation does not describe what an asset contains.
Modules

What else can Make do with Unifire?

Unifire gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Unifire1

Make an API Call

ActionIn the docs only

With this module you reach any endpoint of the Unifire API from your scenario, using the connection you already created, so nothing is out of reach just because there is no dedicated module.

When to use it
as soon as you need something beyond watching new assets, like reading or updating data the trigger does not return.
Watch out
you write the endpoint yourself, so keep the Unifire API documentation open and test with Run once.
Need help

Need help automating Unifire with Make?

A person reads every message.

FAQ

Unifire and Make: frequent questions

01Is the Unifire Make integration free?
Yes, on the Make side. Unifire is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Every module run is an operation, which Make counts on your monthly credits. Your Unifire subscription is a separate matter, handled on Unifire's own pricing page.
02What do you need to connect Unifire to Make?
An active Unifire account and its API key. In Unifire, go to the dashboard, click Settings, open the API section of the workspace settings and copy the key. In Make, add a Unifire module, click Create a connection, give it a name if you like and paste the key. That single connection then serves both Unifire modules, the trigger and the API call, so you never enter the key a second time in the same scenario or in the next ones you build.
03Does the Unifire trigger in Make fire in real time?
No. Watch New Assets is a scheduled trigger, the type given by its name since the documentation adds nothing else. Make checks Unifire on the scenario's schedule, every 15 minutes by default, and handles whatever is new since the previous check. On a paid plan the interval can drop to 1 minute. For a quicker test while you build, the Run once button executes the scenario on demand and shows you the bundles straight away, without waiting for the next scheduled check.
04What if the Unifire module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Unifire API with the connection you already set up, so you cover what the trigger alone does not do. You will need the endpoint from the Unifire API documentation, since Make lists no other Unifire module. Keep in mind that Make's page for this app is flagged as AI-generated and may contain mistakes; if something does not match, check with Unifire directly and test each call with Run once.
05Should you use Make or n8n for Unifire?
It depends on how you like to work, not on Unifire. In Make, you get the two modules described here, a guided editor and one connection shared by both. The same app often has an n8n node too, so check what that node offers before choosing. Compare how each tool fits your team and the flows you plan, then pick the one where your first scenario reads most clearly. Neither choice changes what the Unifire API itself allows.
Same platform

Other docs you might need on this stack.

Browse all integrations