WhatsApp message auto-logger for Vtiger CRM with lead relation
Auto-Log WhatsApp Inbound Messages to Vtiger CRM Leads (with WhatsAppLog)
Description
π₯ A Game-Changer for CRM Logging! Automatically Log WhatsApp Inbound Messages to Vtiger and Link to Leads π¬β‘ β οΈ This Workflow Requires Community Nodes & a Self-Hosted n8n Instance
> This template uses a custom community node:
> * n8n-nodes-vtiger-crm
> β
No need for an Evolution API node β webhook is used instead.
π§ How to Install Community Nodes
Go to Settings β Community Nodes Click Install Node Add this:
n8n-nodes-vtiger-crm
Restart n8n if prompted.
π¬ Automatically Log WhatsApp Inbound Messages in Vtiger CRM
Overview
This workflow listens for inbound WhatsApp messages via Evolution API Webhook, filters out outbound and group messages, and logs the message in the custom WhatsAppLog module in Vtiger. If the sender is not in CRM, it creates a new lead and links the message.
π What This Workflow Does
π© Listens to WhatsApp inbound messages via webhook
π« Filters out group and outbound messages
π Looks up existing lead by phone
π Creates a new lead if not found
π§Ύ Logs the message in the WhatsAppLog module
π Relates message to corresponding lead
π Evolution API Webhook Configuration
- Open your Evolution API dashboard
- Go to
Events β Webhook - Enable Webhook
- Set the Webhook URL to your n8n webhook path:
https://your-n8n-domain/webhook/whatsAppListen - Enable only the event:
β
MESSAGES_UPSERT - Disable all other events to avoid unnecessary triggers
This ensures only inbound WhatsApp messages are pushed to n8n.
> No need to use the Evolution API node in n8n. All communication is triggered via webhook.
πΈ Visual Preview
π§© Workflow Canvas
> Full view of the automation steps in n8n
π¬ WhatsApp Message Capture
> A sample inbound message sent to your WhatsApp number
π οΈ Setup Instructions
1. Vtiger CRM Setup
- Ensure the
Leadsmodule has phone fields (phone or mobile) - Create a custom module
WhatsAppLog(if not already present) - Connect your Vtiger CRM API credentials to n8n
2. Webhook Setup
- Follow the Webhook Configuration steps above for Evolution API
- Make sure your n8n instance is publicly accessible
3. Workflow Customization
- Update field mapping inside the
SetandLognodes - Adjust the
assigned_user_idor custom fields as needed
π₯ Who Is This For?
- CRM admins managing WhatsApp communication
- Sales teams tracking lead interactions in Vtiger
- Support teams logging WhatsApp tickets
- Businesses using Evolution API to receive WhatsApp messages
π Credentials Required
β Vtiger CRM API β No Evolution API credentials needed inside workflow (webhook-only)
π· Tags
vtiger, whatsapp, crm automation, inbound message logging, evolution api, whatsapp crm integration, n8n template, community nodes, lead management, self-hosted n8n, customer communication, no-code crm, webhook
n8n Whatsapp Message Auto-Logger for vTiger CRM
This n8n workflow acts as a flexible receiver for incoming data, specifically designed to process and potentially route information based on a simple condition. While the provided JSON is a basic template, it lays the groundwork for more complex integrations, such as logging WhatsApp messages into a CRM like vTiger.
What it does
This workflow currently performs the following steps:
- Receives Data: It starts by listening for incoming data via a Webhook. This Webhook acts as the entry point for any external system to send information to this workflow.
- Sets Initial Fields: It then uses an "Edit Fields (Set)" node to define or modify data fields. This is useful for standardizing incoming data or adding new properties.
- Conditional Routing: An "If" node evaluates a condition based on the processed data.
- If the condition evaluates to
TRUE, the data is passed to a "No Operation, do nothing" node (which can be replaced with a specific action like logging to vTiger). - If the condition evaluates to
FALSE, the data is also passed to a "No Operation, do nothing" node (which can be replaced with an alternative action or error handling).
- If the condition evaluates to
- Provides Context: A "Sticky Note" is included for documentation, allowing users to add explanations or instructions directly within the workflow canvas.
Prerequisites/Requirements
- n8n Instance: A running n8n instance (cloud or self-hosted).
- Webhook Source: An external system or application configured to send data to the n8n Webhook URL.
Setup/Usage
- Import the Workflow: Import this JSON definition into your n8n instance.
- Activate the Webhook: The "Webhook" node will generate a unique URL. This is the endpoint where your external system (e.g., a WhatsApp integration platform) should send its data.
- Configure "Edit Fields":
- Open the "Edit Fields" node.
- Define the fields you expect to receive or want to create. For example, if you're receiving WhatsApp messages, you might extract
senderPhoneNumber,messageContent,timestamp, etc.
- Configure the "If" Node:
- Open the "If" node.
- Set up the condition(s) that determine how the incoming data should be routed. For instance, you might check if
messageContentcontains specific keywords or ifsenderPhoneNumberis from a known lead.
- Replace "No Operation" Nodes:
- The "No Operation, do nothing" nodes are placeholders. Replace them with the actual actions you want to perform:
- For the
TRUEbranch (e.g., if a lead is identified), add a vTiger node to create or update a record, log the message, or link it to a lead. - For the
FALSEbranch (e.g., if no lead is found or the message is irrelevant), you might send a notification, log it to a different system, or simply discard it.
- For the
- The "No Operation, do nothing" nodes are placeholders. Replace them with the actual actions you want to perform:
- Save and Activate: Save the workflow and activate it to start processing incoming data.
Example Use Case (as hinted by directory name):
To implement "Whatsapp Message Auto-Logger for vTiger CRM with Lead Relation":
- The Webhook would receive messages from a WhatsApp API (e.g., Twilio, MessageBird, or a custom integration).
- The Edit Fields node would extract relevant message details like sender, message body, and timestamp.
- The If node would check if the sender's phone number already exists as a lead in vTiger.
- If
TRUE, the workflow would use a vTiger node (not included in this basic template) to log the message as an activity or comment on the existing lead. - If
FALSE, the workflow might create a new lead in vTiger or route the message for manual review.
- If
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitorβs webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger β Manually start the workflow or schedule it to run periodically. Input Setup β Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) β Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring β Clean and convert GPT output into JSON format. Data Storage (Google Sheets) β Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the βSet Input Fieldsβ node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors β Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection β Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report β Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization β Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs β Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting Itβs a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chatβturn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. π What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing π§ Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation π Required Credentials OpenAI API Setup Go to platform.openai.com β API keys (sidebar) Click "Create new secret key" β Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai β Dashboard β API Keys Generate a new API key β Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) βοΈ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflowβchat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" π― Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration β οΈ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation
PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive β Download PDF β OCR text β AI normalize to JSON β Upsert Buyer (Account) β Create Opportunity β Map Products β Create OLI via Composite API β Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content β the parsed JSON (ensure itβs an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id β build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total β per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger β Download File From Google Download File From Google β Extract from File β Update File to One Drive Extract from File β Message a model Message a model β Create or update an account Create or update an account β Create an opportunity Create an opportunity β Build SOQL Build SOQL β Query PricebookEntries Query PricebookEntries β Code in JavaScript Code in JavaScript β Create Opportunity Line Items --- Quick setup checklist π Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. π IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) π§ AI Prompt: Use the strict system prompt; jsonOutput = true. π§Ύ Field mappings: Buyer tax id/name β Account upsert fields Invoice code/date/amount β Opportunity fields Product name must equal your Product2.ProductCode in SF. β Test: Drop a sample PDF β verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep βReturn only a JSON arrayβ as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields donβt support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your orgβs domain or use the Salesforce nodeβs Bulk Upsert for simplicity.