Resources · Make integration

Creatio Make integrationAutomate Creatio with Make.

Can Make keep your Creatio records up to date for you? The Creatio Make integration gives you 7 modules: 6 actions and 1 search. This guide shows you how to link your account, build a first scenario and pick the right module for each job.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Creatio Make integration do for you?

The Creatio Make integration links your Creatio account to Make, a visual tool where you build a scenario: a chain of modules that runs on a schedule or when another app calls Make. With it, data from your other tools lands in Creatio as new or updated records, and Creatio data can travel the other way, all without writing code.

Every new lead becomes a record. A form tool or a spreadsheet starts the scenario, and Create a Record writes the entry into the Creatio object you choose. Nobody copies fields by hand anymore.

Records stay in sync with the rest of your stack. Search Records finds the entry that matches your criteria, then Update a Record changes only what moved in the source tool. If you already route contacts through Airtable, the Airtable Make integration is a natural partner.

Creatio data feeds other apps. Get a Record reads one entry you point it to so a later module can post it to a chat channel or a sheet.

Know the limits before you start. Creatio has no trigger module in Make, so it cannot start a scenario on its own: something else has to kick things off, such as the schedule of the first module or another app. When a listed module falls short, Make an API Call reaches any endpoint of the Creatio API with the same connection. If you are weighing tools, the n8n vs Make comparison lays out the criteria, and the Make review covers the editor in depth.

Connect

How do you connect Creatio to Make?

  1. 01

    Open a Creatio module

    Log in to Make, add any Creatio module to your scenario, then click Create a connection. A connection is your Creatio account linked to Make once, and every Creatio module in your scenarios reuses it afterward.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear label pays off later. Something like the Creatio environment it points to helps when you run more than one account in the same Make organization.

  3. 03

    Enter your credentials

    Paste the credentials you copied from Creatio, or follow the on-screen instructions. You need an active Creatio account and either an OAuth token or forms authentication, as the Make documentation explains.

First scenario

Build your first scenario with Creatio

GoalWhen a new entry reaches another app, Make creates the matching record in Creatio.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since Creatio has no trigger, pick the app where your entries arrive, a form tool or a sheet for example.

  2. 02

    Add Create a Record

    Click the + on the right of that first module, search for Creatio and choose Create a Record. Click Create a connection if your account is not linked yet.

  3. 03

    Map the fields

    Once the connection exists, Make lists the Creatio objects it can read. Pick one, then drag values from the first module into the matching fields. Each bundle, meaning one item passing from module to module, becomes one record.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Read the bundles each module received, then check in Creatio that the record looks right.

  5. 05

    Schedule and switch on

    Set the schedule on the first module with the clock icon. A new scenario checks every 15 minutes by default. Then switch the scenario on so it keeps running without you.

Modules

Every Creatio module, explained

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

Creatio1

Create a Record

ActionIn the docs only

Adds a fresh entry to the Creatio object you select, filled with data mapped from earlier modules. It is the usual last step of any flow that feeds Creatio from outside.

When to use it
a web form, a signup list or an imported sheet produces people or deals that should exist in Creatio.
Watch out
if duplicates would hurt, run Search Records first to see whether the entry is already there.
Creatio2

Delete a Record

ActionIn the docs only

Removes one Creatio entry. Pair it with Search Records upstream so the scenario targets exactly the right item, not a lookalike.

When to use it
a contact is erased in your main tool and its copy in Creatio has to go too.
Watch out
it acts on real data, so test on a dummy record with Run once before switching the scenario on.
Creatio3

Get a Record

ActionIn the docs only

Fetches one entry you already know how to point to, and hands its values to the next module. Nothing is changed in Creatio.

When to use it
an earlier step identified a record and you need its details, say to write a message or fill a sheet row.
Watch out
it reads one known record; to find entries that match criteria, use Search Records instead. The doc lists no fields, so expect to identify the record, most likely by its ID (our reading).
Creatio4

Make an API Call

ActionIn the docs only

Lets you call any endpoint of the Creatio API from inside the scenario, reusing the connection you already created. It covers whatever the six ready-made modules leave out.

When to use it
you need an operation none of the other Creatio modules offer.
Watch out
here you build the request yourself, so keep the Creatio API documentation open and test each call with Run once before relying on it.
Creatio5

Search Records

SearchIn the docs only

Looks through a Creatio object and returns every entry that matches your criteria, each one as its own bundle. It is how a scenario finds the record to update, read or delete.

When to use it
before creating a contact, to check whether it is already in Creatio.
Watch out
the result can be zero, one or many entries, and every later module then runs once per bundle, which costs one operation each time.
Creatio6

Test Connection

ActionIn the docs only

As the name suggests, it checks that the link between Make and your Creatio account still answers. You get a quick signal without touching any record.

When to use it
after changing your credentials or OAuth settings in Creatio, to confirm the connection before a real scenario depends on it.
Watch out
it only proves access; it says nothing about whether your field mapping in other modules is correct.
Creatio7

Update a Record

ActionIn the docs only

Changes the values of an existing Creatio entry with fresh data from another tool. Your records stay current without manual edits.

When to use it
an order status or a phone number changes in another tool and Creatio should reflect it.
Watch out
it works on a record that already exists, so place Search Records upstream to find it and map what identifies it from there.
Need help

Need help automating Creatio with Make?

A person reads every message.

FAQ

Creatio and Make: frequent questions

01Is the Creatio Make integration free?
Yes, on the Make side. Creatio is a standard app, so it works on the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs and files up to 5 MB. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute and remove the cap on active scenarios. Make counts each module execution as an operation against your monthly credits. Your Creatio subscription is separate and depends on your contract with Creatio.
02What does it take to connect Creatio to Make?
An active Creatio account and a way to authenticate: either an OAuth token or forms authentication. For OAuth 2.0, you create an integrated application in the Creatio system designer, enter the callback URI given by Make, and copy the Client ID and Client secret. In Make, you then click Create a connection on any Creatio module, optionally name it, and paste those credentials. If the connection fails later, the Test Connection module tells you quickly whether access still works.
03Can Creatio start a Make scenario in real time?
No, not by itself. The Creatio app in Make has no trigger module, so the scenario has to start another way. The simplest option is to schedule the first module of the scenario, which runs every 15 minutes by default, or as often as every minute on a paid plan. The other option is to start from a trigger of another app, for example a form tool, and use the Creatio modules afterward.
04What if a Creatio module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Creatio API with the connection you already set up, so you are not limited to the six ready-made modules. Build the request with the Creatio API documentation at hand and test it with Run once. Note that the Make documentation for Creatio is flagged as AI-generated, so verify important details with Creatio directly. The same connection covers both the ready-made modules and your custom calls.
05Make or n8n for Creatio: which one fits?
It depends on the tool your team already knows. On Make, Creatio offers 7 modules covering create, read, update, delete and search, plus an API call module for the rest, and it is available from the Free plan. Many apps also have an n8n node, so check whether one exists for Creatio and compare what each covers for your exact use case before you commit. The n8n vs Make comparison linked above lays out the criteria side by side.