Automated document translation with Straker, Google Drive & Slack

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Automate document translation and ensure translation accuracy using Straker Verify, Google Drive and Slack. How it works? A workflow step is set up to "watch" a Google Drive folder. When your team ...

Best for

Document Extraction automation workflows
Multimodal AI automation workflows
intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-straker-verify.strakerverify, n8n-nodes-base.googledrive, n8n-nodes-base.googledrivetrigger, n8n-nodes-base.webhook

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Vijayeta Sinel.

Original n8n.io source

1.1 Workflow description

Title: Automated document translation with Straker, Google Drive & Slack
Workflow name: Automated document translation with Straker, Google Drive & Slack

Automate document translation and ensure translation accuracy using Straker Verify, Google Drive and Slack.

**How it works? ** A workflow step is set up to "watch" a Google Drive folder. When your team members place new files in this folder, they are downloaded. Straker Verify then translates them and provides a quality score.

Once Straker Verify has completed this, the job info is fetched, the translation is saved to an output folder and you are notified via Slack.

What problem does this solve? When using AI to translate documents, you have no idea about the quality and accuracy of the output. This template answers the question “How good is my translation?” so you have a high level of confidence before you publish.

Who is this for? This workflow template is designed for businesses needing translation and localization of documents such as text docs, presentations, web pages, transcripts, video subtitles and others. Use it to build workflows that localize your content at scale while maintaining translation quality, accuracy and compliance.

Set up instructions

Straker Verify Integration with n8n

Connect to Straker Verify: Obtain Your API Key Sign Up/Log In: Visit https://verify.straker.ai/ to create an account or log in. Navigate to API Keys: Go to Verify → Settings → API Keys. **Copy Your Key:** Find and copy your API key. **Add Key to n8n:** In n8n, go to Settings → Credentials → Straker Verify`.

Set Up Credentials for the Straker Verify Node

Open n8n and go to "Credentials".
From the left sidebar, click on "Credentials".
Search for "Straker Verify" and select "Straker Verify API" from the dropdown.
Paste the copied access token from the Verify app and save it.

Assign Credentials to the Node 1.Go to your workflow and open the Straker Verify node. 2.Select the "Straker Verify API" credentials you just created from the dropdown (Credentials to connect with), and save.

✅ You are now ready to use the workflow.

Workflow Steps

Step 1: Initiate Workflow – Upload Files to Google Drive 1.Upload one or more files to the designated Google Drive folder. This triggers the "New File in Google Drive" node in n8n.

Step 2: Select Workflow The system fetches available workflows via: Fetch All Users Workflows No matching workflow found? You'll be notified via Slack: No workflow found

Step 3: Create Project in Straker Verify The following steps are handled automatically: Fetch language/project options Download files from Google Drive Create a new project using: Create Straker Project ✅ You'll receive a Slack confirmation: > "Project created – ID: xxxxxx"

Step 5: Process Completion & File Return Once files are processed by Straker: The Incoming Translation Result webhook is triggered. The workflow: Downloads processed files: Get File Content from Strakerh - Uploads them to Google Drive: Upload File to Google Drivee

Step 6: Confirmation - Workflow Complete You'll receive a final Slack message: > "Workflow complete – Files are now available in Google Drive"

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Sticky: Setup

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 2 - Sticky: Google Trigger

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 3 - Sticky: Create Project

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 4 - Sticky: Webhook

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 5 - Sticky: Download Translations

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 6 - Sticky: Upload to Drive

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 7 - Create a new project

Type / Role: n8n-nodes-straker-verify.strakerVerify - strakerVerify
Config choices: Version 1

Block 8 - Download file

Type / Role: n8n-nodes-base.googleDrive - googleDrive
Config choices: Version 3

Block 9 - Google Drive Trigger

Type / Role: n8n-nodes-base.googleDriveTrigger - googleDriveTrigger
Config choices: Version 1

Block 10 - Webhook

Type / Role: n8n-nodes-base.webhook - webhook
Config choices: Version 2.1

Block 11 - Download translated files

Type / Role: n8n-nodes-straker-verify.strakerVerify - strakerVerify
Config choices: Version 1

Block 12 - Upload file

Type / Role: n8n-nodes-base.googleDrive - googleDrive
Config choices: Version 3

3. Summary Table

Workflow	Automated document translation with Straker, Google Drive & Slack
Complexity	intermediate
Nodes	12
Categories	Document Extraction, Multimodal AI
Author	Vijayeta Sinel
Published	10 Jun 2025

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/4832/4832.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source Document Extraction workflows Multimodal AI workflows

Frequently asked questions

What does Automated document translation with Straker, Google Drive & Slack do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Document Extraction, Multimodal AI use case.

Vijayeta Sinel

1 workflow

Nodes

