Extract email tasks with Gmail, ChatGPT-4o and Supabase
📩 Gmail → GPT → Supabase | Task Extractor
This n8n workflow automates the extraction of actionable tasks from unread Gmail messages using OpenAI's GPT API, stores the resulting task metadata in Supabase, and avoids re-processing previously handled emails.
✅ What It Does
- Triggers on a schedule to check for unread emails in your Gmail inbox.
- Loops through each email individually using
SplitInBatches. - Checks Supabase to see if the email has already been processed.
- If it's a new email:
- Formats the email content into a structured GPT prompt
- Calls ChatGPT-4o to extract structured task data
- Inserts the result into your
emailstable in Supabase
🧰 Prerequisites
Before using this workflow, you must have:
- An active n8n Cloud or self-hosted instance
- A connected Gmail account with OAuth credentials in n8n
- A Supabase project with an
emailstable and:ALTER TABLE emails ADD CONSTRAINT unique_email_id UNIQUE (email_id); - An OpenAI API key with access to GPT-4o or GPT-3.5-turbo
🔐 Required Credentials
| Name | Type | Description | |-----------------|------------|-----------------------------------| | Gmail OAuth | Gmail | To pull unread messages | | OpenAI API Key | OpenAI | To generate task summaries | | Supabase API | HTTP | For inserting rows via REST API |
🔁 Environment Variables or Replacements
Supabase_TaskManagement_URI→ e.g.,https://your-project.supabase.coSupabase_TaskManagement_ANON_KEY→ Your Supabase anon key
These are used in the HTTP request to Supabase.
⏰ Scheduling / Trigger
- Triggered using a Schedule node
- Default: every X minutes (adjust to your preference)
- Uses a Gmail API filter: unread emails with label = INBOX
🧠 Intended Use Case
> Designed for productivity-minded professionals who want to extract, summarize, and store actionable tasks from incoming email — without processing the same email twice or wasting GPT API credits.
This is part of a larger system integrating GPT, calendar scheduling, and optional task platforms (like ClickUp).
📦 Output (Stored in Supabase)
Each processed email includes:
email_idsubjectsenderreceived_atbody(email snippet)gpt_summary(structured task)requires_deep_work(from GPT logic)deleted(initially false)
Extract Email Tasks with Gmail, ChatGPT-4o, and Supabase
This n8n workflow automates the process of identifying and extracting actionable tasks from your Gmail inbox, processing them with OpenAI's ChatGPT-4o, and storing them in a Supabase database. It helps you keep track of tasks embedded in your emails without manual sifting.
What it does
- Triggers on a Schedule: The workflow runs at a predefined interval (e.g., daily, hourly) to check for new emails.
- Fetches Unread Gmail Messages: It connects to your Gmail account and retrieves unread emails.
- Filters for Relevant Emails: An
Ifnode checks if the email subject or body contains keywords like "task", "todo", or "action item" to narrow down the relevant messages. - Extracts Tasks with OpenAI (ChatGPT-4o): For each filtered email, it sends the email content to OpenAI's ChatGPT-4o model, prompting it to identify and extract any explicit or implicit tasks.
- Processes OpenAI Response: A
Codenode then parses the response from OpenAI, extracting the structured task information. - Stores Tasks in Supabase: The extracted tasks are then inserted into a Supabase database, allowing for centralized task management.
- Marks Emails as Read (Optional): After processing, the workflow can mark the emails as read in Gmail to avoid reprocessing.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Account: A running instance of n8n (cloud or self-hosted).
- Gmail Account: A Google account with Gmail access and credentials configured in n8n.
- OpenAI API Key: An OpenAI API key with access to the
gpt-4omodel, configured as a credential in n8n. - Supabase Account: A Supabase project with a database table set up to store your tasks, and credentials configured in n8n.
- The table should ideally have columns for
task_description,email_subject,email_id,due_date(if extractable),priority, etc.
- The table should ideally have columns for
Setup/Usage
- Import the Workflow:
- Download the provided JSON file.
- In your n8n instance, go to "Workflows" and click "New".
- Click the "Import from JSON" button and paste the workflow JSON or upload the file.
- Configure Credentials:
- Locate the Gmail node and configure your Google OAuth2 credentials.
- Locate the OpenAI node and configure your OpenAI API Key credentials.
- Locate the Supabase node and configure your Supabase API credentials (Project URL and API Key).
- Customize Nodes:
- Schedule Trigger: Adjust the schedule to your preferred frequency (e.g., every 30 minutes, once a day).
- Gmail: You might want to adjust the "Label" or "Query" parameters to refine which emails are fetched (e.g.,
is:unread in:inbox category:primary). - If: Refine the conditions in the
Ifnode to better filter emails relevant to tasks based on your specific needs. - OpenAI: Review the prompt used to extract tasks. You might want to modify it to include specific instructions for task format or additional details you want to extract (e.g., "Extract tasks, due dates, and assignees in JSON format.").
- Code: If you modify the OpenAI prompt to return a different JSON structure, you will need to update the
Codenode to correctly parse the new format. - Supabase: Ensure the table name and column mappings in the Supabase node match your Supabase database schema.
- Activate the Workflow: Once configured, activate the workflow by toggling the "Active" switch in the top right corner of the workflow editor.
The workflow will now automatically run on its schedule, process your emails, and populate your Supabase database with extracted tasks.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
Two-way property repair management system with Google Sheets & Drive
This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.
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