Resources · Zapier integration

Frontify Zapier integrationAutomate Frontify with Zapier.

The Frontify Zapier integration gives you 1 trigger, 3 actions and 0 searches. Enough to react the moment an asset event fires in a project, add assets from a link or a file, and invite people to a library without opening Frontify.

See the 4 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Frontify Zapier integration actually does

Zapier links Frontify, the brand management platform, to the other tools your team uses. You build a Zap: an automation with one trigger (the event that starts it) and one or more actions (what it then does for you). Frontify brings one trigger and three actions to that game.

Three results people build with it. First, a reviewer who gets access on time: an asset event fires in a project through New Asset Webhook, and Invite a User to a Project adds the right person to that library. Second, a library fed from links: a URL collected somewhere else becomes an asset with Create External Asset by URL, so a video hosted elsewhere sits next to your brand files. Third, files that land where the brand team looks: Create File Based Asset uploads a file from a URL, or one handed over by an earlier step of the Zap, into the project you pick.

Now the honest part. Zapier offers no search for Frontify, so a Zap cannot look up an existing asset, a user or a project before acting. There is no action to edit, move or delete an asset either, and only one trigger, tied to asset events. If your process needs any of that, Zapier will not cover it with this app (a side-by-side like Make vs Zapier helps you check whether another tool does better here).

The upside: the single trigger is instant, which matters more than it sounds once you look at the cost block below. Still deciding whether Zapier itself fits your team? Our Zapier review covers the platform as a whole.

Vocabulary

Zapier words in one minute

Seven terms, plain English. Each one shows up again further down the page.

Zap
The automation you build on Zapier: one trigger, then one or several actions that run each time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for it to happen.
Action
What the Zap does after it starts: the step that creates, sends or moves something in an app on your behalf.
Task
The unit Zapier bills you for: one action your Zap finishes successfully. The number on your plan counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself, the moment the event occurs.
Filter
A step that lets the Zap continue only when the incoming data meets the condition you set, and halts it otherwise.
Connection
Your Frontify account linked to Zapier once, then reused by every step of every Zap that works with Frontify.
Cost

What a Frontify Zap really costs

Short version: the trigger is free, each successful action counts as one task, and the free plan handles a basic two-step Zap.

  • TriggerNever costs a task
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo

The free plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger and one action. Add a second action or a filter and it becomes a multi-step Zap, which needs a paid plan. A three-action Zap uses three times the tasks of a one-action Zap, while an action that fails is not counted at all. The interval grid below only concerns polling triggers, so it never slows the instant Frontify trigger. Frontify is not a premium app, so it works from the free plan.

Connect

Connect Frontify to Zapier in three steps

  1. 01

    Open your Apps page

    In your Zapier account, go to the Apps page and click + Add connection. A dialog opens with a search box: type Frontify and pick it from the results.

  2. 02

    Sign in to Frontify

    Click Add connection. A new tab opens on Frontify, where you log in with the account the Zaps should act as. Use an account that can reach the brands and projects you plan to automate.

  3. 03

    Grant access

    Accept the access request in that tab. The connection then appears in your Apps list, and every Frontify step you add later reuses it, so this is a one-time job per account.

First Zap

Your first Frontify Zap

GoalWhen an asset event fires in a project, invite a reviewer to that library, but only for one of the events you ticked.

  1. 01

    Pick the trigger

    Create a new Zap, choose Frontify as the app and New Asset Webhook as the trigger event, then select your Frontify connection.

  2. 02

    Set the scope

    Choose the Brand, then the Project / Library to watch, then the Events you want to hear about. All three are required, and they decide what wakes the Zap up.

  3. 03

    Test the trigger

    Run the test. Zapier brings back the three most recent items from the connected account, so you map the next steps on real data instead of a guess.

  4. 04

    Add the filter and the action

    If you ticked several Events, add a Filter that lets only one of them through, then Invite a User to a Project: pick the Brand, the Project / Library, the User Email and the Role.

  5. 05

    Test, then publish

    Test the action once and check the invite in Frontify. Then click Publish to switch the Zap on. Remember the filter makes this a paid-plan Zap.

Triggers

The Frontify trigger

1 event starts a Zap when something happens in Frontify, and one of them is instant: the app calls Zapier straight away, whatever your plan.

1

New Asset Webhook

Instant trigger

In Zapier“Triggers when an asset webhook is fired.”

This starts your Zap whenever an asset event you chose occurs in one Frontify project or library, so the rest of your tools hear about it without anyone posting a message.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a marketing team wants a reviewer, a channel or a spreadsheet updated as soon as a designer drops a new asset into the campaign library.
Watch out
the trigger watches one project at a time and only the events you tick, so a second library means a second Zap or an edited one.
Actions

The three Frontify actions

Frontify gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create External Asset by URL

Action

In Zapier“An external asset in Frontify is an asset that does not have a file as a source but rather a URL.”

Adds an asset whose source is a link rather than a file, so content hosted elsewhere gets a proper place and title inside your Frontify library.

