Get email notifications for newly uploaded Google Drive files

This workflow sends out email notifications when a new file has been uploaded to Google Drive. The workflow uses two nodes: Google Drive Trigger**: This node will trigger the workflow whenever a new file has been uploaded to a given folder Send Email**: This node sends out the email using data from the previous Google Drive Trigger node.

Tom

+2

Upload leads from a CSV file to Pipedrive CRM

This workflow gets leads' contacts from a CSV file and adds it to the Pipedrive CRM by creating an organization and a person. The CSV file in this workflow serves as a universal connector allowing you to export contacts from any platform like LinkedIn, Facebook, etc. Prerequisites Google account and Google credentials Pipedrive account and Pipedrive credentials How it works The Google Drive Trigger node starts the workflow when a new CSV file is uploaded to a specific folder in Google Drive. Google Drive node downloads the CSV file. Spreadsheet File node reads data from the CSV file and sends the output to the Merge node. This Spreadsheet File's output becomes the input 1 for the Merge node. Meanwhile, the Pipedrive node gets the same list of contacts from the CSV file. IF node checks if Pipedrive has these contacts already created previously and sends the checked results to the Merge node. These results arrive at the Merge node as input 2. Merge node compares two inputs via email and removes the matches. Pipedrive node creates new contacts based on the data provided by the Merge node with necessary details such as organization and notes.

n8n Team

+8

Create a Follow-Up Email draft from Google Meet Recording – With OpenAI Whisper

Disclaimer: This template only works on self-hosted n8n instances and needs a community node. This workflow is designed to streamline the process of creating professional follow-up emails based on Google Meet recordings. It leverages OpenAI's transcription and summarization capabilities to extract key points, action items, and next steps, then drafts an email in Gmail for easy review and sending. Important : Custom n8n Installation with ffmpeg (Recommended): The workflow is optimized for instances of n8n with ffmpeg installed. This allows for seamless conversion of Google Meet recordings from MP4 to MP3 format, significantly reducing file size and improving processing efficiency. OAuth Configuration Required: For self-hosted n8n instances, ensure OAuth authentication is properly configured for Google Drive and Gmail. This is essential for accessing recordings and creating email drafts securely. Privacy Considerations: Before sending Google Meet recordings to OpenAI for processing, verify compliance with the data protection standards of the country or company you belong to. As this workflow is shared publicly, the creator is not responsible for ensuring compliance with regulations in your region or company. Workflow Overview: Detects when a Google Meet recording is uploaded to a designated Google Drive folder. Converts the recording to MP3 (if ffmpeg is available) and processes it through OpenAI for transcription. Summarizes the meeting and generates a professional follow-up email draft in Gmail, ready for your review and customization.

Dataki

Transcribe audio files from Cloud Storage

This workflow transcribes audio files stored in AWS S3 and stores the information in Google Sheets. Google Drive Trigger node** triggers the workflow when a new file is uploaded in Google Drive. AWS S3 1 node** uploads the new file to an S3 bucket. AWS S3 2 node** gets the file from the S3 bucket. AWS Transcribe 1 node** creates a transciption job for the respective audio file. Wait node** waits for the transcription job from the previous node to be complete before proceeding with the workflow (necessary in case the service is busy or the file to be transcribed is large, delaying the workflow). AWS Transcribe 2 node** gets the information of the transcription job. Set node** sets the necessary values to be included in the data set. Google Sheets node** adds the transcription information to a sheet that serves as data set.

Lorena

+5

Automatic Background Removal for Images in Google Drive

This n8n workflow simplifies the process of removing backgrounds from images stored in Google Drive. By leveraging the PhotoRoom API, this template enables automatic background removal, padding adjustments, and output formatting, all while storing the updated images back in a designated Google Drive folder. This workflow is very useful for companies or individuals that are spending a lot of time into removing the background from product images. How it Works The workflow begins with a Google Drive Trigger node that monitors a specific folder for new image uploads. Upon detecting a new image, the workflow downloads the file and extracts essential metadata, such as the file size. Configurations are set for background color, padding, output size, and more, which are all customizable to match specific requirements. The PhotoRoom API is called to process the image by removing its background and adding padding based on the settings. The processed image is saved back to Google Drive in the specified output folder with an updated name indicating the background has been removed. Requirements PhotoRoom API Key Google Drive API Access Customizing the Workflow Easily adjust the background color, padding, and output size using the configuration node. Modify the output folder path in Google Drive or replace Google Drive with another storage service if needed. For advanced use cases, integrate further image processing steps, such as adding captions or analyzing content using AI.

Simon

Automatically optimise images added to a Google drive folder

How it works This workflow watches a selected Google Drive folder for any images added to it. It then takes that image, sends it the the tinypng.com service which optimises and reduces its size (where possible) Tinypng then returns the updated image which is then automatically saved in your chose Google Drive folder Setting things up It's pretty simple to configure and should only take around 5-10mins. You only need to set up credentials for Google Drive and Tinypng.com For Tinypng.com you can sign up for their free tier API access which gives you 500 optimisations per month Once you have those two things, you just need choose your 'input' folder to watch for images and your 'output' folder for where these images should be stored There are a few more optional things you can do such as the naming of your final image and also lots more you could do with the Tinypng API for more advanced image optimisation

Jonathan

Transcribe Audio Files, Summarize with GPT-4, and Store in Notion

