Vtiger to WhatsApp, greet every new lead fast
New lead comes in. You mean to reply fast. Then a call runs long, Slack pings, and suddenly “quick follow-up” turns into tomorrow.
This Vtiger WhatsApp automation hits sales reps first, honestly. But CRM admins cleaning up messy records and founders trying to keep leads warm feel it too. The outcome is simple: every new lead gets a welcome message quickly, without you babysitting the process.
You’ll see how the workflow checks Vtiger for uncontacted leads, sends a personalized WhatsApp greeting, and marks the lead so it never double-sends.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Vtiger to WhatsApp, greet every new lead fast
flowchart LR
subgraph sg0["Scheduled Minute Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Scheduled Minute Trigger", pos: "b", h: 48 }
n1@{ icon: "mdi:cog", form: "rounded", label: "Fetch Latest Vtiger Lead", pos: "b", h: 48 }
n2@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Lead Result Check", pos: "b", h: 48 }
n3@{ icon: "mdi:cog", form: "rounded", label: "Mark Lead WhatsApp Sent", pos: "b", h: 48 }
n4@{ icon: "mdi:web", form: "rounded", label: "Dispatch WhatsApp Greeting", pos: "b", h: 48 }
n5@{ icon: "mdi:cog", form: "rounded", label: "No Action Handler", pos: "b", h: 48 }
n1 --> n2
n2 --> n3
n2 --> n4
n2 --> n5
n0 --> n1
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
class n2 decision
class n4 api
The Problem: New leads go cold while you “get to it”
Speed-to-lead is one of those things everyone agrees matters, but almost nobody executes perfectly. Vtiger captures the lead, then the real world happens. Someone has to notice the new record, copy the phone number, open WhatsApp, paste a message, and remember to log it. Miss a few and your follow-up looks sloppy. Worse, you get the awkward moment where two people message the same lead because there’s no single “we already greeted them” signal in the CRM.
It adds up fast. Here’s where it breaks down in day-to-day work.
- New leads sit uncontacted for hours because nobody is watching Vtiger every minute.
- Manual WhatsApp messages get inconsistent, so your first touch feels different depending on who sent it.
- Teams end up sending duplicate greetings when the CRM doesn’t clearly show “already messaged.”
- Copy-pasting phone numbers invites mistakes, and one wrong digit is a lost conversation.
The Solution: Vtiger → WhatsApp instant welcome, automatically
This workflow runs quietly in the background and handles that first hello for you. Every minute, n8n checks Vtiger for the latest lead that has not been marked as “messaged” yet (using a custom field, like cf_1090). If it finds one, it pulls the lead’s name and phone number, then sends a personalized WhatsApp greeting through Evolution API. Right after sending, it updates the same lead record in Vtiger to mark it as “WhatsApp sent,” which prevents repeats. If there’s no eligible lead, the workflow simply does nothing and waits for the next check.
The workflow starts on a scheduled trigger (every minute). Then Vtiger is queried for a lead that matches your “uncontacted” rule. Finally, Evolution API delivers the WhatsApp message and Vtiger gets updated so your pipeline stays clean.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you get about 20 new leads a day. Manually sending a WhatsApp greeting often takes around 5 minutes per lead once you find the record, copy the phone, paste a message, and note it in Vtiger, which is about 100 minutes daily. With this workflow, the “work” is basically zero after setup: Vtiger is checked every minute, the message sends automatically, and the lead is marked as contacted. You’re getting back roughly 1–2 hours a day, and replies start coming in while you’re doing other things.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Vtiger CRM to store and fetch new leads.
- Evolution API to send WhatsApp messages programmatically.
- Vtiger CRM API credentials (get them from your Vtiger user/API settings).
Skill level: Intermediate. You’ll connect credentials, add a custom field in Vtiger, and you must enable community nodes on a self-hosted n8n.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A scheduled check kicks it off. n8n runs this workflow every minute, so new leads don’t wait for someone to notice them.
Vtiger is queried for the “next” unmessaged lead. The workflow fetches the most recent lead where your custom field indicates WhatsApp has not been sent yet (for example, cf_1090 != 1).
A quick decision prevents noise. If no lead is returned, a “no action” path runs and nothing else happens. If a lead is found, the workflow continues with message sending and record updates.
Evolution API sends the WhatsApp greeting and Vtiger gets updated. The message uses the lead’s firstname/lastname, then the workflow marks the record as “sent” so the next run doesn’t greet the same person again.
You can easily modify the message template to match your brand voice based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Scheduled Minute Trigger
Set up the workflow to run every minute so new leads are checked continuously.
- Add the Scheduled Minute Trigger node as the workflow trigger.
- Set the schedule rule to run every minute by configuring minutesInterval to
1. - Connect Scheduled Minute Trigger to Fetch Latest Vtiger Lead.
Step 2: Connect Vtiger and Fetch the Latest Lead
Pull the most recent lead that has not yet been marked as WhatsApp contacted.
- Add the Fetch Latest Vtiger Lead node.
- Credential Required: Connect your vtigerApi credentials.
- Set query_field to
select * from Leads where cf_1090!=1 order by id desc limit 1;. - Ensure Fetch Latest Vtiger Lead outputs to Lead Result Check.
Step 3: Add the Lead Result Check
Only proceed when a valid lead is returned from Vtiger.
- Add the Lead Result Check node.
- Configure the condition to check that leftValue is not empty with
={{ $json.result[0].id }}. - Connect the “true” output to both Mark Lead WhatsApp Sent and Dispatch WhatsApp Greeting.
- Connect the “false” output to No Action Handler.
Lead Result Check outputs to both Mark Lead WhatsApp Sent and Dispatch WhatsApp Greeting in parallel.
Step 4: Configure WhatsApp Send and Vtiger Update Actions
Send the WhatsApp greeting and immediately mark the lead as contacted.
- Add the Mark Lead WhatsApp Sent node.
- Credential Required: Connect your vtigerApi credentials.
- Set operation to
update. - Set element_field to
={ "cf_1090": "1" }. - Set webservice_id_field to
={{ $json.result[0].id }}. - Add the Dispatch WhatsApp Greeting node.
- Credential Required: Connect your evolutionApi credentials.
- Set resource to
messages-api. - Set remoteJid to
={{ $json.result[0].phone }}. - Set messageText to
=Hi {{ $json.result[0].firstname }} {{ $json.result[0].lastname }} 😊, We have received your interest with our services and we well contact you soon. Have a nice day 🙏💐. - Set instanceName to
Ahmed560.
No Action Handler exists as a placeholder path when no lead is found; it performs no actions.
Step 5: Test & Activate Your Workflow
Validate the end-to-end flow before turning it on in production.
- Click Execute Workflow to run a manual test.
- Confirm Fetch Latest Vtiger Lead returns a lead with
cf_1090!=1. - Verify Mark Lead WhatsApp Sent updates the lead and Dispatch WhatsApp Greeting sends a WhatsApp message.
- Toggle the workflow to Active to enable the every-minute schedule.
Common Gotchas
- Vtiger CRM credentials can expire or need specific permissions. If things break, check your Vtiger API/user settings and the credential record inside n8n first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Frequently Asked Questions
Plan on about an hour if Vtiger and Evolution API are ready.
No. You’ll connect credentials, set a custom field, and edit the message text. The only “technical” part is running self-hosted n8n with community nodes enabled.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Evolution API costs (your hosting or subscription).
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and you should. Most people tweak the WhatsApp message inside the Evolution API “Dispatch WhatsApp Greeting” node, then adjust the schedule so it runs every few minutes instead of every minute if they want fewer checks. You can also change the “uncontacted” rule in the Vtiger fetch node (the filter using your custom field like cf_1090). Some teams add a second condition so only leads from certain sources get the WhatsApp greeting.
Usually it’s expired or incorrect API credentials in the n8n Vtiger node. Re-check the base URL, username/token, and that the Vtiger user has API access. If it fails only sometimes, it can be rate limits or a temporarily slow Vtiger instance, so adding a simple retry or lowering how often you poll can help.
A lot, as long as your Vtiger and Evolution API can keep up.
For this specific CRM WhatsApp use case, n8n is often the practical choice because you can self-host, run community nodes (like the Vtiger and Evolution API nodes), and avoid paying extra for multi-branch logic. Zapier and Make are great when everything you need is a built-in, supported app and the flow is simple. Here, the “no duplicates” behavior depends on updating a field in Vtiger and making decisions based on it, which is easier to control in n8n. Also, WhatsApp automation frequently needs a provider like Evolution API, and that’s a smoother fit in n8n with HTTP/community nodes. Talk to an automation expert if you want help choosing the simplest stack for your volume.
Once this is running, new leads get greeted on time, and your team stops doing the same small task 20 times a day. The workflow handles the repetitive part so you can focus on actual conversations.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
