Automated Email Sending from Google Sheets with Gmail
Overview
This workflow automates the process of sending personalized emails to customers based on data stored in a Google Sheet. It runs on a schedule, checks for rows that are marked with a status of "Waiting for sending" and whose date matches the current day, then sends an email via Gmail using the row's subject, title, and recipient address. After sending, it updates the sheet to mark the status as "Sent successfully". This is ideal for marketing campaigns, scheduled reminders, or any recurring email outreach where you want to track delivery status.
Workflow Steps
- Schedule Trigger — Runs the workflow at a configurable interval (currently every 1 minute for testing; adjust to daily or hourly as needed). No authentication required.
- Retrieve Customer Messages Data (Google Sheets) — Fetches all rows from a specified Google Sheet (OAuth2 authentication). The sheet must contain columns: ID, Name, Email, Date, Status, Title, Subject.
- Filter Status (Waiting for sending) (Filter) — Filters the rows to only those where:
Statusequals "Waiting for sending"Title,Subject,Email,Name,Dateall existDate(formatted as yyyy/MM/dd) equals today's date
- Send a message (Gmail) — For each filtered row, sends an email (OAuth2 authentication) to the recipient in
Email, with subject fromTitleand plain text body fromSubject. - Merge fields (Merge) — Combines the original row data (from the filter) with the output of the Gmail node (by position) to preserve all fields.
- Set data (Set) — Extracts and renames fields:
email,name,IDfrom the merged data. - Update Message Status (Google Sheets) — Updates the same Google Sheet (OAuth2 authentication) by matching the row with the same
IDand setting theStatuscolumn to "Sent successfully".
Setup Instructions
- Google Account: You need a Google account with access to Google Sheets and Gmail.
- Google Sheet: Create a new Google Sheet with the following columns (header row):
ID,Name,Email,Date,Status,Title,Subject. Populate it with your data. TheDatecolumn must be inyyyy/MM/ddformat (e.g.,2025/03/15). Set theStatusto "Waiting for sending" for rows you want to send today. - n8n Credentials:
- Create Google Sheets OAuth2 credentials in n8n (use the same Google account).
- Create Gmail OAuth2 credentials in n8n (also the same account).
- Update Node Parameters:
- In the Retrieve Customer Messages Data node, change the
Document IDto your own sheet's ID (found in the sheet URL). - In the Update Message Status node, do the same.
- Adjust the Schedule Trigger interval to your desired frequency (e.g., every day at 9 AM).
- In the Retrieve Customer Messages Data node, change the
- Test: Run the workflow manually first to ensure it sends an email and updates the sheet correctly.
Use Cases & Variations
- Marketing Campaigns: Send promotional emails to a list of customers on a specific date.
- Reminders & Follow-ups: Automate birthday greetings, appointment reminders, or invoice follow-ups.
- Multi-channel: Extend the workflow to also send SMS via Twilio or a Slack message after the email is sent.
- HTML Emails: Change the Gmail node's
emailTypeto "html" and use an HTML template in the message field. - Conditional Logic: Add more filter conditions (e.g., only send to certain segments) or use a Switch node to route different email templates.
- Logging: Add a node to log sent emails to another sheet or a database for auditing.
Workflow JSON
{
"meta": {
"instanceId": "257476b1ef58bf3cb6a46e65fac7ee34a53a5e1a8492d5c6e4da5f87c9b82833",
"templateId": "2088"
},
"nodes": [
{
"id": "0e4c65ce-95e9-4a32-bc5c-0461cb339764",
"name": "Filter Status (Waiting for sending)",
"type": "n8n-nodes-base.filter",
"position": [
1670,
1110
],
"parameters": {
"options": {
"looseTypeValidation": true
},
"conditions": {
"options": {
"leftValue": "",
"caseSensitive": true,
"typeValidation": "loose"
},
"combinator": "and",
"conditions": [
{
"id": "401b79a0-a079-4ea0-805b-a963d9206031",
"operator": {
"name": "filter.operator.equals",
"type": "string",
"operation": "equals"
},
"leftValue": "={{ $json.Status }}",
"rightValue": "Waiting for sending"
},
{
"id": "74ec18c7-e4cc-4d82-ba05-0ec4781cbb9f",
"operator": {
"type": "string",
"operation": "exists",
"singleValue": true
},
"leftValue": "={{ $json.Title }}",
"rightValue": ""
},
{
"id": "6e293a16-48cd-40bb-9882-09b456a97d58",
"operator": {
"type": "string",
// ... 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 LinkedIn Content Creator with Perplexity Research & Auto-Posting
AI-Powered LinkedIn Content Automation Workflow Overview This workflow automates the entire LinkedIn content lifecycle — from research and ideation to image generation and scheduled posting. It uses Perplexity AI for topic research, an Anthropic Claude model as the content strategist, and OpenAI's image generation model to create branded visuals. The workflow runs on two separate schedules: one for content creation (daily) and one for publishing (twice weekly). It stores all posts in a Google Sheet for review before they go live, giving you full control over what gets published. This is ideal for founders, marketers, and content creators who want to maintain a consistent LinkedIn presence without spending hours writing, designing, and scheduling posts manually. The system learns from past content stored in Google Sheets and uses AI to generate fresh, on-brand posts that resonate with your target audience. Node-by-Node Breakdown Content Creation Pipeline (Runs Daily at 5 AM) Schedule () — No auth. Triggers the content creation workflow daily at 5:00 AM. This is the starting point for generating new post ideas. Get Past Ideas () — OAuth2. Reads all rows from the "LinkedIn Posts" sheet in the Google Sheet "AI Content Database". This provides the AI with context about previously generated posts to avoid repetition. Join Ideas () — No auth. A JavaScript code node that concatenates all past post ideas into a single text string, making it easy for the AI to reference them. LinkedIn Creator Agent () — No auth (uses connected models). This is the core AI agent that generates LinkedIn post content. It uses: - Anthropic Chat Model () — API Key auth. Uses Claude 3.7 Sonnet as the language model for content generation. - Perplexity Research () — API Key auth. A sub-workflow that uses Perplexity AI to research current topics and trends. - Structured Output Parser () — No auth. Ensures the AI output follows a structured JSON format with fields: , , and . Image Style () — OAuth2. Downloads a reference image from Google Drive that serves as the style guide for generating new images. OpenAI Image1 () — Header Auth (HTTP Header Auth). Sends a POST request to OpenAI's image generation API (gpt-image-1 model) with the reference image and a prompt describing the desired image for the LinkedIn post. Convert to File () — No auth. Converts the base64 image data from OpenAI's response into a binary file for saving to Google Drive. Save Image () — OAuth2. Uploads the generated image to a specific folder ("LinkedIn AI Posts") in Google Drive, naming it after the post title. Save Post () — OAuth2. Appends a new row to the "LinkedIn Posts" sheet with the post text, description, image URL, and status set to "review". Publishing Pipeline (Runs Every 3 Days at 2 PM) Schedule 2 () — No auth. Triggers the publishing workflow every 3 days at 2:00 PM. Get Ready Posts () — OAuth2. Filters the Google Sheet for rows where the status column equals "ready", retrieving posts that have been approved for publishing. Pick One () — No auth. Limits the output to a single post (first row) from the filtered results. Download Image () — OAuth2. Downloads the image associated with the selected post from Google Drive using the image URL stored in the sheet. Publish Post () — OAuth2. Publishes the post to LinkedIn with the text content and attached image, set to public visibility. Update Status () — OAuth2. Updates the status of the published post from "ready" to "posted" in the Google Sheet, matching by the "about" column. Setup Instructions Required Accounts & Services Google Account — For Google Sheets and Google Drive access. You'll need to create a Google Cloud Project and enable the Sheets and Drive APIs, then create OAuth2 credentials. Anthropic Account — Sign up at console.anthropic.com to get an API key for Claude 3.7 Sonnet. Perplexity AI Account — Sign up at perplexity.ai and obtain an API key for research capabilities. OpenAI Account — Sign up at platform.openai.com and get an API key for image generation. LinkedIn Account — You'll need a LinkedIn profile or company page to post to. Connect via n8n's LinkedIn OAuth integration. Configuration Steps Create a Google Sheet named "AI Content Database" with a sheet called "LinkedIn Posts" containing columns: , , , . Upload a reference image to Google Drive that represents your brand's visual style. Update the Google Sheet ID and folder IDs in the nodes to match your own. Configure all credential connections in n8n for each service. Adjust the cron schedules to match your desired posting frequency. Customize the AI system prompt in the LinkedIn Creator Agent to match your brand voice. Use Cases & Variations Primary Use Cases Personal Brand Building: Automate daily LinkedIn content for thought leaders and consultants. Agency Content Management: Manage multiple client content calendars from a single workflow. Content Repurposing: Adapt the workflow to generate content for Twitter, Instagram, or newsletters. Possible Variations Platform Swap: Replace the LinkedIn node with Twitter, Facebook, or Slack nodes. Research Source: Swap Perplexity for a Google Search API or RSS feed reader. Image Model: Use DALL-E 3 or Stable Diffusion instead of gpt-image-1. Review Workflow: Add a Slack notification node to alert you when posts are ready for review. Multi-Platform Publishing: Duplicate the publishing pipeline for different social networks. Content Calendar: Add a calendar node to schedule posts for specific dates and times.
Product Video Generator using AI
Overview This workflow automatically generates personalized, cinematic-quality product videos by combining competitor ad intelligence from Foreplay, creative prompt generation with Google Gemini AI, and text-to-video generation via Kie.ai (Sora 2). It's designed for marketers, brand managers, and content creators who want to produce high-quality video ads quickly without manual scripting or editing. The workflow fetches product images from Google Drive, analyzes competitor video ads from Foreplay, uses Gemini to craft optimized video prompts, generates videos through Kie.ai, and automatically saves the finished videos back to Google Drive. Workflow Steps Manual Trigger (No auth) — Starts the workflow manually for testing or on-demand video generation. Set Workflow Credentials (No auth) — Configures environment variables including Google Drive folder IDs, Foreplay API base URL, API key, and brand ID. These values are referenced throughout the workflow. Set Product Information (No auth) — Defines the product details: name (e.g., "Homyped"), niche (e.g., "fashion"), category (e.g., "shoes"), and target market (e.g., "b2c"). These parameters drive the entire video generation process. Fetch Product Image from Google Drive (OAuth2) — Retrieves the first image file from a specified Google Drive folder. Uses the folder ID set in step 2. Fetch Competitor Video Data (Foreplay API) (Bearer Token auth) — Calls the Foreplay API to get competitor ad data filtered by brand ID, date range (last month), niche, target market, language (English), video duration (5-30 seconds), and platform (Instagram). Returns the top 5 longest-running video ads. Split Foreplay Response (No auth) — Splits the Foreplay API response array into individual items for processing each competitor ad example. Assemble Video Input Data (No auth) — Combines competitor ad data (description, transcript, emotional drivers, duration) with the product image URL into a structured format for prompt generation. Iterate Over Ad Examples (No auth) — Processes each competitor ad example one at a time in batches, allowing the workflow to generate multiple video prompts and videos sequentially. Generate Video Prompt (No auth) — Uses Google Gemini AI (connected via the Google Gemini LLM node) to generate a personalized, cinematic-quality text prompt for video generation. The prompt incorporates product information, competitor ad details, emotional tone, and target duration. Google Gemini LLM (API Key auth) — The language model connection that powers the prompt generation. Requires a Google Gemini API key. Create Video Task (Kie.ai) (Bearer Token auth) — Sends the generated prompt and product image URL to Kie.ai's Sora 2 image-to-video model. Configures portrait aspect ratio, removes watermark, and includes a callback URL. Check Video Generation Status (Bearer Token auth) — Polls Kie.ai's API to check the status of the video generation task using the task ID returned from step 11. Video Generation Status (No auth) — A switch node that evaluates the video generation status: - Success — Proceeds to download the finished video - Failed — Returns to the iteration loop to try the next ad example - Processing — Waits and checks again Wait Before Checking Again (No auth) — Pauses execution for 1 minute before re-checking the video generation status. Download Finished Video (No auth) — Downloads the completed video file from the URL provided by Kie.ai's success response. Upload Generated Video to Google Drive (OAuth2) — Saves the downloaded video to a specified Google Drive folder, named with the current date and time. Setup Instructions Required Accounts & Services Google Account — For Google Drive access (store product images and save generated videos) - Create a Google Cloud Project and enable the Google Drive API - Set up OAuth 2.0 credentials in n8n Foreplay Account — For competitor ad intelligence - Sign up at Foreplay - Get your API key and brand ID from your Foreplay dashboard Google Gemini API Key — For AI prompt generation - Get an API key from Google AI Studio Kie.ai Account — For video generation (Sora 2 model) - Sign up at Kie.ai and obtain API credentials - Configure Bearer Token authentication in n8n Configuration Steps Add all API keys and credentials in the n8n credentials manager Update the Set Workflow Credentials node with your: - Google Drive folder IDs (for product images and generated videos) - Foreplay API key and brand ID - Kie.ai callback URL (optional) Update the Set Product Information node with your product details Ensure your product image folder in Google Drive is set to public access Run the workflow manually to test Use Cases & Variations Primary Use Cases E-commerce product videos — Generate video ads for new product launches Competitor analysis — Create videos inspired by successful competitor ad formats Social media content — Produce Instagram-ready video ads A/B testing — Generate multiple video variations from different competitor examples Adaptation Ideas Change video model — Replace Kie.ai with another video generation service (e.g., Runway, Pika) Add scheduling — Replace Manual Trigger with a Cron trigger for automated daily video generation Multi-product support — Modify the workflow to iterate over a list of products from a Google Sheet Add review step — Insert a human approval node before uploading to Google Drive Different platforms — Change the Foreplay API parameters to target TikTok, Facebook, or YouTube ads Custom branding — Modify the Gemini prompt to include specific brand guidelines or tone of voice
Contact Form to Slack & Email Notification Workflow
This workflow automates the process of capturing contact form submissions from your website and immediately notifying your team via Slack while also sending a confirmation email to the submitter. It's designed to help businesses respond faster to leads and inquiries without manual intervention. Workflow Steps Form Submission on Website (No auth) — This node creates a simple web form that collects Name, Email, and Phone from visitors. The form is embedded on your website using the provided webhook URL. No authentication is required as it's a public-facing form. Slack (OAuth2) — Sends a formatted message to your designated Slack channel (e.g., #leads) containing the submitted details. Requires a Slack app with bot token and appropriate channel permissions. Send Email - Gmail (OAuth2) — Sends a thank-you email to the submitter using Gmail API. Requires OAuth2 credentials for a Google account. Send Email - Outlook (OAuth2) — Sends the same thank-you email via Microsoft Outlook API. Requires OAuth2 credentials for a Microsoft account. Setup Instructions Slack: Create a Slack app with chat:write scope, install it to your workspace, and add the bot to your target channel. Gmail: Enable Gmail API in Google Cloud Console, create OAuth2 credentials, and authorize the workflow. Outlook: Register an app in Azure AD, grant Mail.Send permission, and configure OAuth2 credentials. Form: Copy the webhook URL from the Form Submission node and embed it as the form action in your HTML form. Use Cases & Variations Lead capture: Replace Slack with CRM nodes (HubSpot, Salesforce) to create contacts automatically. Multi-channel notifications: Add SMS via Twilio or push notifications via Telegram. Conditional routing: Use IF nodes to route different form responses to different Slack channels or email templates. Data enrichment: Add HTTP Request nodes to enrich lead data (e.g., company info from email domain).