Google Drive to AWS S3 File Sync with Deduplication
High-Level Summary
This workflow automates the synchronization of files from a specific Google Drive folder to an AWS S3 bucket. When a file is updated in the watched Google Drive folder, the workflow triggers, compares existing S3 objects, and uploads only the updated or new files, preventing duplicates. An error handler ensures failures are caught and logged. This is ideal for backup, migration, or continuous sync scenarios.
Node Breakdown
- Google Drive Trigger (OAuth2) — Watches a specific folder for file updates. Configured to trigger on
fileUpdatedevents within a folder specified by thefolderToWatchparameter (uses{{ $env.WEBHOOK_URL }}[your_id]— you must replace[your_id]with the actual Google Drive folder ID). No additional options set. - Merge (No auth) — Compares incoming data from the trigger with existing S3 objects. Uses
removeKeyMatchesmode, comparing the propertyname.value(from trigger) againstKey.value(from S3 list). This filters out files already present in S3. - AWS S3 – get (AWS Credentials) — Lists all objects in the S3 bucket
mybucketusing thegetAlloperation. This provides the reference list for the merge step. - AWS S3 – upload (AWS Credentials) — Uploads files that are new or updated. The filename is taken from
$json["name"]. Uploads to bucketmybucketwith server-side encryptionAES256and a tagYOUR_CREDENTIAL_HERE: gdrive(you should replace the tag key with an actual value). Binary data is not enabled – you will need to adjust if file content is passed as binary. - Error Handler (No auth) — A
Stop and Errornode that catches any workflow error and stops execution with a custom message.
Setup Instructions
- Google Drive: Enable the Google Drive API in your Google Cloud Console, create OAuth2 credentials (Web application), and set up an n8n Google Drive OAuth2 credential. The trigger requires a folder ID – retrieve it from the folder’s URL (e.g.,
https://drive.google.com/drive/folders/abc123). - AWS S3: Create an IAM user with programmatic access (Access Key ID and Secret Access Key). Attach a policy granting
s3:ListBucket,s3:PutObject, ands3:GetObjectfor the target bucket (mybucket). Create the bucket if it doesn’t exist. - Environment Variable: The trigger’s
folderToWatchuses$env.WEBHOOK_URL. Define this variable in your n8n instance (e.g., as a placeholder or actual webhook URL). Alternatively, replace the expression with the folder ID directly. - Connect the nodes: The current workflow has no connections drawn – you must manually link: Google Drive Trigger → Merge (Input 1), AWS S3 – get → Merge (Input 2), Merge → AWS S3 – upload. Also connect the error output of any node to Error Handler.
Use Cases and Adaptations
- Automated backup: Replace the merge step with a conditional to always upload even if files exist.
- Cross-account sync: Change the S3 bucket to a different AWS account or region.
- File type filtering: Add a Filter node after the trigger to only process certain file extensions.
- Notifications: Insert a Slack or email node after successful upload.
- Two-way sync: Extend with a reverse trigger from S3 events to update Google Drive.
Workflow JSON
{
"nodes": [
{
"name": "Google Drive Trigger",
"type": "n8n-nodes-base.googleDriveTrigger",
"position": [
480,
1480
],
"parameters": {
"event": "fileUpdated",
"options": {},
"triggerOn": "specificFolder",
"folderToWatch": "{{ $env.WEBHOOK_URL }}[your_id]"
},
"credentials": {
"googleDriveOAuth2Api": {
"id": "{{ $credentials.googleDriveOAuth2Api.id }}",
"name": "Google Drive account"
}
},
"typeVersion": 1,
"id": "0feb2324-889c-404d-9131-d63e8d0ba893",
"notes": "This googleDriveTrigger node performs automated tasks as part of the workflow."
},
{
"name": "Merge",
"type": "n8n-nodes-base.merge",
"position": [
680,
1560
],
"parameters": {
"mode": "removeKeyMatches",
"propertyName1": "name.value",
"propertyName2": "Key.value"
},
"typeVersion": 1,
"id": "b163b0d1-ef02-49c2-a49b-75dfe4fd5923",
"notes": "This merge node performs automated tasks as part of the workflow."
},
{
"name": "AWS S3 - get",
"type": "n8n-nodes-base.awsS3",
"position": [
480,
1660
],
"parameters": {
"options": {},
// ... truncated (copy to see full JSON)How to Import This Workflow
- 1Copy the workflow JSON above using the Copy Workflow JSON button.
- 2Open your n8n instance and go to Workflows.
- 3Click Import from JSON and paste the copied workflow.
Don't have an n8n instance? Start your free trial at n8nautomation.cloud
Related Templates
AI-Powered CV Scanner with Google Sheets & Gemini
Overview This workflow automates the initial screening of job applicants by combining a web form, AI-powered CV analysis, and Google Sheets. When a candidate submits their application (name, email, and CV PDF), the workflow instantly extracts the text from the PDF using Mistral OCR, then sends it to Google Gemini for evaluation against a predefined job description. The AI returns a qualification score (0.0 to 1.0) and a detailed explanation, which are then logged alongside the candidate's details in a Google Sheet. This eliminates manual CV review, speeds up your hiring pipeline, and ensures every applicant is evaluated consistently. Workflow Steps Application Form (Form Trigger) — No auth required. This node presents a custom-branded web form to collect the candidate's Full Name, Email, and CV (PDF upload). The form is styled with a dark, glassmorphism theme and includes animated backgrounds. Once submitted, the workflow triggers automatically. Log Candidate Submission (Google Sheets) — OAuth2. Immediately after form submission, this node appends the candidate's name and email to the 'CVs' Google Sheet. This ensures the application is recorded even if the subsequent analysis steps fail. Extract CV Text (Mistral AI) — API Key auth. This node takes the uploaded PDF file from the form and uses Mistral's OCR API to extract all text content from the CV. It dynamically selects the binary file uploaded in the previous step. AI Qualification (LLM Chain) — This is the core analysis node. It uses a detailed prompt that includes: - A system message defining the AI as a professional, objective hiring assistant. - The full job description for a "Senior Frontend Developer" with core requirements and preferred qualifications. - Clear evaluation logic: candidates missing core requirements cannot score above 0.6; meeting all core requirements yields at least 0.75; preferred qualifications add bonuses up to 1.0. - The extracted CV text as context. - An instruction to output raw JSON only. Gemini 2.5 Flash Lite (Language Model) — API Key auth (Google AI Studio). This node provides the actual AI model (Google Gemini 2.5 Flash Lite) with a temperature of 0.4 for balanced, deterministic outputs. It powers the LLM Chain above. JSON Output Parser (Output Parser) — This node ensures the AI's response is valid JSON with the exact schema: (number) and (string). It prevents malformed responses from breaking downstream nodes. Add CV Analysis (Google Sheets) — OAuth2. After analysis, this node updates the candidate's row in the 'CVs' sheet by matching on the Email column. It writes the and from the AI's output into the corresponding columns. Create 'CVs' Spreadsheet (Google Sheets) — OAuth2. This node runs once when the workflow is first triggered manually. It creates a new Google Sheet named 'CVs' with columns: FullName, Email, QualificationRate, QualificationDescription. Setup Instructions Prerequisites A Google account (for Google Sheets) A Mistral AI account (free tier available) — Get your API key here A Google AI Studio account — Create an API key here Step-by-Step Google Sheets Credentials: In the three Google Sheets nodes, create or select an OAuth2 credential for Google Sheets. Grant access to create and edit spreadsheets. Mistral AI Credential: In the "Extract CV Text" node, create a new credential and paste your Mistral API key. Gemini Credential: In the "Gemini 2.5 Flash Lite" node, create a new credential and paste your Google AI Studio API key. Customize Job Description: Open the "AI Qualification" node and edit the section in the prompt to match your actual job posting. Activate the Workflow: Toggle the workflow to "Active" status. The "Application Form" node will generate a public URL you can share with candidates. Test: Use the "Start Here" manual trigger to initialize the Google Sheet, then submit a test application via the form URL. Use Cases & Variations Custom Job Roles: Replace the Senior Frontend Developer description with any role (e.g., Marketing Manager, Data Scientist, Sales Rep) by editing the prompt in the AI Qualification node. Different Storage: Replace Google Sheets with Airtable, Notion, or a database like PostgreSQL for storing applications and results. Multi-Round Screening: Add a Slack or email notification node to alert the hiring team when a candidate scores above a certain threshold (e.g., >0.8). Interview Scheduling: Connect the output to a Calendly or Google Calendar node to automatically invite high-scoring candidates for an interview. Batch Processing: Modify the trigger to accept a CSV upload of multiple CVs for bulk analysis. Enhanced Analysis: Add more output fields like "years of experience", "top skills", or "red flags" by updating the JSON schema in the Output Parser and the prompt.
Convert Baserow Markdown to HTML via Webhook
This workflow automatically converts markdown content stored in a Baserow table to HTML. It is triggered by a webhook and can process either a single record (specified by a record ID) or all records in the table. After conversion, it updates the original record(s) with the resulting HTML, making it ideal for content management systems, blog posts, or any scenario where markdown needs to be rendered for web use. Step-by-Step Walkthrough Baserow sync video description — Webhook (no auth) This node starts the workflow when an HTTP request is received. It uses a unique path () and expects an optional query parameter to indicate a single record ID. No authentication is configured, so you should secure the webhook with a validation mechanism or by keeping the URL secret. Check if it's 1 record or all records — If (no auth) This conditional node checks whether the incoming request contains a parameter (i.e., a specific record ID). If it exists, the workflow proceeds to fetch and convert a single record; otherwise, it processes all records in the table. Get single record from baserow — Baserow (API Key auth) When a record ID is provided, this node retrieves that specific row from the Baserow table (ID ) in database . The row ID is dynamically set using the expression . Convert markdown to HTML (single) — Markdown (no auth) This node converts the content of the field (which contains markdown) into HTML. Options enabled include emoji support, simple line breaks, and backslash escaping of HTML tags. The output is stored in . Update single record in baserow — Baserow (API Key auth) The generated HTML is written back to the same record. The field ID (which corresponds to the HTML version of the description) is updated with the converted value. Get all records from baserow — Baserow (API Key auth) When no specific record ID is given, this node fetches all rows from the table (). No additional filters are applied. Convert markdown to HTML (all records) — Markdown (no auth) For each record retrieved, this node converts the field to HTML. Options are left at defaults (no emoji/simple line breaks). Update all records in baserow — Baserow (API Key auth) The converted HTML is updated back into every record’s field ID . Note that this updates all records sequentially; the node uses to target each row. (There are also nine error‑handler nodes connected to the webhook, which are not shown in detail but provide error logging or fallback behavior.) Setup Instructions Baserow – You need a Baserow account and an API token. In n8n, create a new Baserow credential (type: Baserow API) and enter your API token. You must also know your database ID () and table ID (). These can be found in the Baserow URL when browsing the table. Webhook – The workflow provides a unique webhook URL (e.g., ). Configure any external system (like a custom app, Zapier, or manual testing) to send a POST request to this URL. Optionally include a query parameter to update only one record. No other external services are required; the markdown conversion is handled natively by n8n. Use Cases and Variations Content Management System – Automatically convert markdown blog posts or descriptions stored in Baserow to HTML for display on a website. Email Campaigns – Convert markdown content to HTML before sending via an email service (you could add an SMTP node after the update). Batch Processing – The “all records” path is perfect for periodic re‑rendering of an entire table, e.g., after changing markdown conversion options. Variation – Instead of a webhook, you could trigger the workflow on a schedule to re‑convert stale records. Replace the webhook with a Schedule Trigger node and add a filter (e.g., only records updated in the last hour). Security – Since the webhook has no authentication, consider adding a Header Auth node or an HMAC validator to prevent unauthorized calls. This workflow is production‑ready, includes error handling, and can be easily adapted for other Baserow tables or different field mappings.
Daily Web Scraper and Extract Data to Google Sheets
High-level Summary This workflow automatically scrapes a public web page every morning at 8:00 AM and appends the extracted data (e.g., product title, price) to a Google Sheet. It creates a time-series dataset that you can chart or analyze, making it ideal for tracking competitor prices, job listings, product availability, or any recurring data from a static HTML page. Node-by-Node Walkthrough Every Morning (Schedule Trigger) — No auth - Runs the workflow daily at 8:00 AM using a cron expression . Fetch Page (HTTP Request) — No auth - Requests the target URL (currently set to ). It fetches the full HTML of the page. Retries up to 3 times with a 5-second wait between attempts. Extract Values (HTML) — No auth - Uses CSS selectors to extract structured data from the HTML. Configured to extract: - from the first element. - from elements matching the selector . Add Date Stamp (Code) — No auth - A JavaScript code node that maps each input item to an output object containing: - : today's date in YYYY-MM-DD format. - and : copied from the HTML extraction step. Append Row (Google Sheets) — OAuth2 (Google account) - Appends a new row to a Google Sheet (specified by and ). The columns are automatically mapped from the input data, so each row will contain Date, Title, and Price. Setup Instructions Google Sheets Credentials: You need a Google account and an OAuth2 credential in n8n. If you haven't already, create a Google Sheets credential in n8n by authorizing your Google account. Replace Placeholders: - In the Fetch Page node, change the URL to the actual web page you want to scrape. - In the Append Row node, set the to the ID of your Google Sheet (found in the sheet's URL). Customize CSS Selectors: Open the target page in your browser, right-click on the data you want to extract, and select “Inspect”. Copy the CSS selector for each element and update the Extract Values node accordingly. Test: Run the workflow manually once to verify that the data is extracted and written correctly. Activate: Turn on the workflow to run automatically every morning. Use Cases and Adaptations Price Monitoring: Track prices of a product on e-commerce sites over time. Job Listings: Scrape a job board for new postings (combined with a filter to avoid duplicates). News Headlines: Collect daily headlines from a news site into a spreadsheet. Product Availability: Check if an item is in stock and log the status. Variations: Add an Error Trigger workflow to notify you via Slack or email if a scrape fails. Use IF nodes to only append rows when the price has changed. Replace the HTTP Request with an API node if the source offers a JSON API. Add additional extraction fields (e.g., rating, description, URL). Note: Only scrape public pages, respect the site's , and keep the schedule to once per day to avoid overloading the server.