HumationHuman + Automation
Back to Catalog

Parse PDF, DOCX & images with Mistral OCR via Google Drive with Slack alerts

Yves TkaczykYves Tkaczyk
1034 views
2/3/2026
summarizationemailopenaigoogle sheetsimap
Official Page

Use cases

  • Monitor Google Drive folder, parsing PDF, DOCX and image file into a destination folder, ready for further processing (e.g. RAG ingestion, translation, etc.)
  • Keep processing log in Google Sheet and send Slack notifications.

How it works

  • Trigger: Watch Google Drive folder for new and updated files.
  • Create a uniquely named destination folder, copying the input file.
  • Parse the file using Mistral Document, extracting content and handling non-OCRable images separately.
  • Save the data returned by Mistral Document into the destination Google Drive folder (raw JSON file, Markdown files, and images) for further processing.

How to use

  • Google Drive and Google Sheets nodes:
    • Create Google credentials with access to Google Drive and Google Sheets. Read more about Google Credentials.
    • Update all Google Drive and Google Sheets nodes (14 nodes total) to use the credentials
  • Mistral node:
  • Slack nodes:
    • Create Slack OAuth2 credentials. Read more about Slack OAuth2 credentials
    • Update the two Slack nodes: Send Success Message and Send Error Message:
      • Set the credentials
      • Select the channel where you want to send the notifications (channels can be different for success and errors).
  • Create a Google Sheets spreadsheet following the steps in Google Sheets Configuration. Ensure the spreadsheet can be accessed as Editor by the account used by the Google Credentials above.
  • Create a directory for input files and a directory for output folders/files. Ensure the directories can be accessed by the account used by the Google Credentials.
  • Update the File Created, File Updated and Workflow Configuration node following the steps in the green Notes.

Requirements

  • Google account with Google API access
  • Mistral Cloud account access to Mistral API key.
  • Slack account with access to Slack client ID and secret ID.
  • Basic n8n knowledge: understanding of triggers, expressions, and credential management

Who’s it for

Anyone building a data pipeline ingesting files to be OCRed for further processing.

🔒 Security

All credentials are stored as n8n credentials. The only information stored in this workflow that could be considered sensitive are the Google Drive Directory and Sheet IDs. These directories and the spreadsheet should be secured according to your needs.

Need Help?

Reach out on LinkedIn or Ask in the Forum!

n8n Workflow: Parse PDF/DOCX & Images with Mistral OCR via Google Drive with Slack Alerts

This n8n workflow automates the process of extracting text from various document types (PDF, DOCX, images) uploaded to a specific Google Drive folder. It uses a custom Mistral OCR service for text extraction and notifies a Slack channel about the processing status and results.

What it does

  1. Monitors Google Drive: Listens for new files created in a specified Google Drive folder.
  2. Filters by File Type: Checks if the uploaded file is a PDF, DOCX, or an image (PNG, JPG, JPEG).
  3. Downloads File: If the file type is supported, it downloads the file from Google Drive.
  4. Converts to Base64 (for images): If the file is an image, it converts the binary data to a Base64 string.
  5. Prepares OCR Request: Sets up the payload for the Mistral OCR API, including the file content and type.
  6. Sends to Mistral OCR: Makes an HTTP request to a custom Mistral OCR endpoint to process the document/image.
  7. Extracts OCR Result: Parses the response from the OCR service to get the extracted text.
  8. Updates Google Sheet (Optional/Placeholder): Includes a Google Sheets node, which is currently not connected but could be used to log the OCR results or file metadata.
  9. Sends Slack Notification: Posts a message to a designated Slack channel with the processing status and the extracted text (or an error message if OCR fails).

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • Google Drive Account: Configured Google Drive credentials in n8n with access to the monitored folder.
  • Slack Account: Configured Slack credentials in n8n with permission to post to the desired channel.
  • Mistral OCR Service: A running custom Mistral OCR service accessible via an HTTP endpoint. This workflow assumes the service is available and expects a specific JSON input/output format.
  • Google Sheets Account (Optional): If you intend to use the Google Sheets node, you'll need Google Sheets credentials and a target spreadsheet.

Setup/Usage

  1. Import the Workflow:
    • Copy the provided JSON workflow.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the "Import from JSON" button and paste the copied JSON.
  2. Configure Credentials:
    • Google Drive Trigger: Select or create a new Google Drive OAuth2 credential. Specify the "Folder ID" you want to monitor for new files.
    • Google Drive (Download File): Select the same Google Drive credential.
    • Slack: Select or create a new Slack OAuth2 credential. Configure the "Channel" where you want to receive notifications.
    • Google Sheets (Optional): If you plan to use this node, select or create a Google Sheets OAuth2 credential and configure the spreadsheet details.
  3. Configure Mistral OCR Endpoint:
    • Locate the "HTTP Request" node.
    • Update the "URL" field to point to your actual Mistral OCR service endpoint.
    • Adjust any headers or body parameters if your OCR service requires different authentication or input formats.
  4. Activate the Workflow: Once all credentials and configurations are set, activate the workflow.

Now, whenever a new PDF, DOCX, or image file is uploaded to the specified Google Drive folder, the workflow will automatically process it, extract text using your Mistral OCR service, and send a notification to Slack.

Related Templates

Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API

Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use — Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen

RapiwaBy Rapiwa
183

Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack

📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. 🚀📚💬 What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. 📦 Step 3: Logs release data into Google Sheets for record-keeping and analysis. 📊 Step 4: Retrieves FAQ or documentation data from Notion. 📚 Step 5: Merges GitHub and Notion data to calculate documentation drift. 🔍 Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. 🔔 Key Benefits ✅ Keeps SDK documentation aligned with product releases ✅ Prevents outdated information from reaching users ✅ Provides centralized release tracking in Google Sheets ✅ Sends real-time Slack alerts for overdue updates ✅ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.

Rahul JoshiBy Rahul Joshi
31

Automate Gmail responses with GPT and human-in-the-loop verification

Try It Out! This n8n template uses AI to automatically respond to your Gmail inbox by drafting response for your approval via email. How it works Gmail Trigger monitors your inbox for new emails AI Analysis determines if a response is needed based on your criteria Draft Generation creates contextually appropriate replies using your business information Human Approval sends you the draft for review before sending Auto-Send replies automatically once approved Setup Connect your Gmail account to the Gmail Trigger node Update the "Your Information" node with: Entity name and description Approval email address Resource guide (FAQs, policies, key info) Response guidelines (tone, style, formatting preferences) Configure your LLM provider (OpenAI, Claude, Gemini, etc.) with API credentials Test with a sample email Requirements n8n instance (self-hosted or cloud) Gmail account with API access LLM provider API key Need Help? Email Nick @ nick@tropicflare.com

Nick CanfieldBy Nick Canfield
88