n8n-nodes-base.stickynote n8n-nodes-straker-verify.strakerverify n8n-nodes-base.googledrive n8n-nodes-base.googledrivetrigger n8n-nodes-base.webhook

Complexity

intermediate

Published 10 Jun 2025

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/4832/4832.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Detect semantic duplicate website pages with Google Drive, Postgres and Ollama

## Quick overview This workflow scans HTML files in a Google Drive folder, extracts and stores page text in Postgres, generates local vector embeddings with Ollama, and uses PGVector similarity searches to produce CSV reports that flag semantically duplicate website pages. ## How it works 1. Starts manually and clears the existing PGVector embeddings table and the scraped page text table in Postgres. 2. Lists files in a specified Google Drive folder, filters to the target documents, and processes them in batches. 3. Downloads each HTML file from Google Drive, extracts the main body text, cleans it, and upserts the results into a Postgres table for scraped pages. 4. Reads the scraped page text back from Postgres in batches, splits it into overlapping chunks, and attaches page metadata (sheet_id, file_name, file_url) to each chunk. 5. Generates embeddings locally with Ollama and inserts the chunk vectors and metadata into Postgres (PGVector), deduplicating already-processed pages. 6. Builds an HNSW index in Postgres, computes chunk-to-chunk similarity matches and a pairwise page report, and exports the results as a CSV file. 7. Computes page-level centroid embeddings, finds highly similar page pairs, and exports a page-level duplicate report as a CSV file. ## Setup 1. Add Google Drive OAuth2 credentials and set the Google Drive folder URL/ID used to scan for your HTML files. 2. Add Postgres credentials for a database with the pgvector extension enabled and permissions to create/alter tables and indexes (including HNSW indexes). 3. Add an Ollama credential and ensure the embedding model mxbai-embed-large:latest is available on your Ollama instance. 4. Confirm your source files are HTML documents and that the workflow’s text extraction and similarity thresholds match your content and desired duplicate sensitivity. ## Requirements - Working instance of n8n, either self-hosted or on the cloud. Remember, this workflow can be computationally expensive. - Google Drive API (with OAuth setup in n8n credentials section) - Ollama (for open source models) or any Embedding model API - PostgreSQL with PGVector or any other vector database - PgAdmin (for PostgreSQL) or your interface to access database tables via SQL for troubleshooting (optional). ## Additional info Limitations and Enhancements: Physical system memory mxbai-embed-large Running through Ollama is free and private, but the embedding generation speed depends entirely on your hardware. The more system memory you have, the more data you can process in batches in the loop node. Similarity threshold and boilerplate content The cosine distance used in this workflow is 0.15 for chunk-level matching. And 0.05 (similarity above 95%) of the threshold is used for page-level centroid matching. This is only the starting point. Once you have the data, and especially if your data has more noise, you might need to tweak these thresholds for better matching. This workflow needs HTML files to extract text This workflow doesn't crawl a website or fetch pages by entering a URL. You need to download HTML files (rendered or source) for consumption. Use parallel processing and Cloud APIs Two sub-processes take the most time: Downloading HTML files from Google Drive Creating vector embeddings If you can use parallel processing in n8n and execute these sub-processes in parallel, the process will be done much faster. Additionally, if you can use cloud APIs for embedding, it may save some you some processing time as well. Use efficient SQL queries Since I am from a non-tech background and not a coder, I used a mix of Gemini, Perplexity and Claude to create SQL codes for this workflow. If you're better at it, you can run computationally efficient queries that would help you achieve better results with less computation expense and time.

View

Generate monthly BigQuery KPI PDF reports with Claude, Google Docs, Outlook and Teams