Who is this for? This workflow template is perfect for content creators, researchers, students, or anyone who regularly works with audio files and needs to transcribe and summarize them for easy reference and organization. What problem does this workflow solve? Transcribing audio files and summarizing their content can be time-consuming and tedious when done manually. This workflow automates the process, saving users valuable time and effort while ensuring accurate transcriptions and concise summaries. What this workflow does This template automates the following steps: Monitors a specified Google Drive folder for new audio files Sends the audio file to OpenAI's Whisper API for transcription Passes the transcribed text to GPT-4 for summarization Creates a new page in Notion with the summary Setup To set up this workflow: Connect your Google Drive, OpenAI, and Notion accounts to n8n Configure the Google Drive node with the folder you want to monitor for new audio files Set up the OpenAI node with your API key and desired parameters for Whisper and GPT-4 Specify the Notion database where you want the summaries to be stored How to customize this workflow Adjust the Google Drive folder being monitored Modify the OpenAI node parameters to fine-tune the transcription and summarization process Change the Notion database or page properties to match your preferred structure With this AI-powered workflow, you can effortlessly transcribe audio files, generate concise summaries, and store them in a structured manner within Notion. Streamline your audio content processing and organization with this automated template.

Pat

+4

Extract text from PDF and image using Vertex AI (Gemini) into CSV

Case Study I'm too lazy to record every transaction for my expense tracking. Since all my expenses are digital, I just extract the transactions from bank PDF statements and screenshots into CSV to import into my budgeting software. Read more -> How I used A.I. to track all my expenses What this workflow does Upload your PDF or screenshots into Google Drive It then passes the PDF/image to Vertex Gemini to do some A.I. image recognition It then sends the transactions as CSV and stores it into another Google Drive folder Setup Set up 2 google drive folders. 1 for uploading and 1 for the output. Input your Google Drive crendtials Input your Vertex Gemini credentials How to adjust it to your needs You can upload other types of documents for information extraction. You can extract any text data from any image or PDF You can adjust the A.I. prompt to do different things

Keith Rumjahn

Send Google Drive files to Notion database

This workflow sends a file to a Notion database of your choosing when a new file is created in a specific Google Drive folder. Prerequisites Notion account and Notion credentials. Google account and Google credentials. Google Drive folder to monitor for new files. How it works When a Google Drive file is created in the folder you specified, the workflow sends the file to the Notion database you created. The workflow uses the On file upload node to trigger the workflow when a new file is created in the folder. The Create database page node creates a new page in the Notion database you created. Setup Create a Notion database called "My Google Drive Files" with the following columns: Filename Google Drive File Share the database to n8n. In the n8n workflow, click on the Create database page node and select the database you created in step 1. In Google Drive, create a folder and navigate to it. Copy the URL of the Google Drive folder you are currently in. In the n8n workflow, add the folder URL to On file upload node.

n8n Team

Sync data between Google Drive and AWS S3

This workflow synchronizes files one-way from Google Drive to AWS S3. Google Drive Trigger node** triggers the workflow when a new file is added to the drive. AWS S3 node** gets all files stored in an S3 bucket. Merge node** merges the files from Google Drive and AWS S3 by key (file name) and keeps only the new file. AWS S3 node** uploads the new file in the S3 bucket.

Lorena

Create an Onfleet task when a file in Google Drive is updated

Summary Onfleet is a last-mile delivery software that provides end-to-end route planning, dispatch, communication, and analytics to handle the heavy lifting while you can focus on your customers. This workflow template listens to a Google Drive update event and creates an Onfleet delivery task. You can easily change which Onfleet entity to interact with. Configurations Connect to Google Drive with your own Google credentials Specify the Poll Times and File URL or ID to your own preference, the poll time determines the frequency of this check while the file URL/ID specifies which file to monitor Update the Onfleet node with your own Onfleet credentials, to register for an Onfleet API key, please visit https://onfleet.com/signup to get started

James Li

+3

Recognize invoices / receipts from Google Drive and put them into Google Sheets

This workflow allows you to recognize a folder with receipts or invoices (make sure your files are in .pdf, .png, or .jpg format). The workflow can be triggered via the "Test workflow" button, and it also monitors the folder for new files, automatically recognizing them. Video Demo https://youtu.be/mGPt7fqGQD8 1. n8n import glitch After import, the trigger node "When clicking 'Test workflow'" might be disconnected. You need to connect it via 2 arrows to "Google Sheets1" and "Google Drive" nodes. So, the workflow has 2 triggers - via button, and via Google Sheets "new file" event - both of these triggers should be connected to 2 nodes. Here is how it should look like: https://ocr.oakpdf.com/n8n_fix.png 2. Set up RapidAPI HTTP auth key Create new "HTTP header" n8n credential and paste your RapidAPI key from https://rapidapi.com/restyler/api/receipt-and-invoice-ocr-api into it. https://ocr.oakpdf.com/n8n_api_key.png Make sure "HTTP Request" node uses this credential. 3. Set up your Google Auth You need a Google connection to work with your Google Sheets and Google Drive accounts: https://docs.n8n.io/integrations/builtin/credentials/google/oauth-generic/#finish-your-n8n-credential 4. Set up Google Sheets Copy this Google Sheets document: https://docs.google.com/spreadsheets/d/1G0w-OMdFRrtvzOLPpfFJpsBVNqJ9cfRLMKCVWfrTQBg/edit?usp=sharing Custom document formats and advanced usage Email: [email protected] Linkedin: https://www.linkedin.com/in/anthony-sidashin/

Anthony

Integrate Google Drive Trigger with 500+ apps and services

Popular ways to use Google Drive Trigger integration