Telegram Smart Archive Manager with OCR and Airtable Indexing - n8n Workflow

Users who receive many documents or images via Telegram and need an organized, searchable archive.
Automation specialists looking for advanced n8n templates combining messaging, cloud storage, OCR, and database indexing.
Teams needing a simple, indexed document management system without relying on proprietary software.
Developers wanting to study a complex n8n workflow example involving conditional branching and external API calls (Google Vision).

• Anyone utilizing Airtable for knowledge management and seeking an efficient file ingestion method using an n8n trigger.

Managing digital files spread across multiple messaging apps can be chaotic. This sophisticated n8n workflow solves this by instantly processing files received in a designated Telegram chat, creating a permanent, searchable record. When a document or image is sent, the n8n automation takes over. It downloads the file, uploads it securely to Google Drive, and critically, checks if it's OCR-eligible (images or PDFs). If so, it uses the Google Vision API via an HTTP Request n8n node to extract text. Finally, all metadata, the Drive link, and the extracted text are indexed into an Airtable database, making every document immediately searchable directly through a Telegram command. This comprehensive n8n workflow dramatically increases efficiency and ensures no valuable text is locked away inside images.

This n8n workflow operates on a dual-path logic initiated by the Telegram trigger:

1. Incoming Telegram Message (n8n Trigger): The Telegram Trigger n8n node activates upon any new message.


2. Initial Routing: The flow immediately splits into two branches using an If n8n node:

1. File Processing: The file ID is used by a Telegram n8n node to download the binary data. This binary data is then immediately uploaded to Google Drive using the Google Drive n8n node, securing a permanent URL.


2. OCR Conditional Check: An If n8n node checks the file's MIME type. If it is an image or a PDF, the n8n workflow routes the binary data to the Google Vision OCR service (via an HTTP Request n8n node) for text extraction. Non-eligible files skip this step.


3. Data Merging and Indexing: Both the OCR results (extracted text) and the skipped paths are combined using a Merge n8n node. The resulting data stream, which now includes the Drive link and text content, is indexed into Airtable using the Airtable n8n node.


4. Confirmation: The final step in the file upload path is a Telegram n8n node that sends a success message back to the original chat, including a preview of the extracted text and the Google Drive link.


5. Search Execution: In the Search Command Path, an Airtable n8n node performs a full-text search against the indexed field. The results are formatted and returned to the user via a final Telegram n8n node, completing the searchable n8n workflow functionality.

To deploy this powerful n8n workflow template, follow these steps:

1. Import the n8n Workflow: Copy the provided JSON data and paste it into your n8n instance using the 'New' -> 'Import from JSON' option.


2. Telegram Credentials: Set up your Telegram Bot API credentials. This credential is required for the Telegram Trigger n8n node and the Telegram actions (Download, Send Message).


3. Google Drive Credentials: Configure Google Drive OAuth2 credentials. Ensure the account has permission to upload files to the specified root folder (My Drive in this configuration).


4. Google Vision API Setup: The Google Vision OCR n8n node uses an HTTP Request node configured with OAuth2. You must have a Google Cloud Project with the Google Vision API enabled and configure a corresponding OAuth2 credential in n8n for this n8n node.


5. Airtable Credentials: Set up the Airtable Token API credential. You need to configure the Base ID and Table ID in the Index in Airtable and Search in Index n8n nodes to match your chosen database structure. Ensure the Airtable base has fields for file name, Drive URL, and extracted text (used for the search formula).


6. Activate: Save the n8n workflow and set the Telegram Trigger to 'Active' to start listening for incoming messages.

Telegram Trigger (n8n trigger): The starting point of this n8n workflow. It is configured to listen for new messages and edited messages, specifically trapping files and commands.
Check if File/Image (If n8n node): Essential for flow control, this n8n node checks for the existence of message.document or message.photo properties before proceeding with the archival process.
Extract File Metadata (Set n8n node): Collects dynamic data points like fileId, fileName, and mimeType using expressions (={{ $json.message.document?.fileid || $json.message.photo?.slice(-1)[0].fileid }}).
Download File from Telegram (Telegram n8n node): Executes the file download operation using the previously extracted fileId, retrieving the binary data necessary for subsequent steps.
Upload to Google Drive (Google Drive n8n node): Saves the binary file content to the specified Google Drive location, generating the permanent webViewLink used for indexing.
Google Vision OCR (HTTP Request n8n node): This key n8n node performs OCR by sending the file binary data (content-encoded) to the Google Vision API endpoint. This enables full-text search capabilities.
Index in Airtable (Airtable n8n node): Creates a new record in the Airtable base. It maps the file metadata and the extractedText (from OCR or 'Not applicable' placeholder) into searchable fields, completing the searchable archive portion of the n8n workflow.
Search in Index (Airtable n8n node): Used in the separate command path. It executes a search operation using a complex filter formula (=SEARCH(LOWER("{{ $json.searchQuery }}"), LOWER({extracted_text}))) to find relevant files based on user input from the n8n trigger.