Resources · Make integration

Curator Make integrationAutomate Curator with Make.

Can Make pick up new Curator confirmations and open sessions for you? The Curator Make integration gives you 3 modules: one scheduled trigger and two actions. This page shows how to link your account with an API key, then walks you through a first scenario you can test right away.

Try the Curator integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Curator Make integration automate?

The Curator Make integration links your Curator account to Make so other apps can react to Curator, and Curator can react to them, without code. You build a scenario, which is the automation itself: a chain of modules, each one a single brick such as a trigger or an action.

Hand off new confirmations. Watch Confirmations is the only trigger. Make checks Curator on the scenario's schedule and passes each new confirmation along as a bundle, meaning one item flowing to the next module. From there you can post it in a team chat or copy it into a spreadsheet.

Open sessions from another tool. Create a Session goes the other way: a form, a CRM or a sheet feeds the details, and Curator gets a new session without anyone retyping them.

Reach the rest of the API. Make an API Call covers anything the two named modules leave out, with the same connection.

Know the limits before you start. The Make documentation for Curator is short: it lists the three modules without describing their fields, and it warns that its text is AI-generated from Curator's own documentation, so check anything important with Curator. Curator may also have an n8n node; if you are choosing between the two tools, read n8n vs Make. New to the editor? Make training starts from zero, and Make troubleshooting helps when a run fails.

Connect

How do you connect your Curator account to Make?

  1. 01

    Copy your API key in Curator

    Sign in to Curator, open the Integration section from the main menu, then click API Access. The key appears on screen: copy it. You need an active Curator account for this to work.

  2. 02

    Add a Curator module in Make

    Open a scenario, search for Curator, pick any of its modules and click Create a connection. A connection is your Curator account linked to Make once, then reused by every Curator module.

  3. 03

    Paste the key and save

    Give the connection a name in Connection name if you like, which helps when a client and an internal account sit side by side. Paste the API key you copied and confirm.

First scenario

Your first scenario with Curator

GoalWhen a new row lands in a sheet from another app, Make creates a session in Curator.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Here that first module comes from another app, such as the spreadsheet where requests arrive.

  2. 02

    Set the starting module

    Search for that app, pick its trigger and link your account with Create a connection. Make then lists the files or sheets it can read, so choose the one that receives new requests.

  3. 03

    Add Create a Session

    Click the + on the right of the first module, search for Curator and choose Create a Session. Select your Curator connection, then map the data from the previous module into the fields Make shows.

  4. 04

    Test with Run once

    Add a test row, then click Run once. Open the bubble above each module to read the bundle it received, and check in Curator that the session exists with the right details.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set Scheduling. A new scenario runs every 15 minutes by default, which is also the shortest gap on the Free plan. Then switch the scenario on.

Triggers

What starts a Curator scenario

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

Curator1Watch Confirmations

Watch Confirmations

triggerIn the docs only

Watch Confirmations brings every new Curator confirmation into your scenario as its own bundle, so the next modules can act on it one by one.

How it fires
scheduled, a type inferred from the module's name since Make's directory gives no badge for it. Make checks the app on the scenario's schedule, which is every 15 minutes by default, so a confirmation shows up at the next check rather than the second it happens.
When to use it
when a new confirmation should reach someone or somewhere else, such as a message to the team or a row in a tracking sheet.
Watch out
the Make documentation does not describe what a confirmation contains. Run once on a real account and read the bundle before you map anything.
Modules

What the Curator modules do

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

Curator1

Create a Session

ActionIn the docs only

Create a Session adds a new session in Curator from data another module hands over, so nobody copies details by hand between tools.

When to use it
when a request captured elsewhere, in a form or a sheet, should turn into a Curator session.
Watch out
this action writes to your account every time the scenario runs. Test with Run once on a single row before you switch the scenario on, or a duplicate trigger can create duplicate sessions.
Curator2

Make an API Call

ActionIn the docs only

Make an API Call lets you reach any endpoint of the Curator API from your scenario, reusing the connection you already set up.

When to use it
when neither Watch Confirmations nor Create a Session covers what you need, and Curator's API documentation shows an endpoint that does.
Watch out
you write the request yourself here, so you need that API documentation open. Make's own docs do not describe the endpoints.
Need help

Need help automating Curator with Make?

A person reads every message.

FAQ

Questions about Curator and Make

01Is the Curator Make integration free?
Yes, on the Make side. Curator is a standard app, so it is available from the Free plan. That plan allows 2 active scenarios, runs of up to 5 minutes, a scheduled run every 15 minutes at the shortest, files up to 5 MB and 512 MB of data transfer. Paid plans go down to a 1 minute interval and allow unlimited active scenarios. Make counts usage in operations, one per module run on one bundle. You still need an active Curator account, which Curator bills on its own terms.
02What do you need to connect Curator to Make?
An active Curator account and its API key. In Curator, open the Integration section from the main menu, click API Access and copy the key shown. In Make, add any Curator module, click Create a connection, optionally name it, then paste the key. The same connection then serves all three Curator modules, including Make an API Call, so you only do this once per account. If the key changes in Curator, update it in the connection once.
03Does the Curator trigger react in real time?
No. Watch Confirmations is listed as a scheduled trigger, a type inferred from its name: Make checks Curator on the scenario's schedule instead of being called the moment something happens. A new scenario checks every 15 minutes by default, and 15 minutes is also the shortest interval on the Free plan. Paid plans can check as often as every minute. Curator has no instant trigger in Make, so a short delay between a confirmation and its handling is normal.
04What if a Curator module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Curator API with the connection you already have, so anything the API offers stays reachable even without a dedicated module. You will need Curator's API documentation to write the request. Also keep in mind that the Make documentation for Curator is AI-generated from Curator's docs and may contain mistakes, so verify important details with Curator. That way no endpoint is out of reach.
05Should you use Make or n8n with Curator?
It depends on the tool your team already uses. On Make, Curator offers three modules: a scheduled trigger for confirmations, an action to create a session and an API call for the rest. The same app often has an n8n node too. Compare the modules each side offers for your use case and pick the editor you are most comfortable building in. Neither choice changes what Curator itself can do.
Same platform

Other docs you might need on this stack.

Browse all integrations