Resources · Make integration

Macanta Make integrationAutomate Macanta with Make.

Keep your Macanta contacts current without typing them in by hand. The Macanta Make integration gives you 9 modules: 7 actions and 2 searches. This guide shows a CRM owner how to link the account and build a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Macanta Make integration let you do?

The integration links your Macanta account to Make, a visual tool where you build a scenario: an automation made of modules, each one a single brick such as an action or a search. With it, Make can create, find and update Macanta contacts and data objects based on what happens in your other apps.

Every web lead lands as a contact. A form app starts the scenario, then Create a Contact writes the person into Macanta. Nobody retypes a name or an email again.

Records stay in sync after a sale. When your billing tool marks a deal as won, Search Contacts finds the buyer and Update a Contact changes the fields your team relies on. For custom records, Create a Data Object and Update a Data Object do the same job.

Other tools read what Macanta knows. Get a Contact or Search Data Objects by Type and Contact ID pull details out so a later module can use them in an email or a report.

What Make cannot do here: Macanta has no trigger module, so a change inside Macanta never starts a scenario on its own. Something else has to kick it off, another app or the scenario schedule. Make also flags the Macanta documentation as limited, so expect to test each module with your own data. The Make troubleshooting guide helps when a run fails.

Many apps also have an n8n node; the n8n vs Make comparison sets the two tools side by side. To learn the editor properly first, see the Make training.

Connect

How do you connect Macanta to Make?

  1. 01

    Open the connection window

    Add any Macanta module to a scenario and click Create a connection. A connection is your Macanta account linked to Make once, then reused by all nine modules, so this happens only the first time.

  2. 02

    Name the connection

    Give it a label you will recognize later, such as the account owner or the team. This step is optional, but it saves guessing when several people link their own Macanta accounts in the same organization.

  3. 03

    Authorize and save

    Depending on what Make shows, either approve access on the Macanta page that opens or paste the key Macanta gives you. Then click Save. The module can now read your contacts and data objects.

First scenario

Your first scenario: update a Macanta contact from another app

GoalWhen another app sends you a person's details, Make finds that person in Macanta and updates the contact record.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Pick the app that holds the new information, for example your form tool, and choose its module.

  2. 02

    Add Search Contacts

    Click the + on the right, search for Macanta and pick Search Contacts. Click Create a connection if this is your first Macanta module, then map the detail from the previous app that identifies the person.

  3. 03

    Add Update a Contact

    Add Update a Contact after the search. Map the contact coming from Search Contacts, then fill only the fields you want to change with data from the first app.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time and shows the bundles each module received; a bundle is one item passed along, here one contact. Check the record in Macanta.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, which is also the shortest gap on the Free plan. Switch the scenario on and it keeps working.

Modules

What can each Macanta module do?

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

Macanta1

Create a Contact

ActionIn the docs only

You get a brand new person in Macanta, filled from whatever the previous module passed along, so leads stop living in inboxes and spreadsheets.

When to use it
a form app or a booking tool starts the scenario and each new submission should become a Macanta record.
Watch out
this module does not check for an existing record, so place Search Contacts before it when the same person may come back.
Macanta2

Create a Data Object

ActionIn the docs only

This one saves a new data object in Macanta, the custom records your account keeps next to contacts, without anyone opening the CRM to add it.

When to use it
an order, a signed agreement or a support request arrives in another app and deserves its own record rather than a note on the contact.
Watch out
the Macanta documentation is limited, so run it once on a test contact to see which fields Make offers.
Macanta3

Get Data Object via Item ID

ActionIn the docs only

Hand it an item ID and it returns that exact data object, ready for the next module to read and reuse in its own fields.

When to use it
an earlier step already stored the ID, for example in a spreadsheet row or a previous run, and you need the full record back.
Watch out
without the ID you cannot use it; Search Data Objects by Type and Contact ID is the way to locate records you cannot name.
Macanta4

