Resources · Make integration

Vtiger CRM Make integrationAutomate Vtiger CRM with Make.

Can your CRM records move on their own once a deal or contact changes? The Vtiger CRM Make integration gives you 7 modules: 1 trigger, 5 actions and 1 search. This guide is for sales and ops teams, and it walks you from the connection to a first working scenario.

Try the Vtiger CRM integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Vtiger CRM Make integration do for you?

The Vtiger CRM Make integration links your CRM account to Make, so records can be created, read, updated, searched or deleted by a scenario, the automation you build in Make, instead of by hand. Each step of that scenario is a module, and one trigger can start it whenever a record is created or updated.

Fewer copy and paste jobs. A lead that lands in a form tool or a spreadsheet can become a Vtiger record through Create a Record, with no one retyping names and emails.

Other tools that stay in step with the CRM. Watch Records picks up records that were just created or edited, so a scenario can push those changes to your reporting sheet or your team chat.

Clean lookups before you write. Search Records finds records that match your criteria, and Update a Record then edits the right one instead of adding a duplicate.

What the app does not offer: no instant trigger, so changes are picked up on the scenario's schedule. When a listed module falls short, Make an API Call reaches the rest of the Vtiger API with the same connection. If you are weighing tools, the n8n vs Make comparison lays out the criteria, the Make pricing page covers plans, and the Make training helps you go further.

Connect

How do you connect Vtiger CRM to Make?

  1. 01

    Get your access key in Vtiger

    In Vtiger CRM, open the user menu at the top right, then My Preferences. Click the More icon on your user record, pick Change Access Key, confirm with yes, and copy the API key shown on the preferences page.

  2. 02

    Add a Vtiger CRM module in Make

    In your scenario, add any Vtiger CRM module and click Create a connection. The Connection name field is optional; a clear label helps once several accounts share the same Make organization.

  3. 03

    Paste the credentials and save

    Enter the credentials copied from your Vtiger account, or follow the on-screen instructions, then save. This connection, your Vtiger account linked to Make once, is reused by every Vtiger module you add later.

First scenario

Build your first scenario with Vtiger CRM

GoalWhen a new lead arrives in another app, Make creates the matching record in Vtiger CRM.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. That first brick is the app where your leads arrive, such as a form tool.

  2. 02

    Add Create a Record

    Click the + to the right of that first module, search for Vtiger CRM, pick Create a Record and select your connection. Make then lists the Vtiger modules it can read.

  3. 03

    Map the lead's data

    Choose the record type, then drag the name, email or company from the previous module into the matching fields. Each lead flows through as a bundle, one item passed from module to module.

  4. 04

    Test with Run once

    Click Run once, send a test lead, and read the bundles each module received. Check in Vtiger that the new record looks right.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default) and turn the scenario on. From now on, each run counts operations, one per module per bundle, on your Make plan.

Triggers

What starts a Vtiger CRM scenario

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

Vtiger CRM1Watch Records

Watch Records

Scheduled trigger

In Make“Triggers when a record is created or updated.”

Watch Records gives your scenario a steady feed of Vtiger records that were just created or edited, so the rest of the flow always works on fresh data. Every matching record arrives as its own bundle.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and 15 minutes at the shortest on the Free plan.
When to use it
a sales team that wants each updated deal or new contact copied to a reporting sheet.
Watch out
new and edited records both come through, so the next modules must be fine handling either kind.
Modules

What each Vtiger CRM module does

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

Vtiger CRM1

Create a Record

Action

In Make“Creates a new record.”

Create a Record adds a fresh entry to the Vtiger module of your choice, filled with data coming from earlier steps, so nobody retypes it by hand.

When to use it
a signup, a quote request or a spreadsheet row that should become a lead or a contact in the CRM.
Watch out
it never checks for an existing twin, so place Search Records before it when duplicates are a risk.
Vtiger CRM2

Delete a Record

Action

In Make“Deletes a record.”

Delete a Record removes one Vtiger record, which keeps the CRM tidy when another system says an entry no longer exists.

When to use it
a test record created while building, or an entry cancelled in the tool that feeds your CRM.
Watch out
none of the Vtiger modules restores a deleted record, so test it with Run once on a dummy record before you switch the scenario on.
Vtiger CRM3

Get a Record

Action

In Make“Return the data of a specified record of selected module.”

Get a Record returns the full data of one record you already know, in the module you select, so later steps can use every value it holds.

When to use it
another app hands you a record reference and you need the rest of its details before writing an email or a document.
Watch out
it needs a precise record; when you only know a name or an email, start with Search Records.
Vtiger CRM4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call opens the rest of the Vtiger API to your scenario while reusing the connection you already set up, so you are not limited to the six ready-made modules.

When to use it
a task none of the listed modules covers and that the Vtiger API documents.
Watch out
you write the request yourself, so keep the Vtiger API documentation open and test each call with Run once.
Vtiger CRM5

Update a Record

Action

In Make“Updates an existing record.”

Update a Record edits a record that already exists in Vtiger, which keeps the CRM aligned with what happens in your other tools.

When to use it
a payment confirmed in your billing app should move the deal forward, or a new phone number should reach the contact card.
Watch out
pairing it with Watch Records on the same module can make the scenario pick up its own edits.
Vtiger CRM6

Search Records

Search

In Make“Retrieves records of selected module that match specified criteria.”

Search Records finds the Vtiger records of a module that match the criteria you set, which tells your scenario whether a person or a deal is already in the CRM.

When to use it
before creating a lead, to check whether that email is already there and update it instead.
Watch out
it can return zero, one or several bundles, and every module that follows runs once per bundle.
Need help

Need help automating Vtiger CRM with Make?

A person reads every message.

FAQ

Vtiger CRM and Make: common questions

01Is the Vtiger CRM Make integration free?
Yes, on the Make side. Vtiger CRM is a standard app, available from the Free plan onward. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and count usage in credits per month. You still need your own active Vtiger CRM account, whose subscription is handled on the Vtiger side.
02What do you need to connect Vtiger CRM to Make?
An active Vtiger CRM account with API access, and its access key. In Vtiger, open your preferences from the user menu, click the More icon on your user record and choose Change Access Key. Confirm, then copy the key shown on the preferences page. In Make, add any Vtiger CRM module, click Create a connection, give it a name if you like, and paste the credentials. Every Vtiger module in your scenarios then reuses that same connection.
03Does the Vtiger CRM trigger in Make work in real time?
No. Watch Records is a scheduled trigger: Make checks Vtiger on the scenario's schedule rather than being alerted the moment a record changes. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans can go down to 1 minute. Vtiger CRM has no instant trigger in Make, so a shorter schedule is the way to pick up changes sooner.
04What if a Vtiger CRM module is missing in Make?
Use Make an API Call. It sends any request the Vtiger API supports and reuses the connection you already created, so there is nothing new to authorize. That covers actions the six other modules do not offer. Note that the Make documentation for this app carries a warning: it was drafted with AI from the official Vtiger documentation, so check important details with Vtiger directly before a scenario relies on them in production.
05Should you use Make or n8n for Vtiger CRM?
It depends on your criteria. On Make, Vtiger CRM comes with 7 ready modules: a scheduled trigger, five actions including a generic API call, and a search. That covers most record work without code. n8n often has a node for the same app, so compare what each one exposes for your use case and which editor your team prefers. Neither choice is wrong; the deciding factor is the modules you actually need.
Same platform

Other docs you might need on this stack.

Browse all integrations