HumationHuman + Automation
Back to Catalog

🚚 Automate delivery confirmation with Telegram Bot, Google Drive and Gmail

Samir SaciSamir Saci
2960 views
2/3/2026
BackupGoogle DriveAutomationData StorageAPI
Official Page

Tags: Supply Chain Management, Logistics, Transportation

Context

Hey! I'm Samir, a Supply Chain Engineer and Data Scientist from Paris founder of LogiGreen Consulting

We design tools to help small and medium businesses in improving their logistics processes using data analytics and automation.

> Let's use N8N to make supply chains more efficient and sustainable Supply Chains!

📬 For business inquiries, you can add me on Here

Who is this template for?

This workflow template is designed for logistics operations that cannot rely on a Transportation Management System to record proofs of deliveries.

Example of Logistic Operations

What is a delivery confirmation?

This workflow uses a Telegram bot to automatically notify logistics teams by email when a shipment is delivered.

Example of Delivery Notice

Drivers (equipped with their smartphones) can record their arrival with all the necessary information for accurate distribution planning.

How do we notify the delivery?

Let us imagine a truck driver arriving at the destination; he can contact the bot to be guided on how to record the delivery.

Screens of Telegram Discussion

  1. User Guide: the first bot's message is a brief explanation of the process
  2. Record Shipment Number: the bot asks the driver to share the shipment number and record it
  3. Collect GPS Location: the bot asks the driver to share its GPS location and record them
  4. Picture of the Shipment: the bot asks for a picture of the shipment and saves it in Google Drive
  5. Send Confirmation: after data collection, the bot proposes to send a confirmation to the logistics management team

An email is then automatically sent by the N8N workflow including all the information recorded by the flow and a picture of the shipment.

Example of Notification via Email

Prerequisite

This workflow does not require any additional paying subscription.

  • A Google Drive Account with a folder including a Google Sheet
  • API Credentials: Google Drive API, Google Sheets API and Gmail API
  • A Telegram Bot with its API token from BotFather
  • A Google sheet to store the shipment records with these five columns prepared: shipmentNumber, recordTime, gpsLattitude, gpsLongitude, cargoPicture, deliveryTime

Next Steps

Follow the sticky notes to set up the parameters inside each node and get ready to improve your logistics operations!

I have detailed the steps in a short tutorial 👇 image.png 🎥 Check My Tutorial

🚀 Interested in applications of N8N for Logistics & Supply Chain Management? Let's connect on Linkedin

Notes

  • This workflow can be adapted to add more functionalities. I explain how in the video.
  • The bot can handle multiple drivers at the same time.
  • If you want to learn more about the original tool designed with Python: 🚚 Blog Article about Telegram Shipment Tracking Bot

This workflow has been created with N8N 1.82.1 Submitted: March 17th, 2025

Automate Delivery Confirmation with Telegram Bot, Google Drive, and Gmail

This n8n workflow streamlines the process of confirming deliveries by integrating a Telegram bot, Google Drive, Google Sheets, and Gmail. It allows for quick updates on delivery statuses, stores relevant information, and sends automated email notifications.

What it does

  1. Listens for Telegram Commands: The workflow is triggered by specific commands sent to a Telegram bot.
  2. Extracts Delivery Information: It parses the Telegram message to extract details such as the tracking number, delivery status, and recipient email.
  3. Updates Google Sheet: Based on the extracted tracking number, it searches a specified Google Sheet. If found, it updates the delivery status; otherwise, it adds a new entry.
  4. Generates Delivery Confirmation PDF (Placeholder): The workflow includes a placeholder for generating a delivery confirmation PDF using Google Drive. This step would typically involve creating a document from a template with the delivery details.
  5. Sends Confirmation Email: An automated email is sent to the recipient (or a specified email address) confirming the delivery, optionally attaching the generated PDF.
  6. Sends Telegram Confirmation: A confirmation message is sent back to the Telegram chat, acknowledging the update.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Telegram Bot: A Telegram bot token and the chat ID where you will send commands.
  • Google Sheets Account: A Google Sheets spreadsheet with delivery information (e.g., tracking number, status, recipient email).
  • Google Drive Account: A Google Drive account for storing or generating PDF confirmations.
  • Gmail Account: A Gmail account for sending email notifications.
  • n8n Credentials: Configured n8n credentials for Telegram, Google Sheets, Google Drive, and Gmail.

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON file.
    • In your n8n instance, click "New" in the workflows sidebar, then "Import from JSON".
    • Paste the JSON content or upload the file.
  2. Configure Credentials:
    • Click on each node (Telegram Trigger, Google Sheets, Google Drive, Gmail, Telegram) and configure the respective credentials.
    • For Google services, you'll typically use OAuth2 credentials.
    • For Telegram, provide your Bot Token and ensure the Telegram Trigger node is set to listen for updates from your bot.
  3. Customize Google Sheets Node (ID: 18):
    • Specify your "Spreadsheet ID" and "Sheet Name".
    • Adjust the "Search Column" and "Search Value" to match your tracking number column.
    • Configure the "Update Key" and "Update Column" for the delivery status.
  4. Customize Google Drive Node (ID: 58):
    • This node is currently a placeholder. You would need to configure it to create a PDF file from a template, specifying the folder ID and file name.
  5. Customize Gmail Node (ID: 356):
    • Set the "From Email" and "To Email" addresses. The "To Email" can be dynamically pulled from the Google Sheet data (e.g., {{$node["Google Sheets"].json["email"]}}).
    • Compose your email "Subject" and "Body".
    • If you implement the Google Drive PDF generation, you can attach the file here.
  6. Customize Telegram Nodes (IDs: 50, 49):
    • Ensure the Telegram Trigger (ID: 50) is configured to receive messages from your bot.
    • Customize the Telegram message in the Telegram node (ID: 49) to provide relevant feedback.
  7. Activate the Workflow: Once all configurations are complete, activate the workflow.

Now, when you send a command to your Telegram bot (e.g., "delivery confirmed [tracking_number] [recipient_email]"), the workflow will process the request, update your Google Sheet, potentially generate a PDF, send an email, and confirm back on Telegram.

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.

Ranjan DailataBy 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

Daniel NkenchoBy 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.

Le NguyenBy Le Nguyen
942