Back to Catalog

Auto-edit images from Google Drive with Nano Banana and send via Gmail

Automate With MarcAutomate With Marc
1259 views
2/3/2026
Official Page

Auto-Edit Images from Google Drive with (Wavespeed) Nano Banana and Send via Gmail

When a new image is uploaded to a specific Google Drive folder, this workflow sends it to Wavespeed’s Google Nano Banana image editing API, waits for the edited version, and then emails the result automatically. Perfect for creators, marketers, and ops teams who want hands-off, consistent image edits with instant delivery to a stakeholder inbox.

👉 Watch step-by-step video tutorials of workflows like these on: www.youtube.com/@automatewithmarc

Highlights

Google Drive trigger detects new image uploads

Wavespeed API (Google Nano Banana) performs automated image editing

Polling loop checks job status until complete

Gmail auto-sends the edited image to your chosen recipient

Great for social media pipelines, product photo retouching, or team approvals

Apps & Nodes Used

Trigger: Google Drive Trigger (fileCreated in folder)

HTTP Request: POST to Wavespeed (submit edit job)

Wait: Delay before first status check (15s)

HTTP Request: GET result (poll prediction status)

IF: Status == completed → proceed, else wait & recheck

Gmail: Send edited image output to recipient

Prerequisites

n8n account (Cloud or Self-hosted)

Google Drive folder for uploads

Wavespeed API key (HTTP Header Auth)

Gmail account with OAuth2 connected to n8n

Configuration (5 Steps)

Google Drive Trigger – set to your image upload folder.

POST Image Edit Request – sends file URL + prompt (default: “Change the lighting to night scene”).

Wait 15s – lets the job start.

GET Image Edit Request – checks prediction status/result.

IF → Gmail – once status = completed, send edited image to your chosen email.

Customization

Change the prompt (e.g., “remove background”, “enhance product lighting”).

Set Gmail recipient dynamically or statically.

Adjust polling wait times based on job length.

Save results to Drive/S3 instead of email if needed.

Error Handling

Add IF nodes to catch API errors. Set a retry limit to avoid infinite loops. Use Drive “Share File” if API can’t access the uploaded file link.

Auto-Edit Images from Google Drive with Nano Banana and Send via Gmail

This n8n workflow automates the process of detecting new images in a specified Google Drive folder, sending them for processing to the Nano Banana API, and then emailing the processed images.

