Resources · Make integration

Layerre Make integrationAutomate Layerre with Make.

Can Make handle your Layerre templates while you work elsewhere? The Layerre Make integration gives you 7 action modules for templates, variants and Canva imports. This page shows how to link your account, what each module is for and how to build a first scenario.

Try the Layerre integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Layerre Make integration let you automate?

The Layerre Make integration lets a Make scenario (the automation you build in Make, a chain of modules) work with your Layerre account for you. Each module is one brick of that chain. Here all 7 are actions: they list, create or delete templates and variants, or import a template from Canva.

Keep a clean template library. A scenario can pull the list with Get Templates, then remove the ones you retired using Delete a template. Nobody has to open Layerre and click through each entry.

Bring Canva designs over without copy and paste. Create Template from Canva turns a Canva design into a Layerre template, so a designer finishing work in Canva can hand it off through Make. Get Variants and Create a Variant then work with the variants of that template.

Reach what the listed modules skip. Make an API Call reuses your connection to call any endpoint of the Layerre API. Useful, because Make itself says its Layerre documentation is limited: there is not enough public information about the app, so expect to test each module with Run once before you trust it.

Layerre has no trigger in Make, so a scenario starts from a schedule or from another app. The same kind of app often has an n8n node too; if you are weighing both tools, read n8n vs Make. To learn the editor properly, the Make training walks through it, and the Make pricing page explains how operations are counted.

Connect

How do you connect your Layerre account to Make?

  1. 01

    Add a Layerre module

    In a scenario, click the +, search for Layerre and pick any of its modules. Then click Create a connection. A connection is your Layerre account linked to Make once, and every Layerre module reuses it afterward.

  2. 02

    Name the connection

    Giving it a name is optional but worth the few keystrokes. If you ever run two Layerre accounts, one for a client and one for your own work, a clear name tells you which one a module is using.

  3. 03

    Authorize and save

    Make either opens a Layerre page where you allow access, or asks you to paste a key that Layerre gives you. The Layerre doc does not say which of the two it uses. Finish the step, then click Save.

First scenario

Build your first scenario with Layerre

GoalEach time you run it, Make turns an approved Canva design into a Layerre template, then adds a variant of that new template.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the editor. This first slot is where your chain begins.

  2. 02

    Add Create Template from Canva

    Search for Layerre, choose Create Template from Canva and pick your connection (or create it now). Once connected, Make lists what it can read in your account, so you pick the design instead of typing it.

  3. 03

    Chain Create a Variant

    Click the + on the right of the first module and add Create a Variant. Map the template that the previous module returns into its fields, so the variant is attached to the template you just imported.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received (a bundle is one item passed along, here the new template). Open Layerre and check the template and its variant.

  5. 05

    Decide how it starts

    Run once is enough when you import a design now and then. A schedule (the clock on the first module, every 15 minutes by default) would repeat the same import on each run, so only switch the scenario on once the design it points to changes between runs.

Modules

What each Layerre module does

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

Layerre1

Create Template from Canva

ActionIn the docs only

This module brings a Canva design into Layerre as a new template, so the design lands where the rest of your templates live without a manual export. It is the only module here that touches Canva.

When to use it
right after a design is approved in Canva and should become a reusable Layerre template.
Watch out
the doc lists no fields for it, so run it once on a test design and read what it returns before chaining more modules.
Layerre2

Create a Variant

ActionIn the docs only

Here you get a new variant added in Layerre from inside a scenario. Judging by the module names, variants sit next to templates; the doc does not define them further, so treat that as a reading, not a spec.

When to use it
after Get Templates or Create Template from Canva, when each incoming template should get its own variant.
Watch out
every variant created costs one operation, the unit Make counts on your plan.
Layerre3

Delete a template

ActionIn the docs only

Retired templates disappear from your Layerre account with this module, which keeps the library short for whoever picks a template next. It acts on one template per bundle it receives.

When to use it
after Get Templates, with a filter in between so only the templates you meant to retire reach it.
Watch out
treat the deletion as final and test it with Run once on a throwaway template first.
Layerre4

Delete a variant

ActionIn the docs only

Use it to remove a single variant from Layerre while leaving its template untouched, unlike Delete a template which works at the template level. That keeps the cleanup narrow.

When to use it
once Get Variants has returned the list and you only want to drop the outdated ones.
Watch out
treat the deletion as final: place a filter before it and check the bundles in a Run once test.
Layerre5

Get Templates

ActionIn the docs only

Judging by its name, you receive your Layerre templates as bundles, one per template, ready to feed the next module. Most scenarios on this app start here, since Layerre has no trigger.

When to use it
as the first module of a scheduled scenario that needs to act on existing templates.
Watch out
every module after it runs once per template, so a large library multiplies the operations counted on your plan.
Layerre6

Get Variants

ActionIn the docs only

The result is a list of variants from your Layerre account, handed to the next module one bundle at a time. Pick it over Get Templates whenever the scenario is about variants rather than whole templates.

When to use it
before Delete a variant, or to send variant details to another app such as a spreadsheet.
Watch out
the doc gives no filter options for it, so check in a Run once test what it actually returns.
Layerre7

Make an API Call

ActionIn the docs only

With this module you can call any endpoint of the Layerre API while reusing the connection you already created, so there is no second login to manage. It covers whatever the six other modules leave out.

When to use it
when you need a Layerre feature that none of the listed modules offers.
Watch out
you have to know the endpoint yourself, and Make says public information on Layerre is thin.
Need help

Need help automating Layerre with Make?

A person reads every message.

FAQ

Layerre and Make: common questions

01Is the Layerre Make integration free?
Yes, Layerre is a standard app in Make, so you can use it on the Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the gap to 1 minute and allow unlimited active scenarios. Layerre may have its own pricing, which this page does not cover.
02What do you need to connect Layerre to Make?
A Layerre account and a Make account are enough to start, since the Layerre doc lists no other prerequisite. Add any Layerre module, click Create a connection, name it if you like, then either authorize Make on the Layerre page or paste the key Layerre provides, and click Save. The doc does not say which of the two methods Layerre uses. Once saved, the connection works for all 7 Layerre modules, so you only do this once per account.
03Can a Layerre scenario start in real time?
Not from Layerre itself, because the app has no trigger module in Make. You start the scenario another way. The simplest is scheduling: set the clock on the first module, which runs every 15 minutes by default on a new scenario, or every minute at best on a paid plan. The other way is to begin with a trigger from another app, for example a form or a file tool, and add Layerre modules after it. Only an instant trigger from that other app reacts as soon as something happens.
04What if the Layerre module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Layerre API with the connection you already have, so you are not limited to the 6 other modules. The catch is documentation: Make says there is not enough public information about Layerre to document it fully, so you will need the endpoint details from Layerre. Test each call with Run once and read the bundle it returns before you switch the scenario on.
05Should you use Make or n8n for Layerre?
It depends on the tool you already work in. On Make, Layerre offers 7 action modules and Make an API Call for the rest, all on the Free plan. Many apps also have an n8n node, so check whether Layerre is one of them before choosing. If your other automations already run in one tool, keeping Layerre there saves you from maintaining two sets of connections. The comparison page on this site sets out the general criteria between the two tools.
Same platform

Other docs you might need on this stack.

Browse all integrations