HumationHuman + Automation
Back to Catalog

Generate & upload images with Image-to-Image GPT, Google Sheets & Drive

Evoort SolutionsEvoort Solutions
1385 views
2/3/2026
IntegrationData ProcessingAutomationEventsGoogle Calendar
Official Page

🖼️ Image-to-Image AI Generator from Google Sheets with Google Drive Upload

✅ Use Case

Automatically generate AI images from prompts listed in a Google Sheet, upload the images to Google Drive, and log the result back into the sheet.

Uses the image-to-image-gpt API for fast, customizable generation.

💡 Problem It Solves

Manual image generation workflows are inefficient and error-prone. Creative and content teams often have to:

  • Manually paste prompts into image generation tools
  • Save images locally
  • Upload to Google Drive
  • Paste the link back into tracking spreadsheets

This automation removes all that friction—turning one spreadsheet into a complete image creation pipeline.

🌟 Benefits

  • 🔁 Fully automated image generation
  • 📤 Direct uploads to Google Drive
  • 🧾 Image links and timestamps logged in Google Sheets
  • ⚠️ Built-in error logging for API failures
  • 🧩 Modular and easily extensible
  • 📊 Keeps a historical log of successes and errors

🧩 Workflow Overview

| Node | Description | |------|-------------| | 1. Manual Trigger | Starts the workflow when executed manually | | 2. Google Sheets2 | Reads all rows from the input Google Sheet | | 3. Loop Over Items | Processes one row (prompt) at a time | | 4. If2 | Filters only rows where Prompt is not empty and drive path is empty | | 5. HTTP Request1 | Calls the image-to-image-gpt API with the prompt | | 6. If1 (Error Handling) | If an error exists in the API response, route to logging | | 7. Google Sheets4 (Error Log) | Appends error details to a log sheet for review | | 8. Code1 | Decodes the base64 image returned by the API | | 9. Google Drive1 | Uploads the image to a selected Google Drive folder | | 10. Google Sheets1 (Write Back) | Updates the original row with the image drive path and timestamp | | 11. Wait | Delays the next prompt to prevent hitting API rate limits |

🛠 Tech Stack

  • n8n (no-code automation)
  • Google Sheets (data input/output)
  • Google Drive (image storage)
  • image-to-image-gpt API via RapidAPI
  • JavaScript (in Code node) for base64 processing

📝 Sheet Format

Your Google Sheet should include the following columns:

| Column | Purpose | |----------------|----------------------------------| | Prompt | The AI prompt to send to the API | | Image url | (Optional) Initial image URL | | drive path | Updated with Drive link by flow | | Generated Date | Auto-filled by the workflow | | Base64 | Stores raw or error data |

🚀 How to Use

  1. Import this workflow into your n8n instance
  2. Set up Google Sheets and Google Drive service credentials
  3. Add your RapidAPI key in the HTTP Request node headers
  4. Use the image-to-image-gpt endpoint in the HTTP request
  5. Configure the Google Sheet and Drive folder in the respective nodes
  6. Execute manually or add a Cron node for scheduling

📌 Example Applications

  • 🛍 eCommerce: Auto-generate product mockups
  • 🧵 Fashion/Design: Visualize styles or fabrics from prompts
  • ✍️ Blogging/Content: Auto-generate header images from titles
  • 📣 Marketing: Generate ad banners from text

🧪 Tips

  • You can add a Cron node if you want this to run on a schedule
  • Use a separate tab/sheet for logging failed prompts
  • Extend the flow by adding:
    • Email notifications
    • Slack alerts
    • File name templating

Create your free n8n account and set up the workflow in just a few minutes using the link below:

👉 Start Automating with n8n

Save time, stay consistent, and grow your LinkedIn presence effortlessly!

Generate and Upload Images with Image-to-Image GPT and Google Sheets/Drive

This n8n workflow automates the process of generating images based on descriptions in a Google Sheet, applying image-to-image transformations using a GPT model, and then uploading the generated images to Google Drive. It's ideal for content creators, marketers, or anyone needing to rapidly produce and manage visual assets from textual prompts.

What it does

  1. Triggers Manually: The workflow is initiated by a manual trigger, allowing you to control when the image generation process starts.
  2. Reads Data from Google Sheets: It connects to a specified Google Sheet to retrieve image generation prompts and other relevant data.
  3. Loops Over Items: For each row (item) read from the Google Sheet, the workflow processes it individually.
  4. Generates and Transforms Images (via HTTP Request): It makes an HTTP request to an external API (presumably an image-to-image GPT model) to generate new images based on the input from Google Sheets.
  5. Conditional Processing: An "If" node likely checks for a condition (e.g., successful image generation, specific data fields) to determine the next steps.
  6. Uploads to Google Drive: If the condition is met, the generated images are uploaded to a designated folder in Google Drive.
  7. Waits (Optional Delay): A "Wait" node can introduce a delay between operations, potentially to manage API rate limits or ensure proper synchronization.
  8. Executes Custom Code: A "Code" node allows for custom JavaScript logic, which could be used for data manipulation, logging, or advanced error handling.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • Google Account: A Google account with access to Google Sheets and Google Drive.
  • Google Sheets Credential: An n8n credential configured for Google Sheets.
  • Google Drive Credential: An n8n credential configured for Google Drive.
  • Image-to-Image GPT API: Access to an external API for image generation and transformation (e.g., OpenAI DALL-E, Stability AI, Midjourney, or a custom service). This will require an API key or other authentication details configured within the HTTP Request node.

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 from which to read the image prompts.
  3. Configure HTTP Request Node:
    • Set up the URL for your image-to-image GPT API.
    • Configure the HTTP method (likely POST).
    • Add any necessary headers (e.g., Authorization with your API key).
    • Map the input data from Google Sheets (e.g., image description, style parameters) to the request body of the API call.
    • Adjust the response handling to correctly parse the image data.
  4. Configure Google Drive Node:
    • Select your Google Drive credential.
    • Specify the folder ID where the generated images should be uploaded.
    • Map the image data received from the HTTP Request node to the file content for upload.
    • Define the filename for the uploaded images (e.g., using data from Google Sheets).
  5. Configure If Node:
    • Define the conditions for successful image generation or any other logic you need to implement before uploading to Google Drive.
  6. Configure Code Node (Optional):
    • If needed, add custom JavaScript logic to process data, format responses, or handle specific scenarios.
  7. Configure Wait Node (Optional):
    • Adjust the delay duration if you need to space out API calls or other operations.
  8. Activate the Workflow: Ensure the workflow is active.
  9. Execute Manually: Click "Execute Workflow" in the Manual Trigger node to run the workflow.

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.

Ranjan DailataBy Ranjan Dailata
161

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 invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942