What it does

  1. Monitors Google Drive: Continuously checks a designated Google Drive folder for new or updated image files.
  2. Sends to Nano Banana API: When a new image is detected, it makes an HTTP request to the Nano Banana API, presumably to perform some image editing or analysis.
  3. Conditional Processing: Includes an 'If' node, indicating that further actions might depend on the outcome of the Nano Banana API call or specific conditions related to the image. (Note: The specific conditions are not detailed in the provided JSON, but the node's presence suggests conditional logic).
  4. Waits for Processing (Implicit): A 'Wait' node is included, which might be used to pause the workflow, potentially allowing time for the Nano Banana API to complete its processing or for a manual review step.
  5. Sends Email via Gmail: After processing (and any waiting period), the workflow sends an email using Gmail, likely containing the processed image or a link to it.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • Google Drive Account: Configured with credentials in n8n to allow access to the specified folder.
  • Gmail Account: Configured with credentials in n8n to send emails.
  • Nano Banana API Key/Endpoint: Access to the Nano Banana API for image processing. The HTTP Request node will need the correct API endpoint and any necessary authentication (e.g., API key in headers or query parameters).

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Google Drive Trigger:
    • Set up your Google Drive credentials.
    • Specify the Google Drive folder ID that the workflow should monitor for new images.
  3. Configure HTTP Request (Nano Banana):
    • Update the "HTTP Request" node with the correct Nano Banana API endpoint.
    • Add any required authentication (e.g., API key) in the headers or query parameters.
    • Ensure the request body correctly sends the image data from the Google Drive trigger.
  4. Configure If Node: Review and configure the conditions in the "If" node if specific logic is required based on the Nano Banana API response or image properties.
  5. Configure Wait Node: Adjust the duration of the "Wait" node as needed, depending on the expected processing time for the Nano Banana API or any desired delay.
  6. Configure Gmail Node:
    • Set up your Gmail credentials.
    • Specify the recipient email address(es), subject, and body for the email.
    • Attach the processed image (or a link to it) from the Nano Banana API response.
  7. Activate the Workflow: Once all configurations are complete, activate the workflow to start monitoring your Google Drive folder.

Related Templates

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

AI multi-agent executive team for entrepreneurs with Gemini, Perplexity and WhatsApp

This workflow is an AI-powered multi-agent system built for startup founders and small business owners who want to automate decision-making, accountability, research, and communication, all through WhatsApp. The “virtual executive team,” is designed to help small teams to work smarter. This workflow sends you market analysis, market and sales tips, It can also monitor what your competitors are doing using perplexity (Research agent) and help you stay a head, or make better decisions. And when you feeling stuck with your start-up accountability director is creative enough to break the barrier 🎯 Core Features 🧑‍💼 1. President (Super Agent) Acts as the main controller that coordinates all sub-agents. Routes messages, assigns tasks, and ensures workflow synchronization between the AI Directors. 📊 2. Sales & Marketing Director Uses SerpAPI to search for market opportunities, leads, and trends. Suggests marketing campaigns, keywords, or outreach ideas. Can analyze current engagement metrics to adjust content strategy. 🕵️‍♀️ 3. Business Research Director Powered by Perplexity AI for competitive and market analysis. Monitors competitor moves, social media engagement, and product changes. Provides concise insights to help the founder adapt and stay ahead. ⏰ 4. Accountability Director Keeps the founder and executive team on track. Sends motivational nudges, task reminders, and progress reports. Promotes consistency and discipline — key traits for early-stage success. 🗓️ 5. Executive Secretary Handles scheduling, email drafting, and reminders. Connects with Google Calendar, Gmail, and Sheets through OAuth. Automates follow-ups, meeting summaries, and notifications directly via WhatsApp. 💬 WhatsApp as the Main Interface Interact naturally with your AI team through WhatsApp Business API. All responses, updates, and summaries are delivered to your chat. Ideal for founders who want to manage operations on the go. ⚙️ How It Works Trigger: The workflow starts from a WhatsApp Trigger node (via Meta Developer Account). Routing: The President agent analyzes the incoming message and determines which Director should handle it. Processing: Marketing or sales queries go to the Sales & Marketing Director. Research questions are handled by the Business Research Director. Accountability tasks are assigned to the Accountability Director. Scheduling or communication requests are managed by the Secretary. Collaboration: Each sub-agent returns results to the President, who summarizes and sends the reply back via WhatsApp. Memory: Context is maintained between sessions, ensuring personalized and coherent communication. 🧩 Integrations Required Gemini API – for general intelligence and task reasoning Supabase- for RAG and postgres persistent memory Perplexity API – for business and competitor analysis SerpAPI – for market research and opportunity scouting Google OAuth – to connect Sheets, Calendar, and Gmail WhatsApp Business API – for message triggers and responses 🚀 Benefits Acts like a team of tireless employees available 24/7. Saves time by automating research, reminders, and communication. Enhances accountability and strategy consistency for founders. Keeps operations centralized in a simple WhatsApp interface. 🧰 Setup Steps Create API credentials for: WhatsApp (via Meta Developer Account) Gemini, Perplexity, and SerpAPI Google OAuth (Sheets, Calendar, Gmail) Create a supabase account at supabase Add the credentials in the corresponding n8n nodes. Customize the system prompts for each Director based on your startup’s needs. Activate and start interacting with your virtual executive team on WhatsApp. Use Case You are a small organisation or start-up that can not afford hiring; marketing department, research department and secretar office, then this workflow is for you 💡 Need Customization? Want to tailor it for your startup or integrate with CRM tools like Notion or HubSpot? You can easily extend the workflow or contact the creator for personalized support. Consider adjusting the system prompt to suite your business

ShadrackBy Shadrack
331

🎓 How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616