HumationHuman + Automation
Back to Catalog

Schedule daily email reminders from Google Sheets with Gmail

Yar Malik (Asfandyar)Yar Malik (Asfandyar)
641 views
2/3/2026
ExportDirectusWebhookCSVPagination
Official Page

Intro

This template is for teams, individuals, or businesses who want to automatically send daily email reminders (e.g., updates, status alerts, follow‑ups) using n8n + Gmail.

How it works

  1. Cron Trigger fires every day at your specified time.
  2. Google Sheets node reads all rows from your sheet.
  3. If node filters rows matching your condition (e.g., Status = "Pending").
  4. Send a message (Gmail) sends a customized email to each filtered row.

Required Google Sheet Structure

| Column Name | Type | Example | Notes | |-------------|--------|--------------------------|------------------------------------| | Email | string | user@example.com | Recipient email address | | Status | string | Pending | Filter criterion | | Subject | string | Daily Status Update | Email subject (supports variables) | | Body | string | “Please update your task”| Email body (text or HTML) |

Detailed Setup Steps

  1. Google Sheets
    • Build your sheet with the columns above.
    • In n8n → Credentials, add Google Sheets API (avoid sensitive names).
  2. Gmail
    • In n8n → Credentials → Gmail (OAuth2 or SMTP), connect your account.
    • Do not include your real email in the credential name.
  3. Import & Configure
    • Export the workflow JSON (three‑dot menu → Export).
    • Paste it under Template Code in the Creator form.
    • In each node, select your Google Sheets and Gmail credentials.
  4. Sticky Notes
    • On the If node: “Defines which rows to email.”
    • On the Gmail node: “Sends the email.”

Customization Guidance

  • Adjust schedule: change the Cron expression in Cron Trigger.
  • Modify filter: edit the condition in the If node.
  • Customize email: use expressions like {{$node["Get row(s) in sheet"].json["Subject"]}}.

Troubleshooting

  • Verify the Google Sheet is shared with the connected service account.
  • Check your Cron timezone and expression.
  • Ensure Gmail credentials are valid and not rate‑limited.

Security & Best Practices

  • Remove any real email addresses and sheet IDs.
  • Use n8n Credentials or environment variables—never hard‑code secrets.
  • Add sticky notes for any complex logic.

Schedule Daily Email Reminders from Google Sheets with Gmail

This n8n workflow automates the process of sending daily email reminders based on data stored in a Google Sheet. It allows you to manage a list of recipients and their reminder details, ensuring timely communication.

What it does

  1. Manual Trigger: The workflow is initiated manually, allowing you to run it on demand.
  2. Read Google Sheet: It connects to a specified Google Sheet and retrieves all data from it. This sheet is expected to contain the reminder details, including recipient email addresses.
  3. Conditional Logic (If): The workflow includes an If node, which is currently configured but not connected. In a complete implementation, this node would typically be used to filter or process the data from Google Sheets based on certain conditions (e.g., check if a reminder date is today, or if a reminder has already been sent).
  4. Send Email (Gmail): If the conditions are met (or if the If node is bypassed), the workflow will send emails using Gmail. This node would be configured to use the data from the Google Sheet to populate the recipient, subject, and body of the email.

Prerequisites/Requirements

  • n8n Instance: A running instance of n8n.
  • Google Sheets Account: A Google account with access to Google Sheets.
  • Gmail Account: A Google account with access to Gmail.
  • Google Sheets Credential in n8n: An n8n credential configured for Google Sheets (OAuth2 recommended).
  • Gmail Credential in n8n: An n8n credential configured for Gmail (OAuth2 recommended).
  • Google Sheet: A Google Sheet containing the data for your reminders. The structure of this sheet will depend on how you configure the "Google Sheets" and "Gmail" nodes.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Google Sheets Node:
    • Select your Google Sheets credential.
    • Specify the Spreadsheet ID and Sheet Name where your reminder data is stored.
    • Ensure the "Operation" is set to "Get All" or "Read Data" to fetch the necessary information.
  3. Configure Gmail Node:
    • Select your Gmail credential.
    • Configure the "To" field using an expression to dynamically pull the recipient email address from the Google Sheets data (e.g., {{ $json.emailAddress }}).
    • Configure the "Subject" and "Body" fields, also using expressions to personalize the email content with data from your Google Sheet (e.g., {{ $json.reminderSubject }} and {{ $json.reminderMessage }}).
  4. Configure If Node (Optional but Recommended):
    • Connect the "Google Sheets" node's output to the "If" node's input.
    • Define your conditions within the "If" node. For example, you might check a "Reminder Date" column in your Google Sheet to see if it matches the current date.
    • Connect the "True" branch of the "If" node to the "Gmail" node.
  5. Activate the Workflow: Once configured, activate the workflow.
  6. Execute Manually: Click "Execute Workflow" to run it. For daily reminders, you would typically replace the "Manual Trigger" with a "Cron" node set to run daily at a specific time.

Related Templates

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247

Auto-reply & create Linear tickets from Gmail with GPT-5, gotoHuman & human review

This workflow automatically classifies every new email from your linked mailbox, drafts a personalized reply, and creates Linear tickets for bugs or feature requests. It uses a human-in-the-loop with gotoHuman and continuously improves itself by learning from approved examples. How it works The workflow triggers on every new email from your linked mailbox. Self-learning Email Classifier: an AI model categorizes the email into defined categories (e.g., Bug Report, Feature Request, Sales Opportunity, etc.). It fetches previously approved classification examples from gotoHuman to refine decisions. Self-learning Email Writer: the AI drafts a reply to the email. It learns over time by using previously approved replies from gotoHuman, with per-classification context to tailor tone and style (e.g., different style for sales vs. bug reports). Human Review in gotoHuman: review the classification and the drafted reply. Drafts can be edited or retried. Approved values are used to train the self-learning agents. Send approved Reply: the approved response is sent as a reply to the email thread. Create ticket: if the classification is Bug or Feature Request, a ticket is created by another AI agent in Linear. Human Review in gotoHuman: How to set up Most importantly, install the gotoHuman node before importing this template! (Just add the node to a blank canvas before importing) Set up credentials for gotoHuman, OpenAI, your email provider (e.g. Gmail), and Linear. In gotoHuman, select and create the pre-built review template "Support email agent" or import the ID: 6fzuCJlFYJtlu9mGYcVT. Select this template in the gotoHuman node. In the "gotoHuman: Fetch approved examples" http nodes you need to add your formId. It is the ID of the review template that you just created/imported in gotoHuman. Requirements gotoHuman (human supervision, memory for self-learning) OpenAI (classification, drafting) Gmail or your preferred email provider (for email trigger+replies) Linear (ticketing) How to customize Expand or refine the categories used by the classifier. Update the prompt to reflect your own taxonomy. Filter fetched training data from gotoHuman by reviewer so the writer adapts to their personalized tone and preferences. Add more context to the AI email writer (calendar events, FAQs, product docs) to improve reply quality.

gotoHumanBy gotoHuman
353