Resources · Make integration

Layerise Make integrationAutomate Layerise with Make.

Can Make read your Layerise content and act on it? Yes: the Layerise Make integration gives you 7 modules, 6 searches and 1 GraphQL action. This guide is for support teams new to Make, and it walks you from the connection to a first working scenario.

Try the Layerise integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Layerise Make integration let you automate?

The Layerise Make integration links your Layerise account to Make so a scenario (the automation you build in Make, a chain of modules) can look up your articles, experiences, highlights and topic categories, then pass what it finds to another app. It has no trigger, so something else has to start the flow.

Answer support questions from your own content. A new ticket lands in your helpdesk app, Search Articles looks for matching Layerise articles, and the next module adds them to the ticket. Each module is one brick of the scenario: a search, an action or another app.

Keep a shared list of your topics up to date. Search Topic Categories and Search Languages return several items, which Make calls bundles, one per category or language. Map them into a spreadsheet module and the list your team edits stays in line with Layerise.

Reach what the searches do not cover. Execute a GraphQL Query sends a query you write yourself to Layerise, which is the way to reach data none of the 6 searches returns.

Know the limit before you start: Make marks its own Layerise documentation as limited, because too little public information exists about the app. Expect to test each module with real data. The Make troubleshooting guide helps when a run fails, and the n8n vs Make comparison sets out criteria if you are still choosing a tool. For a guided start, the Make training covers these gestures in depth.

Connect

How do you connect your Layerise account to Make?

  1. 01

    Open the connection window

    Add any Layerise module to your scenario and click Create a connection. A connection is your Layerise account linked to Make once, then reused by all 7 modules of the app.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, handy when several workspaces sit side by side. Then either approve Make on the Layerise page that opens, or paste the key Layerise gives you, depending on what the window asks for.

  3. 03

    Save and check the fields

    Click Save. Back in the module, the fields should now fill with what Make can read from your account. An empty list at this point usually points to the authorization, not the scenario.

First scenario

Your first scenario with Layerise and Make

GoalWhen a new ticket reaches your helpdesk app, Make searches your Layerise articles and hands the results to a GraphQL query you wrote.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the trigger of the app where your tickets arrive, since Layerise has no trigger of its own.

  2. 02

    Add Search Articles

    Click the + on the right of that trigger, search for Layerise and choose Search Articles. Create the connection when Make asks, then fill its fields with data from the ticket.

  3. 03

    Add the GraphQL action

    Add Execute a GraphQL Query after the search. Write the query your team needs and map the article data from the previous module into it.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can check that the search found articles 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 each bundle is an operation, the unit Make counts on your plan.

Modules

What can the Layerise modules do in Make?

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

Layerise1

Execute a GraphQL Query

ActionIn the docs only

This is your way into everything the six search modules leave out: you write a GraphQL query, Make sends it to Layerise and returns the answer as data for the next module.

When to use it
you need a piece of Layerise data or a change that no search module offers, and someone on the team knows how to write a GraphQL query for Layerise.
Watch out
Make documents nothing about this query, so test it with Run once before letting it touch live data.
Layerise2

Search Articles

SearchIn the docs only

You get the Layerise articles that match your search, each one as a separate bundle the next modules can reuse, for example to quote it in a reply.

When to use it
a customer question comes in through another app and you want the help content that already answers it.
Watch out
a search can return zero, one or many articles, so plan what the scenario does when nothing matches.
Layerise3

Search Experiences

SearchIn the docs only

Pulls the experiences stored in your Layerise account into Make, one bundle per experience, so another app can list, count or display them without anyone copying them by hand.

When to use it
a report or dashboard in another tool should show which experiences exist in Layerise.
Watch out
the search may return several results; add a filter if only one should continue.
Layerise4

Search Highlights

SearchIn the docs only

Brings your Layerise highlights into the scenario, each as its own bundle, so their content can feed a message, a sheet or another publishing tool.

When to use it
your highlights belong where people already look. Your team channel, say, or a customer newsletter, with no retyping.
Watch out
no results means the next modules never run. In a test, that looks like a silent failure.
Layerise5

Search Languages

SearchIn the docs only

Tells your scenario which languages your Layerise account works with, returned as one bundle per language that later modules can branch on.

When to use it
a flow has to route content or tickets differently by language and needs the list Layerise actually holds.
Watch out
treat the result as a list, not a single value; map one bundle at a time or aggregate them first.
Layerise6

Search Reminder Schemas

SearchIn the docs only

Lists the reminder schemas defined in Layerise so the scenario knows which ones exist before another module relies on them.

When to use it
you are building a flow around Layerise reminders and want to check or pick a schema by data instead of guessing.
Watch out
Make gives no detail on what a schema contains, so read a real bundle after Run once before mapping anything.
Layerise7

Search Topic Categories

SearchIn the docs only

Returns the topic categories that organize your Layerise content, so another app can mirror the same structure or tag incoming requests with it.

When to use it
a shared spreadsheet or a helpdesk should use exactly the categories your Layerise account holds.
Watch out
several categories mean several bundles, and each bundle that reaches a later module costs one operation.
Need help

Need help automating Layerise with Make?

A person reads every message.

FAQ

Questions about the Layerise Make integration

01Is the Layerise Make integration free?
Yes, Layerise is a standard app, so all 7 modules work on the Make Free plan. That plan has its own limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute, allow unlimited active scenarios and 40 minutes of execution. Usage is counted in operations each month, so a search that returns many bundles uses more of your plan.
02What do you need to connect Layerise to Make?
A Layerise account and a Make account. Make's documentation lists no special prerequisite for Layerise, so the standard flow applies: add a Layerise module, click Create a connection, optionally name it, then authorize Make on the Layerise page or paste the key Layerise gives you, and click Save. The connection is created once and shared by every Layerise module in your scenarios. Since the official documentation for this app is marked as limited, test the connection with a single search module and Run once.
03Can Layerise start a Make scenario in real time?
No, not on its own: the Layerise app in Make has no trigger, neither scheduled nor instant. A scenario that uses Layerise has to start another way. The first option is a trigger from another app, such as your helpdesk or form tool, that fires when a ticket or entry arrives. The second is a schedule on the first module, set to every 15 minutes by default, with a Layerise search as that first module. On the Free plan, the shortest interval is 15 minutes; paid plans go down to 1 minute.
04What if the Layerise module you need is missing in Make?
Start with Execute a GraphQL Query. It sends a query you write to Layerise, so it can reach data the 6 search modules do not return. Layerise has no Make an API Call module in Make, so the GraphQL action is the only open door inside this app. Make also warns that its Layerise documentation is limited, which means you will learn the details by testing with Run once. If the query becomes hard to maintain, the Make agency team can review the case with you.
05Should you use Make or n8n for Layerise?
It depends on what your team already runs and what the scenario needs. On Make, Layerise gives you 7 ready modules, 6 searches and a GraphQL action, usable from the Free plan with the visual editor described on this page. Many apps also have an n8n node, so check whether one exists for Layerise before you compare. Then weigh the same criteria for both tools: which modules cover your case, how you start the flow without a Layerise trigger, and how your team prefers to build and test.
Same platform

Other docs you might need on this stack.

Browse all integrations