Resources · Make integration

Magentrix Make integrationAutomate Magentrix with Make.

Can Make keep your Magentrix records and documents moving without code? The Magentrix Make integration gives you 10 modules: 3 scheduled triggers and 7 actions. This guide is for CRM and sales teams, and walks you from the connection to a first working scenario.

Try the Magentrix integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Magentrix Make integration let you automate?

The Magentrix Make integration links your Magentrix account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules. Each module is one brick of that chain. Here, three of them watch Magentrix for new records, changed records and new documents, and seven act on your data.

Feed Magentrix from your other tools. A lead captured in a form or a spreadsheet can land in Magentrix through Create a Record, so nobody retypes it. If the contact already exists, Universal Search helps you look before you write, and Update a Record completes the entry instead of duplicating it.

Keep documents in sync. Watch New Documents spots files added in Magentrix, Download a Document pulls the file into the scenario, and the next module can store it wherever your team works. The other way round, Upload a Document pushes a signed file from another app back to Magentrix.

React to changes in the CRM. Watch Updated Records starts a scenario when an entry changes, which is handy for alerting a sales rep or copying the change into a reporting sheet. Each item that flows between modules is called a bundle.

What Make does not give you: a detailed Magentrix guide. Make states that its documentation for this app is limited because too little public information exists. When a listed module falls short, Make an API Call reaches the rest of the Magentrix API with the same connection. The Make troubleshooting guide helps when a run fails, and Make pricing explains how operations are counted.

Magentrix may also exist as an n8n node. To weigh both tools on your own criteria, read n8n vs Make.

Connect

How do you connect your Magentrix account to Make?

  1. 01

    Add a Magentrix module

    In your scenario, click the +, search for Magentrix and pick any module. Then click Create a connection. A connection is your Magentrix account linked to Make once, and every Magentrix module reuses it afterwards.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it pays off once you manage more than one Magentrix account from the same Make workspace. Pick something your colleagues will recognize when they open the scenario later.

  3. 03

    Authorize and save

    Depending on what Magentrix asks, either approve access on the Magentrix page that opens, or paste the key Magentrix gives you. Click Save. Make can now list the Magentrix data it is allowed to read.

First scenario

Build your first scenario with Magentrix

GoalWhen a lead arrives from another app, Make creates the matching record in Magentrix.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the app where your leads start, such as your form tool, and its trigger module.

  2. 02

    Add Create a Record

    Click the + on the right of the first module, search Magentrix and choose Create a Record. Select your connection, or click Create a connection if this is your first Magentrix module.

  3. 03

    Map the lead data

    Once connected, Make lists the Magentrix objects it can read. Choose where the record goes, then drag the values from the first module into the matching fields.

  4. 04

    Test with Run once

    Click Run once and send a test lead. Each module shows the bundles it received. Open Magentrix and check that the record appeared with the right values before going further.

  5. 05

    Schedule and switch on

    On the first module, set the schedule, every 15 minutes by default, then switch the scenario on. Remember the Free plan runs scheduled scenarios at most every 15 minutes.

Triggers

What can start a Magentrix scenario?

3 modules start a scenario when something happens in Magentrix. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Magentrix as soon as it happens.

Magentrix1Watch New Documents

Watch New Documents

triggerIn the docs only

You get a scenario that wakes up when a document shows up in Magentrix, so a file your team adds can be copied, shared or archived without anyone forwarding it by hand.

How it fires
scheduled, Make checks Magentrix on the scenario's schedule, so a new document is picked up at the next check rather than the instant it lands.
When to use it
a partner portal where customers drop contracts that your back office needs elsewhere.
Watch out
pair it with Download a Document whenever the next app needs the file itself to store or send it.
Magentrix2Watch New Records

Watch New Records

triggerIn the docs only

This one hands you every fresh Magentrix entry as a bundle, ready to be sent to your email tool, a sheet or a chat channel, which saves you from exporting lists to find out what is new.

How it fires
scheduled, Make checks Magentrix on the scenario's schedule and collects the records created since the previous check.
When to use it
welcoming a new account or alerting the owner when a new lead appears in the CRM.
Watch out
a first Run once may return several records at once; look at the bundles before you switch the scenario on.
Magentrix3Watch Updated Records

Watch Updated Records

triggerIn the docs only

Here you get a signal whenever an existing Magentrix record is modified, which lets a scenario follow a deal or a case through its life instead of only at creation.

