Resources · Make integration

CraftQL Make integrationAutomate CraftQL with Make.

Want your Craft CMS site to react to what happens in your other tools? The CraftQL Make integration gives you 3 action modules: Mutate, Query and Simple. This guide shows how to link your token, build a first scenario and pick the right module.

Try the CraftQL integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the CraftQL Make integration do for you?

The CraftQL Make integration links the CraftQL plugin of your Craft CMS site to Make, a tool where you build a scenario (the automation itself, a chain of modules) without code. Each module is one brick: here, three actions that talk to your site through the GraphQL token you create in CraftQL.

Feed your site from another tool. A marketing team collects entries in a form app; the scenario starts on that app, then hands each bundle (one item passed from module to module, such as one entry) to Mutate, the module whose GraphQL name points to writing data.

Pull site content into a report. An editor who wants a list of pages in a spreadsheet can start the scenario on a schedule and place Query, whose name points to reading data, before a module of another app.

A third module to explore. Simple completes the list. The official docs give no description for any of the three, so open each one in the editor and read the fields Make lists once your connection exists.

What Make does not give you here: no trigger, so CraftQL never starts a scenario by itself, and no universal Make an API Call module. The docs also say their CraftQL content is AI-generated and may contain mistakes, so double-check anything important with CraftQL. If the same app exists as an n8n node, the n8n vs Make page lays out how the two tools differ, and our Make review covers Make as a whole. Need a hand? The Make agency team builds these flows.

Connect

How do you connect CraftQL to Make?

  1. 01

    Create a token in CraftQL

    In your Craft CMS control panel, open the GraphQL section, click Tokens, then New token. Copy the API token shown in the Authorization Header section. You need Craft CMS 3.6.0 or later and the right to install plugins.

  2. 02

    Add a CraftQL module in Make

    Log in to Make, add any CraftQL module to your scenario and click Create a connection. A connection is your CraftQL account linked to Make once, then reused by every CraftQL module.

  3. 03

    Paste the token and save

    Give the connection a name in Connection name if you like, it is optional. Then paste the token you copied, or follow the on-screen instructions, and save. Make can now list what it reads on your site.

First scenario

Your first scenario with CraftQL

GoalWhen a new entry lands in another app, Make passes it to CraftQL Mutate so your site receives the data.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Since CraftQL has no trigger, this first module comes from the app where your entries arrive.

  2. 02

    Add the CraftQL module

    Click the + on the right of the first module, search for CraftQL and pick Mutate. Click Create a connection and paste your token if you have not done it yet.

  3. 03

    Fill the fields

    Fill the fields of Mutate and map the data coming from the first module. Once the connection exists, Make lists what it can read on your site, so you pick instead of typing.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time and shows the bundles each module received. Open them to check that Mutate got what you expected before going further.

  5. 05

    Schedule and switch on

    Set the schedule on the first module with the clock. A new scenario runs every 15 minutes by default, and the Free plan cannot go below that. Then switch the scenario on.

Modules

What each CraftQL module does

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

CraftQL1

Mutate

ActionIn the docs only

Mutate gets data from your scenario into your Craft CMS site. Its name comes from GraphQL, where a mutation writes rather than reads; the official docs add no description, so check the fields in the editor.

When to use it
entries collected in another app should end up stored on your site.
Watch out
it runs once per bundle it receives, so test with Run once on a single item first.
CraftQL2

Query

ActionIn the docs only

Query hands you content from your site so the next modules can use it. In GraphQL, a query reads data, and that is what the name suggests; Make publishes no description, so confirm in the editor.

When to use it
a spreadsheet or a message in another app needs data that already sits in Craft CMS.
Watch out
place it after a trigger or a schedule, since CraftQL cannot start the scenario.
CraftQL3

Simple

ActionIn the docs only

Simple is the third CraftQL action, and the only one whose name says nothing about reading or writing. The docs leave it undescribed, so add it to a test scenario and look at the fields Make offers.

When to use it
Mutate and Query do not match what you have in mind and you want to see what else the app exposes.
Watch out
the CraftQL docs are flagged as AI-generated, so verify with CraftQL.
Need help

Need help automating CraftQL with Make?

A person reads every message.

FAQ

CraftQL and Make: common questions

01Is the CraftQL Make integration free?
Yes, on the Make side. CraftQL is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and lift the active scenario cap. Each operation, one module run on one bundle, counts on your plan. CraftQL itself has its own subscription, described on its pricing page.
02What do you need to connect CraftQL to Make?
You need an active Craft CMS installation, version 3.6.0 or higher, with the right to install plugins, plus an account on CraftQL. In the control panel, open the GraphQL section, click Tokens, then New token, and copy the API token shown in the Authorization Header section. In Make, add a CraftQL module, click Create a connection, give it a name if you want, and paste that token. The same connection then serves all three CraftQL modules.
03Does the CraftQL module trigger in real time?
No, because CraftQL has no trigger at all in Make. Its three modules are actions, so something else has to start the scenario. You have two options. Place a trigger from another app first, for example the form or shop where entries arrive, then add Mutate or Query after it. Or rely on scheduling: the clock on the first module starts the scenario on its own, every 15 minutes by default on a new scenario, with 15 minutes as the floor on the Free plan.
04What if a CraftQL module is missing in Make?
It depends on what you need. CraftQL has only three modules in Make (Mutate, Query and Simple) and no Make an API Call module, so you cannot fall back on a free-form request inside this app. Start by opening each of the three in a test scenario and reading the fields Make lists, since the docs describe none of them. If what you need is still out of reach, look for another app that covers it, or ask the Hack'celeration team to review your case.
05Is Make or n8n better for CraftQL?
It depends on the rest of your setup rather than on CraftQL alone. In Make, CraftQL brings three action modules and no trigger, so your scenario always starts from another app or a schedule. The same app often has an n8n node as well, so check that list before you decide. Pick the tool where your other apps and your team already are, and compare the two on the modules each one offers for your case, not on reputation.
Same platform

Other docs you might need on this stack.

Browse all integrations