When to use it
links to approved videos or partner pages collected in a form should appear next to the brand assets.
Watch out
a Title is required on top of the URL, so map one from the trigger or type a fixed one.
2

Create File Based Asset

Action

In Zapier“Creates a new asset within Frontify by uploading either a file from a URL or another Zap.”

Uploads a real file into a chosen project, taken either from a URL or from a file an earlier step of the Zap already carries.

When to use it
final exports saved in another tool should end up in the brand library without a manual download and upload.
Watch out
the File Name must include the extension, such as .png, or the asset arrives badly named.
3

Invite a User to a Project

Action

In Zapier“Invite a new or existing user to a project or a library. Already invited users are ignored.”

Gives one or several people access to a project or library with the role you pick; anyone already invited is simply skipped.

When to use it
a new agency contact signed in your CRM should reach the campaign library on day one.
Watch out
several addresses go in one field, separated by commas, and all of them get the same role.
When it breaks

When a Frontify Zap breaks

Zapier links no help article to Frontify, so the traps below are the general Zapier ones, applied to this app.

Most Frontify Zaps that go wrong do so for four reasons. None of them throws a clear error, which is why they are worth knowing before you publish. When you are stuck anyway, our Zapier troubleshooting page walks through the usual fixes.

  • No catch-up on old assets

    A Zap only reacts to events after it is switched on. Assets already in the library are never picked up; moving that backlog is a separate job.

  • The Zap that feeds itself

    Create an asset in the very project the trigger watches and the new asset fires the trigger again. The loop repeats and drains your task count fast.

  • Bulk uploads held back

    A sudden flood of events after a big import or a migration can be held back by Zapier's flood protection instead of running one by one.

  • Duplicate starts

    Zapier remembers what it has already seen on polling triggers so the same item does not start a Zap twice. That safeguard belongs to polling; this trigger is instant.
Need help

Need help automating Frontify with Zapier?

A person reads every message.

FAQ

Frontify and Zapier: common questions

01Is the Frontify Zapier integration free?
Yes, you can use it on Zapier's free plan, because Frontify is not a premium app. The free plan gives you 100 tasks a month and unlimited Zaps, with one catch that the pricing page does not shout about: every Zap is limited to two steps, one trigger and one action. A Zap built on New Asset Webhook followed by Invite a User to a Project fits. Add a filter or a second action and it becomes a multi-step Zap, which needs a paid plan. No price is quoted here because Zapier changes its grids often.
02How many tasks does a Frontify Zap use?
One task per action that completes successfully, and nothing else. The trigger never costs a task, however many events Frontify sends. So a Zap that creates one asset uses one task per run, while a Zap that creates an asset and then invites a user uses two. An action that fails is not counted against your plan. The thing to watch is the loop case: an action creating assets in the project your trigger watches can fire the Zap again and again, and each round costs tasks.
03Does Frontify trigger Zaps in real time?
Yes. New Asset Webhook is an instant trigger: Frontify tells Zapier the moment the event happens, so the Zap starts right away. The polling interval grid, which goes from 15 minutes on the free plan down to one minute on Team and Enterprise, does not apply to it. That is good news on a free plan, since a polling trigger there would only be checked every 15 minutes. In the editor, a Zap built on an instant trigger shows a lightning bolt.
04What does it take to connect Frontify to Zapier?
A Frontify account, plus access to the brands, projects and libraries the Zap should touch. The connection is made once from the Apps page of Zapier with + Add connection: you sign in to Frontify in the tab that opens and grant Zapier access. Every Frontify step then reuses that connection. If a project is missing from the Project / Library dropdown later on, the connected account most likely cannot see it, so fix its access on the Frontify side first.
05Why does a Frontify Zap keep running on its own?
Usually because it writes into the place its own trigger watches. If New Asset Webhook listens to a project and a later step creates an asset in that same project, the new asset fires the trigger, which creates another asset, and so on. The loop eats tasks quickly. The fix is simple: send created assets to a different project or library than the one being watched, or add a filter so only the events you really want get through, keeping in mind a filter needs a paid plan.
06What if the Frontify operation you need is not available?
Then Zapier cannot do it with this app today. The integration offers one trigger, three actions and no search: there is no way to find an existing asset, edit or delete one, or watch several projects with one trigger. A workaround is sometimes possible by chaining another app before or after Frontify, but the Frontify part stays limited to creating assets and inviting users. If that gap is a deal breaker, compare what other automation platforms expose for Frontify before you build.
07Zapier, Make or n8n for Frontify?
It depends on your criteria rather than on a winner. On Zapier, the Frontify trigger is instant, so the free plan stays useful for it. The limits are the short list of operations (one trigger, three actions, no search) and the two-step cap on the free plan. If you need a search, an edit or a delete in Frontify, or more steps without a paid plan, check what Make and n8n expose for Frontify before you build.
Same platform

Other docs you might need on this stack.

Browse all integrations