How it fires
scheduled, Make checks Magentrix on the scenario's schedule and passes on the records edited since the last check.
When to use it
copying a stage change into a reporting sheet, or warning a manager when an account is edited.
Watch out
avoid ending the same scenario with Update a Record on that record, since your own edit would be picked up again at the next check.
Modules

What can Make do in Magentrix?

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

Magentrix1

Create a Record

ActionIn the docs only

With this module, data from another app becomes a new Magentrix entry, so a lead or an order never has to be typed twice into the CRM.

When to use it
a web form or a sales spreadsheet that should feed Magentrix directly.
Watch out
run Universal Search first when the same person could already exist, or you will create duplicates.
Magentrix2

Delete a Record

ActionIn the docs only

You get a clean CRM by letting a scenario remove a Magentrix entry that should no longer be there, such as a test contact or a record flagged elsewhere as obsolete.

When to use it
after a cleanup decision made in another tool that Magentrix should mirror.
Watch out
a deletion cannot be undone from Make, so test on a dummy record with Run once first.
Magentrix3

Download a Document

ActionIn the docs only

The result is the actual file from Magentrix inside your scenario, which the next module can save to a drive, attach to an email or send for signature.

When to use it
right after Watch New Documents, when a copy has to live outside the CRM.
Watch out
on the Free plan Make handles files up to 5 MB, so a heavy document may need a paid plan.
Magentrix4

Make an API Call

ActionIn the docs only

This gives you access to any Magentrix API endpoint the other modules do not cover, using the connection you already set up, so you are not stuck when a feature is missing.

When to use it
an operation your team needs that no listed module offers.
Watch out
you write the request yourself, and Make's Magentrix documentation is limited, so rely on the Magentrix API reference.
Magentrix6

Update a Record

ActionIn the docs only

You keep a Magentrix entry accurate by changing it from a scenario, whether the new value comes from a billing tool, a support desk or a spreadsheet.

When to use it
a payment or a status change in another app that the sales team should see in the CRM.
Watch out
you need the record's identifier, usually mapped from a search or a trigger placed earlier in the scenario.
Magentrix7

Upload a Document

ActionIn the docs only

This module puts a file from any other app into Magentrix, so a signed quote or an invoice ends up where your sales team already looks for it.

When to use it
when an e-signature tool or a mailbox receives a file that belongs to a CRM account.
Watch out
map the file from the previous module, and keep the Free plan's 5 MB file limit in mind.
Need help

Need help automating Magentrix with Make?

A person reads every message.

FAQ

Magentrix and Make: frequent questions

01Is the Magentrix Make integration free?
Yes, Magentrix is a standard app in Make, so it is available from the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, caps each run at 5 minutes, handles files up to 5 MB and includes 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Usage is counted in operations, one per module per bundle.
02What does the Magentrix Make integration need to connect?
You need a Magentrix account and a Make account. Make's documentation lists no special prerequisite for this app and gives no dedicated connection steps, so the generic flow applies: add a Magentrix module, click Create a connection, optionally name it, then authorize Make on the Magentrix page or paste the key Magentrix provides, and click Save. If your portal restricts access, ask your Magentrix administrator which method is allowed before you start building.
03Does the Magentrix trigger react in real time?
No. The three Magentrix triggers, Watch New Documents, Watch New Records and Watch Updated Records, are scheduled triggers. Make checks Magentrix on the scenario's schedule, every 15 minutes by default, and picks up whatever changed since the previous check. On a paid plan the interval can go down to 1 minute. None of them is an instant trigger, which would need Magentrix to call Make through a webhook the moment something happens.
04What if a Magentrix module is missing in Make?
Use Make an API Call. It calls any endpoint of the Magentrix API with the connection you already created, so you can reach features the 7 actions do not cover. Keep in mind that Make says its Magentrix documentation is limited, because too little public information about the app exists. You will therefore rely on the Magentrix API reference to build the request, and test it with Run once before switching the scenario on.
05Make or n8n for Magentrix: which one fits?
It depends on your criteria. On the Make side, Magentrix comes with 10 ready modules, 3 scheduled triggers and 7 actions, plus Make an API Call for the rest, and it works from the Free plan. The same app often has an n8n node as well. Compare the modules each tool offers for your exact use case, the way each counts usage, and which editor your team is more comfortable with, then test a small scenario in the tool you lean toward.
Same platform

Other docs you might need on this stack.

Browse all integrations