HumationHuman + Automation
Back to Catalog

Batch ID photo converter & enhancer with Google Drive & Nano Banana API

panyanyanypanyanyany
722 views
2/3/2026
eCommerceWebhookPayment GatewaySubscriptionStripe
Official Page

Overview

This n8n workflow automatically converts and enhances multiple photos into professional ID-style portraits using Gemini AI (Nano Banana). It processes images in batch from Google Drive, applies professional ID photo standards (proper framing, neutral background, professional attire), and outputs the enhanced photos back to Google Drive.

Input: Google Drive folder with photos
Output: Professional ID-style portraits in Google Drive output folder

The workflow uses a simple form interface where users provide Google Drive folder URLs and an optional custom prompt. It automatically fetches all images from the input folder, processes each through the Defapi API with Google's nano-banana model, monitors generation status, and uploads finished photos to the output folder. Perfect for HR departments, recruitment agencies, or anyone needing professional ID photos in bulk.

Prerequisites

  • A Defapi account and API key (Bearer token configured in n8n credentials): Sign up at Defapi.org
  • An active n8n instance with Google Drive integration
  • Google Drive account with two public folders:
    • Input folder: Contains photos to be processed (must be set to public/anyone with the link)
    • Output folder: Where enhanced photos will be saved (must be set to public/anyone with the link)
  • Photos with clear faces (headshots or upper body shots work best)

Setup Instructions

