Resources · Make integration

VERSAT CRM Make integrationAutomate VERSAT CRM with Make.

Need orders and customers to land in VERSAT CRM without retyping them? The VERSAT CRM Make integration gives you 15 action modules and no trigger. This guide shows sales and ops teams how to connect the account, build a first scenario and pick the right module.

Try the VERSAT CRM integration on MakeSee the 15 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the VERSAT CRM Make integration automate?

The VERSAT CRM Make integration links your CRM account to Make, a visual tool where you chain modules into a scenario. A scenario is the automation you build; a module is one brick of it. VERSAT CRM brings 15 action modules for customers, orders, products, trade names and sales rep follow-up.

Orders that arrive already filed. When a shop or form app records a sale, Enviar Cliente and Enviar Pedido can carry the buyer and the order into VERSAT CRM, then Enviar Producto a un Pedido attaches the items.

A pipeline status that follows the field. Modificar Status de un Pedido lets another app, such as a delivery tool, move an order forward instead of someone updating it by hand.

Sales activity pulled out of the CRM. Obtener Check-in de Vendedores and Obtener Seguimiento de Clientes read what your reps logged so a sheet or a chat channel can show it.

Be aware of one real limit: Make's own documentation for VERSAT CRM is incomplete, and it gives no official description of the modules. Test every module with Run once before trusting it, and keep Make troubleshooting close. VERSAT CRM has no trigger in Make, so a schedule or another app has to start the scenario. Weighing the budget side? Read Make pricing, and if you are still choosing a platform, n8n vs Make lays out the criteria.

Connect

How do you connect VERSAT CRM to Make?

  1. 01

    Add a VERSAT CRM module

    In your scenario, click the + and search for VERSAT CRM. Pick any of its modules, then click Create a connection. A connection is your VERSAT CRM account linked to Make once and reused by every VERSAT CRM module.

  2. 02

    Name the connection

    Giving it a name is optional, but it helps later. If you manage two VERSAT CRM accounts, a clear label tells you at a glance which one a module writes to.

  3. 03

    Authorize Make and save

    Depending on what VERSAT CRM asks for, either approve Make on the app's own page or paste the key the app gives you. Then click Save and the module is ready to fill in.

First scenario

Your first scenario with VERSAT CRM

GoalWhen a sale is recorded in another app, Make creates the customer and then the order in VERSAT CRM.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since VERSAT CRM has no trigger, start with the app where your sales happen.

  2. 02

    Add Enviar Cliente

    Click the + on the right of the first module, search VERSAT CRM and choose Enviar Cliente. Click Create a connection if this is your first VERSAT CRM module.

  3. 03

    Map the buyer's details

    Fill the module fields by mapping data from the first module. Each bundle, meaning one item passing from one module to the next, carries one sale.

  4. 04

    Chain Enviar Pedido

    Click the + again and add Enviar Pedido. Map the order data from the first module and, where the form offers it, the result of Enviar Cliente.

  5. 05

    Test with Run once

    Click Run once and open the bundles each module received. Check in VERSAT CRM that the customer and the order both appeared as expected.

  6. 06

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on one bundle counts as one operation on your plan.

Modules

What each VERSAT CRM module does

VERSAT CRM gives you 15 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

VERSAT CRM1

Consultar Nombre Comercial

ActionIn the docs only

Going by its name, this module looks up a trade name stored in VERSAT CRM, so the next module can reuse it instead of you typing the brand by hand. Make publishes no description for it.

When to use it
before sending an order for a client that sells under a different brand than its legal name.
Watch out
run it once and read the output bundle to see exactly what it returns.
VERSAT CRM2

Enviar Cliente

ActionIn the docs only

This is the module that gets a new customer into VERSAT CRM from another tool, judging by its name (send customer). It saves the double entry between your shop, form or quote app and the CRM.

When to use it
right after a first purchase or a signed quote, as the opening VERSAT CRM step of the scenario.
Watch out
nothing in the documentation says whether it checks for duplicates, so test with a customer who already exists.
VERSAT CRM3

Enviar Nombre Comercial

ActionIn the docs only

You get a trade name recorded in VERSAT CRM without opening the app, since the name reads as send trade name. Handy when brands are managed somewhere else first.

When to use it
when a new brand or point of sale is added in your master list and the CRM has to follow.
Watch out
the documentation gives no field list, so let Make show you what the module asks for once the connection exists.
VERSAT CRM4

Enviar Pedido

ActionIn the docs only

Orders stop being retyped: by its name, this module sends an order into VERSAT CRM from whatever app captured the sale. It is the natural centerpiece of an order scenario.

When to use it
when a checkout, a signed quote or a sales form produces a confirmed order.
Watch out
place it after Enviar Cliente if the order needs an existing customer, and confirm that with Run once.
VERSAT CRM5

Enviar Producto

ActionIn the docs only

Your catalog can stay in step with the CRM: the name points to a module that sends a product into VERSAT CRM. Your reps then find the same items they see in your stock or shop tool.

When to use it
when a new product is created in the tool that owns your catalog.
Watch out
this is not the module for adding an item to an order; that job belongs to Enviar Producto a un Pedido.
VERSAT CRM6

Enviar Producto a un Pedido

ActionIn the docs only

An order gets its lines: as the name says, this module adds a product to an order that already sits in VERSAT CRM. It completes what Enviar Pedido started.

When to use it
when a sale holds several items and each one has to appear on the order.
Watch out
each item is its own bundle, so every added line costs one operation; count them before you switch the scenario on.
VERSAT CRM7

Escuchar Clientes