## Quick overview This workflow runs monthly to query KPI data from Google BigQuery, generates a narrative with Anthropic Claude, fills a Google Docs report template, exports it as a PDF, archives it to OneDrive, emails it via Microsoft Outlook, and posts a summary to Microsoft Teams. ## How it works 1. A schedule trigger fires on the 1st of every month at 07:00 and calculates the start and end dates of the previous full calendar month. 2. Four parallel BigQuery queries fetch revenue KPIs, top product categories, weekly sales trend, and top customers for that period. Each result set is tagged with a source label before merging. 3. All tagged rows are combined and aggregated into a single structured report payload containing KPI summaries, ranked tables, and company metadata. 4. The payload is split across two concurrent branches: one sends it to a Claude Sonnet LLM chain to generate an executive narrative with five sections (summary, revenue analysis, category insights, customer insights, and recommendation), and the other creates a named copy of a Google Docs template in your reports folder. 5. Once both branches complete, the narrative is merged into the report payload and the replacement requests for all template placeholders are constructed. 6. The Google Docs node applies all replacements in a single batchUpdate call, then the file is exported as a PDF via Google Drive. 7. The finished PDF is archived to OneDrive, emailed via Outlook with the report attached, and a formatted KPI summary card is posted to a Microsoft Teams channel. ## Setup 1. Set the following n8n environment variables before activating: GCP_PROJECT_ID, BQ_DATASET, GDOCS_TEMPLATE_FILE_ID, GDRIVE_REPORTS_FOLDER_ID, ONEDRIVE_REPORTS_FOLDER_ID, REPORT_RECIPIENTS, TEAMS_TEAM_ID, and TEAMS_CHANNEL_ID. 2. Connect a Google BigQuery credential and update the four SQL queries to match your dataset, table name, and column names. 3. Connect an Anthropic API credential to the Claude Chat Model sub-node, then manually wire its output to the ai_languageModel input (bottom connector) of the Create AI Narrative with Claude node on the canvas. 4. Connect Google Drive and Google Docs OAuth2 credentials. In Google Drive, create a master report template Doc containing the placeholder strings listed in the Customization section, note its file ID from the URL, and set GDOCS_TEMPLATE_FILE_ID accordingly. 5. Connect Microsoft OneDrive, Outlook, and Teams OAuth2 credentials. Retrieve your Teams team ID and channel ID using the Microsoft Graph Explorer and set the corresponding environment variables. ## Requirements - Google Cloud project with BigQuery enabled and an orders table matching the SQL schema in the workflow - Google Workspace account (Drive and Docs OAuth2 access) - Anthropic API key - Microsoft 365 account with OneDrive, Outlook, and Teams access ## Customization - To change the reporting cadence, update the cron expression in the schedule trigger: 0 7 * * 1 for weekly or 0 7 * * * for daily. - To adapt the SQL queries to your schema, replace orders, order_total, customer_id, is_new_customer, created_at, and product_category with your actual column names. - To change the AI model, update the model field in the Claude Chat Model sub-node. - To add more KPI sections, extend the SQL queries, the aggregation code in Consolidate BigQuery Data, and the replacements array in Construct Replacement Requests.

View

Ingest and search Cloudflare R2 media with Gemini, Groq Whisper, and Supabase

## Quick overview This workflow ingests images, PDFs, and videos from a Cloudflare R2 folder, uses Google Gemini to view pdfs, images and videos, Groq stt (Whisper) for video transcriptst - to generate searchable descriptions and tags, stores embeddings in a Supabase pgvector table. ## How it works 1. Receives a webhook request containing a Cloudflare R2 bucket and folder URL, then lists the objects in that folder. 2. Filters to supported file types, builds public CDN URLs and timestamps, and routes each item as an image, PDF, or video. 3. For images, calls Google Gemini with the image URL to generate structured metadata (summary, detailed description, tags, and scores). 4. For PDFs, calls Google Gemini to analyze the document URL and return the same structured metadata. 5. For videos, downloads each file locally, extracts representative frames with FFmpeg for Google Gemini visual analysis, extracts audio, transcribes it with Groq Whisper, and tags transcript chunks with Groq Llama. 6. Normalizes results into a single text “content” field plus JSON metadata, generates Google Gemini embeddings, and inserts the vectors into Supabase (pgvector). 7. Receives a separate webhook query, retrieves the most similar items from Supabase using embeddings, and returns ranked matches in the webhook response. ## Setup 1. Create a Cloudflare R2 bucket with publicly accessible object URLs, and add Cloudflare R2 credentials in n8n. 2. Set up a Supabase project with pgvector enabled and a table named `vec10`, then add Supabase credentials in n8n. 3. Add Google Gemini credentials (Google PaLM/Gemini API) for embeddings and provide an HTTP Header Auth credential for the Gemini HTTP requests. 4. Set the `GROQ_API_KEY` environment variable for the Groq Whisper transcription and Llama tag extraction calls. 5. If you enable video processing, install `curl`, `ffmpeg`, and `ffprobe` on the n8n host and update the local directory paths (temp root, frames directory, and video directory) in the workflow inputs. 6. Copy the ingest webhook (`/vector-ingest`) and query webhook (`/vector-query`) URLs and configure your upstream app to send the expected JSON payloads. ## Additional info Video: FFmpeg code nodes cut videos smartly into "video_frames" items and "video_transcripts" for easy handling and pgvector storage. Exposed webhook to vector query flow allows Voice Agent to find and display the full video, pulled from Cloudflare bucket, by the referenced matching video_frames or video_transcripts returned from vector query.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Automated document translation with Straker, Google Drive & Slack

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Sticky: Setup

Block 2 - Sticky: Google Trigger

Block 3 - Sticky: Create Project

Block 4 - Sticky: Webhook

Block 5 - Sticky: Download Translations

Block 6 - Sticky: Upload to Drive

Block 7 - Create a new project

Block 8 - Download file

Block 9 - Google Drive Trigger

Block 10 - Webhook

Block 11 - Download translated files

Block 12 - Upload file

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions