Real-time sales quote creation in Odoo via Telegram with Google Gemini AI

257 views

2/3/2026

Google Sheets Update Row Spreadsheet Automation Data Manipulation

Overview

This template connects Telegram with Odoo to let your sales team create sales quotes and check product availability in real-time — just by sending chat messages.

It’s designed for sales representatives, distributors, and small business owners who want to manage quotes and product information quickly without logging into Odoo.

⚙️ How It Works

Once configured, this workflow listens to your Telegram bot for incoming messages. Based on the message text, it performs different actions in Odoo:

Product Queries Sales reps can ask about products directly in Telegram:

“What’s the price of Product B?” “How many units of Product A are available?”

The workflow fetches real-time data from Odoo and replies instantly.

Sales Quote Creation Sales reps can also create new sales quotes by typing messages like:

“My customer Amazon, his email address is abc@amazon.com wants to buy 10 pcs of Product A and 15 pcs of Product B.”

The workflow extracts relevant details, creates a sales quote in Odoo, and sends confirmation back in Telegram.

🧰 Setup Instructions

Create a Telegram Bot

Go to @BotFather on Telegram.

Create a new bot and copy the API Token.

Prepare Odoo

Enable the Sales and Product modules.

Generate an API Key from your Odoo user account.

Note your Odoo URL (e.g., https://yourcompany.odoo.com).

Import Workflow

Open your n8n instance (self-hosted or cloud).

Click Import Workflow and upload the provided JSON file.

Add Credentials

Configure your Telegram credentials (Bot Token).

Configure your Odoo credentials (Base URL + API Key).

Activate the Workflow

Set the workflow to active to start listening for Telegram messages.

Send a sample message to your bot to test.

🧠 Use Cases Sales reps capturing orders in the field SMEs managing customer inquiries directly from Telegram Real-time price and stock lookups without opening Odoo Automation of repetitive sales quote tasks

🎛️ Customization Options

This workflow can be easily adapted to your business needs:

Change trigger platform: Replace Telegram with WhatsApp, Slack, or Discord using the respective n8n nodes.

Extend data fields: Add fields like delivery date, salesperson, or payment terms.

Auto-confirm orders: Add a node to automatically confirm a Sales Quote once approved.

✅ Requirements Odoo v14 or later (with Sales module enabled) Telegram Bot Token n8n instance (Cloud or self-hosted)

💬 Example Prompts

Product Query: “What’s the price of Product B?” “How many units of Product A are available?”

Order Entry: “My customer Amazon, his email address is abc@amazon.com wants to buy 10 pcs of Product A and 15 pcs of Product B.”

Real-time Sales Quote Creation in Odoo via Telegram with Google Gemini AI

This n8n workflow automates the process of creating sales quotes in Odoo directly from Telegram messages, leveraging Google Gemini AI for intelligent text classification and data extraction. It streamlines the sales process, allowing users to initiate quote creation with natural language commands.

What it does

This workflow simplifies and accelerates sales quote generation by:

Listening for Telegram messages: It acts as a Telegram bot, waiting for incoming messages.
Classifying message intent with AI: It uses a Google Gemini-powered AI Text Classifier to determine if the message is a request to create a sales quote.
Extracting details for Odoo: If classified as a sales quote request, the AI Agent extracts relevant information like customer name, product, quantity, and other necessary details from the message.
Creating a sales quote in Odoo: It then uses the extracted information to create a new sales quote entry in your Odoo ERP system.
Responding with confirmation: Finally, it sends a confirmation message back to the Telegram chat, indicating whether the sales quote was successfully created or if more information is needed.

Prerequisites/Requirements

To use this workflow, you will need:

n8n Instance: A running n8n instance.
Telegram Bot: A Telegram bot token and chat ID.
Odoo Account: Access to an Odoo instance with API credentials.
Google Gemini API Key: An API key for Google Gemini (via the Google Gemini Chat Model node).
AI Agent and Text Classifier: The n8n Langchain nodes for AI Agent and Text Classifier.

Setup/Usage

Import the workflow: Download the JSON provided and import it into your n8n instance.
Configure Telegram Trigger:
- Set up your Telegram Bot credential.
- Configure the "Telegram Trigger" node to listen for messages from your bot.
Configure Google Gemini Chat Model:
- Set up your Google Gemini API key credential.
- Ensure the "Google Gemini Chat Model" node is correctly configured to use your API key.
Configure Odoo:
- Set up your Odoo API credentials (URL, database, username, password).
- Configure the "Odoo" node with the correct operation (e.g., "Create Record") and resource (e.g., "Sale Order").
Adjust AI Agent and Text Classifier:
- Review and potentially fine-tune the prompts within the "Text Classifier" and "AI Agent" nodes to accurately classify and extract information relevant to your specific sales quote requirements.
- The "Call n8n Workflow Tool" node within the AI Agent is likely used to call the Odoo creation logic once the data is extracted.
Activate the workflow: Once all credentials and configurations are set, activate the workflow.

Now, when you send a message to your Telegram bot requesting a sales quote (e.g., "Create a quote for John Doe for 5 units of Product A"), the workflow will process it, create the quote in Odoo, and send you a confirmation.

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.

By Ranjan Dailata

161

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

By Daniel Nkencho

601

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.

By Le Nguyen

942