ActionIn the docs only

This module should hand you customers from VERSAT CRM, since escuchar means listen. It is listed as an action though, not a trigger, so it cannot start a scenario by itself.

When to use it
after a scheduled start, when another tool needs the customer base.
Watch out
test it with Run once to learn what it really outputs.
VERSAT CRM8

Escuchar Pedidos

ActionIn the docs only

Orders held in VERSAT CRM become usable elsewhere, for example in a shipping or invoicing tool. That reading comes from the name only; the module is listed as an action, not as a trigger.

When to use it
when your warehouse or accounting app has to see the orders your reps entered.
Watch out
without a description, check in the output of Run once whether it returns one order or many before mapping it.
VERSAT CRM9

Escuchar Productos

ActionIn the docs only

The product list of VERSAT CRM can feed another tool through this module, going by its name. Useful when the CRM is where your team maintains prices or references.

When to use it
when a price list, a sheet or a shop has to mirror the products stored in the CRM.
Watch out
it is listed as an action, so the scenario needs a schedule or another app ahead of it to run.
VERSAT CRM10

Hacer una Llamada API

ActionIn the docs only

This is VERSAT CRM's own API call module, judging by its Spanish name. It gives you a way to reach a feature that no other module of the app covers, provided you know the VERSAT CRM API.

When to use it
only after checking that no ready-made module does the job.
Watch out
the documentation says nothing about the API itself, so you need VERSAT CRM's own technical reference to fill it in.
VERSAT CRM11

Listar Clientes

ActionIn the docs only

Here you get a list of customers from VERSAT CRM, which the name spells out. A list usually means several bundles leaving the module, one per customer, and every following module then runs once for each of them.

When to use it
when you need to copy or review the whole customer base in a sheet.
Watch out
a long list multiplies operations downstream, so test on a small account first.
VERSAT CRM12

Modificar Status de un Pedido

ActionIn the docs only

An order moves forward in VERSAT CRM without anyone opening it: the name describes changing an order's status. Delivery, payment or approval can then update the CRM on their own.

When to use it
when a payment clears or a parcel ships in another tool and the order should reflect it.
Watch out
a status change is hard to spot if it goes wrong, so run it once on a test order and check the result.
VERSAT CRM13

Obtener Check-in de Vendedores

ActionIn the docs only

Managers get the check-ins of their sales reps out of VERSAT CRM, if the name is a fair guide. That data can then reach a report, a sheet or a team chat.

When to use it
when field visits logged in the CRM have to show up in the tool your managers already read.
Watch out
the documentation gives no detail on what a check-in contains, so read the bundle from Run once before building on it.
VERSAT CRM14

Obtener Seguimiento de Clientes

ActionIn the docs only

Follow-up notes on customers leave VERSAT CRM through this module, going by its name (get customer follow-up). It is a way to share the account history with people who never open the CRM.

When to use it
when support or finance needs the latest contact with a customer before acting.
Watch out
check whether it returns one entry or several per customer before mapping it.
VERSAT CRM15

Obtener un Cliente por ID

ActionIn the docs only

One precise customer record comes back when you give its ID, as the name states. It is the tidy choice when the previous module already knows which customer is concerned.

When to use it
after an order or a follow-up, to fetch the full customer before writing an email or an invoice elsewhere.
Watch out
map the ID from a module that surely has it, then test an unknown ID with Run once to see how the module reacts.
Need help

Need help automating VERSAT CRM with Make?

A person reads every message.

FAQ

VERSAT CRM and Make: common questions

01Is the VERSAT CRM Make integration free?
Yes, VERSAT CRM is a standard app in Make, so it works on the Free plan. That plan has 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) lower the interval to 1 minute and allow unlimited active scenarios. Usage is counted in operations, one per module run on one bundle. The price of VERSAT CRM itself is a separate matter.
02What do you need to connect VERSAT CRM to Make?
A VERSAT CRM account and a Make account. Make's documentation lists no specific prerequisite and no official steps for this app, so the generic Make flow applies: add a VERSAT CRM module, click Create a connection, optionally name it, then authorize Make on the app's page or paste the key the app provides, and click Save. The same connection then serves all 15 modules. If a step does not match what you see, the account settings on the VERSAT CRM side are the first place to look.
03Does VERSAT CRM trigger Make scenarios in real time?
No, because VERSAT CRM has no trigger module in Make, neither scheduled nor instant. A scenario that uses it has to start another way. The first option is a schedule on the first module, every 15 minutes by default, with a Free plan floor of 15 minutes and 1 minute on paid plans. The second is to open the scenario with a trigger from another app, such as your shop or your form tool, and then call the VERSAT CRM modules that write or read the data.
04What if a VERSAT CRM module is missing in Make?
It depends on what you need. VERSAT CRM does not get Make's universal Make an API Call module, but it ships its own module named Hacer una Llamada API, which appears to be meant for calls beyond what the ready-made modules cover. Using it requires the VERSAT CRM API reference, which Make does not document. Make itself warns that its documentation for this app is limited. If that gets in the way, another app can hold the data, or the team can help you scope the build.
05Should you use Make or n8n with VERSAT CRM?
It depends on your criteria, not on a winner. On the Make side, the facts are clear: VERSAT CRM has 15 action modules, no trigger, works on the Free plan and has limited documentation. Many apps also have an n8n node, so check whether VERSAT CRM does before comparing. Then weigh which editor your team already knows, how you want to start scenarios given the missing trigger, and how you plan to test modules that lack an official description.
Same platform

Other docs you might need on this stack.

Browse all integrations