HumationHuman + Automation
Back to Catalog

Transform images with AI prompts using FLUX Kontext, Google Sheets and Drive

DavideDavide
2067 views
2/3/2026
AirtableZendeskAutomationData SyncAPI
Official Page

This workflow automates the generation of AI-enhanced, contextualized images using FLUX Kontext, based on prompts stored in a Google Sheet. The generated images are then saved to Google Drive, and their URLs are written back to the spreadsheet for easy access.

Example

Image: image

Prompt: The girl is lying on the bed and sleeping

Result: image

Perfect for E-commerce and Social Media

This workflow is especially useful for e-commerce businesses:

  • Generate product images with dynamic backgrounds based on the use-case or season.
  • Create contextual marketing visuals for ads, newsletters, or product pages.
  • Scale visual content creation without the need for manual design work.

How It Works

  • Trigger: The workflow can be started manually (via "Test workflow") or scheduled at regular intervals (e.g., every 5 minutes) using the "Schedule Trigger" node.
  • Data Fetch: The "Get new image" node retrieves a row from a Google Sheet where the "RESULT" column is empty. It extracts the prompt, image URL, output format, and aspect ratio for processing.
  • Image Generation: The "Create Image" node sends a request to the FLUX Kontext API (fal.run) with the provided parameters to generate a new AI-contextualized image.
  • Status Check: The workflow waits 60 seconds ("Wait 60 sec." node) before checking the status of the image generation request via the "Get status" node. If the status is "COMPLETED," it proceeds; otherwise, it loops back to wait.
  • Result Handling: Once completed, the "Get Image Url" node fetches the generated image URL, which is then downloaded ("Get Image File"), uploaded to Google Drive ("Upload Image"), and the Google Sheet is updated with the result ("Update result").

Set Up Steps

To configure this workflow, follow these steps:

  1. Google Sheet Setup:

    • Create a Google Sheet with columns for PROMPT, IMAGE URL, ASPECT RATIO, OUTPUT FORMAT, and RESULT (leave this empty).
    • Link the sheet in the "Get new image" and "Update result" nodes.

  2. API Key Configuration:

    • Sign up at fal.ai to obtain an API key.
    • In the "Create Image" node, set the Header Auth with:
      • Name: Authorization
      • Value: Key YOURAPIKEY

  3. Google Drive Setup:

    • Specify the target folder ID in the "Upload Image" node where generated images will be saved.

  4. Schedule Trigger (Optional):

    • Adjust the "Schedule Trigger" node to run the workflow at desired intervals (e.g., every 5 minutes).

  5. Test Execution:

    • Run the workflow manually via the "Test workflow" node to verify all steps function correctly.

Once configured, the workflow will automatically process pending prompts, generate images, and update the Google Sheet with results.

Need help customizing?

Contact me for consulting and support or add me on Linkedin.

n8n Workflow: Transform Images with AI Prompts using Flux, Kontext, Google Sheets, and Drive

This n8n workflow demonstrates a robust process for generating and managing AI-transformed images based on prompts. It orchestrates interactions between Google Sheets, an external AI image transformation service (implied by HTTP Request), and Google Drive, allowing for automated image generation and storage.

What it does

This workflow automates the following steps:

  1. Triggers Manually or on Schedule: The workflow can be initiated manually or set to run at scheduled intervals.
  2. Reads Data from Google Sheets: It fetches data from a specified Google Sheet, likely containing image prompts or other relevant metadata.
  3. Sends HTTP Request for Image Transformation: It makes an HTTP request to an external service (e.g., Flux, Kontext, or a similar AI image generation API) to transform images based on the data retrieved from Google Sheets.
  4. Waits for Processing: A Wait node is included, suggesting that the external image transformation service might take some time to process, allowing the workflow to pause before proceeding.
  5. Conditional Logic: An If node introduces conditional logic, allowing the workflow to branch based on the outcome of the image transformation or other criteria.
  6. Uploads to Google Drive: Depending on the If node's evaluation, it uploads the transformed images or related files to Google Drive.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Google Account: Access to Google Sheets and Google Drive with appropriate permissions.
  • Google Sheets Credentials: Configured Google Sheets credentials in n8n.
  • Google Drive Credentials: Configured Google Drive credentials in n8n.
  • AI Image Transformation Service: Access to an external AI image transformation API (e.g., Flux, Kontext, or another service that accepts HTTP requests for image generation/transformation). You will need its API endpoint and any required authentication details for the HTTP Request node.

Setup/Usage

  1. Import the Workflow:
    • Copy the provided JSON code.
    • In your n8n instance, click "New Workflow" and then "Import from JSON".
    • Paste the JSON code and click "Import".
  2. Configure Credentials:
    • Locate the "Google Sheets" node and configure your Google Sheets credentials.
    • Locate the "Google Drive" node and configure your Google Drive credentials.
  3. Configure HTTP Request:
    • Locate the "HTTP Request" node.
    • Update the URL, HTTP Method, Headers (for API keys/authentication), and Body (to send your image prompts or data) according to your AI image transformation service's API documentation.
  4. Configure Google Sheets Node:
    • Specify the Spreadsheet ID and Sheet Name from which the workflow should read data.
  5. Configure Google Drive Node:
    • Specify the folder ID or path where the transformed images should be uploaded.
  6. Configure If Node:
    • Adjust the conditions in the "If" node to match your desired logic based on the output of the HTTP Request node.
  7. Configure Schedule Trigger (Optional):
    • If you want the workflow to run automatically, configure the "Schedule Trigger" node with your desired interval (e.g., every hour, daily).
  8. Activate the Workflow: Once all configurations are complete, activate the workflow. You can then trigger it manually using the "When clicking ‘Execute workflow’" node or let the "Schedule Trigger" handle it.

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

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.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

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