Get a Contact

ActionIn the docs only

Pulling one known contact out of Macanta takes a single module, and its details become available for mapping in everything that follows.

When to use it
you already hold the contact reference from an earlier module and want fresh values before sending an email or writing to another tool.
Watch out
it fetches one precise record; when you do not hold its reference yet, start with Search Contacts instead.
Macanta5

Make an API Call

ActionIn the docs only

Anything the Macanta API offers beyond the eight ready-made modules becomes reachable here, using the same connection you already set up.

When to use it
the task you have in mind has no dedicated module, such as an endpoint the list above does not cover.
Watch out
you describe the request yourself, so you need the Macanta API reference at hand; the other modules fill fields for you, this one does not.
Macanta6

Search Contacts

SearchIn the docs only

Before you write anything, this search tells you whether a person already exists in Macanta and hands back the matching contacts for the next module.

When to use it
at the start of any flow that updates records, so a returning customer is updated instead of duplicated.
Watch out
a search can return zero, one or several bundles, and every bundle runs the modules after it, which costs one operation each time.
Macanta7

Search Data Objects by Type and Contact ID

SearchIn the docs only

Pick a data object type and a contact, and you receive every record of that type attached to the person, one bundle per record.

When to use it
a customer asks about their open requests and you want to list them in a reply or push them to a report.
Watch out
you need the contact ID first, so a Search Contacts step usually comes right before this module in the flow.
Macanta8

Update a Contact

ActionIn the docs only

Changes coming from other apps reach the existing Macanta record, so the contact your sales team opens always shows the latest details.

When to use it
a payment clears, an address changes in your shop, or a lead fills a second form and the record needs the new values.
Watch out
map only the fields you mean to change; test with Run once on a sample contact before switching the scenario on.
Macanta9

Update a Data Object

ActionIn the docs only

Status moves, new amounts or a closing date land on a data object that already lives in Macanta, with no manual edit inside the CRM.

When to use it
a project tool marks a job as delivered and the matching Macanta record should reflect it.
Watch out
the module needs to know which record to change, so fetch it first with Get Data Object via Item ID or the data object search.
Need help

Need help automating Macanta with Make?

A person reads every message.

FAQ

Common questions about Macanta and Make

01Is the Macanta Make integration free?
Yes, Macanta is a standard app in Make, so you can use it from the Free plan onward. The Free 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) bring the shortest gap down to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one per module run on one bundle.
02What do you need to connect Macanta to Make?
A Macanta account and a Make account are enough to get started. The Make documentation lists no extra prerequisite for this app. You add a Macanta module, click Create a connection, optionally name it, then either authorize Make on the Macanta page or paste the key Macanta provides, and save. The connection is created once and every Macanta module in your scenarios reuses it, so there is nothing to repeat when you add a second or third module.
03Can a change in Macanta start a Make scenario instantly?
No, Macanta has no trigger module in Make, neither scheduled nor instant. A scenario that uses Macanta has to start somewhere else. You can open it with a trigger from another app, such as a form or a billing tool, and it then fires whenever that app detects something. Or you can run it on the schedule set on the first module, every 15 minutes by default, and let a Macanta search collect what it needs each time.
04What if a Macanta module is missing in Make?
It depends on what you need. Make offers the Make an API Call module for Macanta, which lets you call any endpoint of the Macanta API from your scenario with the same connection. That covers most gaps in the 9 listed modules, as long as you can read the API reference. Keep in mind that Make describes its Macanta documentation as limited, so testing each module with Run once on sample data is the safest way to confirm what it returns.
05Should you use Make or n8n for Macanta?
It depends on the tool your team already knows. Make gives you 9 ready modules for Macanta, including Make an API Call for everything else, and a visual editor where each run can be tested with Run once. n8n often has a node for the same app, so check its node list for Macanta before choosing. Compare them on what matters to your case: the modules you need, how scenarios start and how usage is counted on your plan.