1. Prepare Google Drive Folders

  • Create two Google Drive folders:
    • One for input photos (e.g., https://drive.google.com/drive/folders/xxxxxxx)
    • One for output photos (e.g., https://drive.google.com/drive/folders/yyyyyy)
  • Important: Make both folders public (set sharing to "Anyone with the link can view")
    • Right-click folder → Share → Change "Restricted" to "Anyone with the link"
  • Upload photos to the input folder (supported formats: .jpg, .jpeg, .png, .webp)

2. Configure n8n Credentials

  • Defapi API: Add HTTP Bearer Auth credential with your Defapi API token (credential name: "Defapi account")
  • Google Drive: Connect your Google Drive OAuth2 account (credential name: "Google Drive account"). See https://docs.n8n.io/integrations/builtin/credentials/google/oauth-generic/

3. Run the Workflow

  • Execute the workflow in n8n
  • Access the form submission URL
  • Fill in the form:
    • Google Drive - Input Folder URL: Paste your input folder URL
    • Google Drive - Output Folder URL: Paste your output folder URL
    • Prompt (optional): Customize the AI generation prompt or leave blank to use the default

4. Monitor Progress

The workflow will:

  • Fetch all images from the input folder
  • Process each image through the AI model
  • Wait for generation to complete (checks every 10 seconds)
  • Download and upload enhanced photos to the output folder

Workflow Structure

The workflow consists of the following nodes:

  1. On form submission (Form Trigger) - Collects Google Drive folder URLs and optional prompt
  2. Search files and folders (Google Drive) - Retrieves all files from the input folder
  3. Code in JavaScript (Code Node) - Prepares image data and prompt for API request
  4. Send Image Generation Request to Defapi.org API (HTTP Request) - Submits generation request for each image
  5. Wait for Image Processing Completion (Wait Node) - Waits 10 seconds before checking status
  6. Obtain the generated status (HTTP Request) - Polls API for completion status
  7. Check if Image Generation is Complete (IF Node) - Checks if status is not "pending"
  8. Format and Display Image Results (Set Node) - Formats result with markdown and image URL
  9. HTTP Request (HTTP Request) - Downloads the generated image file
  10. Upload file (Google Drive) - Uploads the enhanced photo to the output folder

Default Prompt

The workflow uses this professional ID photo generation prompt by default:

Create a professional portrait suitable for ID documentation with proper spacing and composition.

Framing: Include the full head, complete shoulder area, and upper torso. Maintain generous margins around the subject without excessive cropping.

Outfit: Transform the existing attire into light business-casual clothing appropriate for the individual's demographics and modern style standards. Ensure the replacement garment appears natural, properly tailored, and complements the subject's overall presentation (such as professional shirt, refined blouse, contemporary blazer, or sophisticated layered separates).

Pose & Gaze: Position shoulders square to the camera, maintaining perfect frontal alignment. Direct the gaze straight ahead into the lens at identical eye height, avoiding any angular deviation in vertical or horizontal planes.

Expression: Display a professional neutral demeanor or subtle closed-lip smile that conveys confidence and authenticity.

Background: Utilize a solid, consistent light gray photographic background (color code: #d9d9d9) without any pattern, texture, or tonal variation.

Lighting & Quality: Apply balanced studio-quality illumination eliminating harsh contrast or reflective artifacts. Deliver maximum resolution imagery with precise focus and accurate natural skin color reproduction.

Customization Tips for Different ID Photo Types

Based on the default prompt structure, here are specific customization points for different use cases:

1. Passport & Visa Photos

Key Requirements: Most countries require white or light-colored backgrounds, neutral expression, no smile.

Prompt Modifications:

  • Background: Change to Plain white background (#ffffff) or Light cream background (#f5f5f5)
  • Expression: Change to Completely neutral expression, no smile, mouth closed, serious but not tense
  • Framing: Add Head size should be 70-80% of the frame height. Top of head to chin should be prominent
  • Outfit: Change to Replace with dark formal suit jacket and white collared shirt or Navy blue blazer with light shirt
  • Additional: Add No glasses glare, ears must be visible, no hair covering the face

2. Corporate Employee ID / Work Badge

Key Requirements: Professional but approachable, company-appropriate attire.

Prompt Modifications:

  • Background: Use company color or standard #e6f2ff (light blue), #f0f0f0 (light gray)
  • Expression: Keep Soft closed-mouth smile — confident and approachable
  • Outfit: Change to specific dress code:
    • Corporate: Dark business suit with tie for men, blazer with blouse for women
    • Tech/Startup: Smart casual polo shirt or button-down shirt without tie
    • Creative: Clean, professional casual clothing that reflects company culture
  • Framing: Use default or add Upper chest visible with company badge area clear

3. University/School Student ID

Key Requirements: Friendly, youthful, appropriate for educational setting.

Prompt Modifications:

  • Background: Use school colors or Light blue (#e3f2fd), Soft gray (#f5f5f5)
  • Expression: Change to Friendly natural smile or pleasant neutral expression
  • Outfit: Change to Replace with clean casual clothing — collared shirt, polo, or neat sweater. No logos or graphics
  • Framing: Keep default
  • Additional: Add Youthful, fresh appearance suitable for educational environment

4. Driver's License / Government ID

Key Requirements: Strict standards, neutral expression, specific background colors.

Prompt Modifications:

  • Background: Check local requirements — often White (#ffffff), Light gray (#d9d9d9), or Light blue (#e6f2ff)
  • Expression: Change to Neutral expression, no smile, mouth closed, eyes fully open
  • Outfit: Use Replace with everyday casual or business casual clothing — collared shirt or neat top
  • Framing: Add Head centered, face taking up 70-80% of frame, ears visible
  • Additional: Add No glasses (or non-reflective lenses), no headwear except religious purposes, natural hair

5. Professional LinkedIn / Resume Photo

Key Requirements: Polished, confident, approachable.

Prompt Modifications:

  • Background: Use Soft gray (#d9d9d9) or Professional blue gradient (#e3f2fd to #bbdefb)
  • Expression: Keep Confident, warm smile — professional yet approachable
  • Outfit: Change to:
    • Executive: Premium business suit, crisp white shirt, tie optional
    • Professional: Tailored blazer over collared shirt or elegant blouse
    • Creative: Smart business casual with modern, well-fitted clothing
  • Framing: Change to Show head, full shoulders, and upper chest. Slightly more relaxed framing than strict ID photo
  • Lighting: Add Soft professional lighting with slight catchlight in eyes to appear engaging

6. Medical/Healthcare Professional Badge

Key Requirements: Clean, trustworthy, professional medical appearance.

Prompt Modifications:

  • Background: Use Clinical white (#ffffff) or Soft medical blue (#e3f2fd)
  • Expression: Change to Calm, reassuring expression with gentle smile
  • Outfit: Change to Replace with clean white lab coat over professional attire or Medical scrubs in appropriate color (navy, ceil blue, or teal)
  • Additional: Add Hair neatly pulled back if long, clean professional appearance, no flashy jewelry

7. Gym/Fitness Membership Card

Key Requirements: Casual, recognizable, suitable for athletic environment.

Prompt Modifications:

  • Background: Use Bright white (#ffffff) or gym brand color
  • Expression: Change to Natural friendly smile or neutral athletic expression
  • Outfit: Change to Replace with athletic wear — sports polo, performance t-shirt, or athletic jacket in solid colors
  • Framing: Keep default
  • Additional: Add Casual athletic appearance, hair neat

General Customization Parameters

Background Color Options:

  • White: #ffffff (passport, visa, formal government IDs)
  • Light gray: #d9d9d9 (default, versatile for most purposes)
  • Light blue: #e6f2ff (corporate, professional)
  • Cream: #f5f5dc (warm professional)
  • Soft blue-gray: #eceff1 (modern corporate)

Expression Variations:

  • Strict Neutral: "Completely neutral expression, no smile, mouth closed, serious but relaxed"
  • Soft Smile: "Very soft closed-mouth smile — confident and natural" (default)
  • Friendly Smile: "Warm natural smile with slight teeth showing — approachable and professional"
  • Calm Professional: "Calm, composed expression with slight pleasant demeanor"

Clothing Formality Levels:

  • Formal: "Dark suit, white dress shirt, tie for men / tailored suit or blazer with professional blouse for women"
  • Business Casual (default): "Light business-casual outfit — clean shirt/blouse, lightweight blazer, or smart layers"
  • Smart Casual: "Collared shirt, polo, or neat sweater in solid professional colors"
  • Casual: "Clean, neat casual top — solid color t-shirt, casual button-down, or simple blouse"

Framing Adjustments:

  • Tight Crop: "Head and shoulders only, face fills 80% of frame" (passport style)
  • Standard Crop (default): "Entire head, full shoulders, and upper chest with balanced space"
  • Relaxed Crop: "Head, shoulders, and chest visible, with more background space for professional portraits"

n8n Form Triggered Photo Converter & Enhancer

This n8n workflow automates the process of receiving an image URL via a form, determining if it's a photo of a person, and if so, enhancing it using the Nano Banana API before uploading it to Google Drive.

Description

This workflow simplifies and automates the enhancement and storage of photos submitted through an n8n form. It intelligently identifies if the submitted image is a photo of a person, then leverages an external API for enhancement, and finally organizes the processed image in Google Drive. This is ideal for scenarios requiring automated image processing and categorization, such as ID photo submissions or profile picture updates.

What it does

  1. Triggers on Form Submission: The workflow starts when a user submits data through an n8n form.
  2. Extracts Image URL: It processes the form submission to extract the image URL provided by the user.
  3. Sets Image Data: The workflow prepares the image URL for further processing by setting it as a variable.
  4. Checks for Person Photo: It makes an HTTP request to the Nano Banana API to determine if the submitted image contains a person.
  5. Conditional Processing:
    • If a person is detected: The workflow proceeds to enhance the photo.
    • If no person is detected: The workflow stops, indicating that only person photos are processed.
  6. Enhances Photo (if person detected): It makes another HTTP request to the Nano Banana API to enhance the photo.
  7. Waits for Enhancement: A short delay is introduced to ensure the enhancement process is complete.
  8. Uploads to Google Drive: The enhanced photo is then uploaded to a specified folder in Google Drive.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • Nano Banana API Key: An API key for the Nano Banana API (used for person detection and photo enhancement).
  • Google Drive Account: A Google Drive account connected to n8n with appropriate permissions to create/upload files.
  • n8n Form: An n8n form configured to accept an image URL as input.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • HTTP Request (Nano Banana API): Configure the HTTP Request nodes (nodes 19 and 20) with your Nano Banana API key. This will likely involve setting a header or query parameter with your API key.
    • Google Drive: Set up your Google Drive credential in n8n.
  3. Configure Form Trigger: Ensure your "On form submission" node (node 1225) is correctly set up to receive the image URL from your form.
  4. Activate the Workflow: Once configured, activate the workflow.
  5. Submit Forms: Submit an image URL through the n8n form to trigger the workflow.

The workflow will automatically detect if the image contains a person, enhance it, and upload it to your Google Drive.

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

🎓 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

Tax deadline management & compliance alerts with GPT-4, Google Sheets & Slack

AI-Driven Tax Compliance & Deadline Management System Description Automate tax deadline monitoring with AI-powered insights. This workflow checks your tax calendar daily at 8 AM, uses GPT-4 to analyze upcoming deadlines across multiple jurisdictions, detects overdue and critical items, and sends intelligent alerts via email and Slack only when immediate action is required. Perfect for finance teams and accounting firms who need proactive compliance management without manual tracking. 🏛️🤖📊 Good to Know AI-Powered: GPT-4 provides risk assessment and strategic recommendations Multi-Jurisdiction: Handles Federal, State, and Local tax requirements automatically Smart Alerts: Only notifies executives when deadlines are overdue or critical (≤3 days) Priority Classification: Categorizes deadlines as Overdue, Critical, High, or Medium priority Dual Notifications: Critical alerts to leadership + daily summaries to team channel Complete Audit Trail: Logs all checks and deadlines to Google Sheets for compliance records How It Works Daily Trigger - Runs at 8:00 AM every morning Fetch Data - Pulls tax calendar and company configuration from Google Sheets Analyze Deadlines - Calculates days remaining, filters by jurisdiction/entity type, categorizes by priority AI Analysis - GPT-4 provides strategic insights and risk assessment on upcoming deadlines Smart Routing - Only sends alerts if overdue or critical deadlines exist Critical Alerts - HTML email to executives + Slack alert for urgent items Team Updates - Slack summary to finance channel with all upcoming deadlines Logging - Records compliance check results to Google Sheets for audit trail Requirements Google Sheets Structure Sheet 1: TaxCalendar DeadlineID | DeadlineName | DeadlineDate | Jurisdiction | Category | AssignedTo | IsActive FED-Q1 | Form 1120 Q1 | 2025-04-15 | Federal | Income | John Doe | TRUE Sheet 2: CompanyConfig (single row) Jurisdictions | EntityType | FiscalYearEnd Federal, California | Corporation | 12-31 Sheet 3: ComplianceLog (auto-populated) Date | AlertLevel | TotalUpcoming | CriticalCount | OverdueCount 2025-01-15 | HIGH | 12 | 3 | 1 Credentials Needed Google Sheets - Service Account OAuth2 OpenAI - API Key (GPT-4 access required) SMTP - Email account for sending alerts Slack - Bot Token with chat:write permission Setup Steps Import workflow JSON into n8n Add all 4 credentials Replace these placeholders: YOURTAXCALENDAR_ID - Tax calendar sheet ID YOURCONFIGID - Company config sheet ID YOURLOGID - Compliance log sheet ID C12345678 - Slack channel ID tax@company.com - Sender email cfo@company.com - Recipient email Share all sheets with Google service account email Invite Slack bot to channels Test workflow manually Activate the trigger Customizing This Workflow Change Alert Thresholds: Edit "Analyze Deadlines" node: Critical: Change <= 3 to <= 5 for 5-day warning High: Change <= 7 to <= 14 for 2-week notice Medium: Change <= 30 to <= 60 for 2-month lookout Adjust Schedule: Edit "Daily Tax Check" trigger: Change hour/minute for different run time Add multiple trigger times for tax season (8 AM, 2 PM, 6 PM) Add More Recipients: Edit "Send Email" node: To: cfo@company.com, director@company.com CC: accounting@company.com BCC: archive@company.com Customize Email Design: Edit "Format Email" node to change colors, add logo, or modify layout Add SMS Alerts: Insert Twilio node after "Is Critical" for emergency notifications Integrate Task Management: Add HTTP Request node to create tasks in Asana/Jira for critical deadlines Troubleshooting | Issue | Solution | |-------|----------| | No deadlines found | Check date format (YYYY-MM-DD) and IsActive = TRUE | | AI analysis failed | Verify OpenAI API key and account credits | | Email not sending | Test SMTP credentials and check if critical condition met | | Slack not posting | Invite bot to channel and verify channel ID format | | Permission denied | Share Google Sheets with service account email | 📞 Professional Services Need help with implementation or customization? Our team offers: 🎯 Custom workflow development 🏢 Enterprise deployment support 🎓 Team training sessions 🔧 Ongoing maintenance 📊 Custom reporting & dashboards 🔗 Additional API integrations Discover more workflows – Get in touch with us

Oneclick AI SquadBy Oneclick AI Squad
93