Generate images from text prompts with Google Imagen 3 via Replicate API
Who is this for?
This n8n workflow is designed for developers, digital artists, and content creators who want to leverage the power of AI-generated images using the Replicate API.
What problem is this workflow solving? / Use case
The workflow automates the process of generating images from textual prompts using the Replicate API. It allows users to generate, check the status of, and retrieve images with minimal manual intervention.
What this workflow does
- Initialize Workflow: Triggered by a manual click, the workflow starts with a prompt for image generation.
- Set Image Generation Parameters: The user can define a prompt and other parameters, which will be sent to the Replicate API for processing.
- Create Prediction: The workflow sends a request to generate an image based on the provided input.
- Check Prediction Status: After a short waiting period, the workflow checks the status of the image generation process.
- Handle Errors: If the status indicates an error (e.g., "failed" or "canceled"), the workflow stops and reports an error.
- Retrieve Image URL: If the image generation is successful, it retrieves and outputs the URL of the generated image.
Setup
- Replicate API Key:
- Go to the Replicate website and sign up for an account if you don’t have one.
- Generate an API key from your Replicate dashboard.
- Configure HTTP Credentials:
- In n8n, navigate to the "Credentials" section and create a new HTTP Header Authentication credential.
- Set the name to
Authorization, and enterBearer YOUR_REPLICATE_API_KEYin the value field, replacingYOUR_REPLICATE_API_KEYwith your actual API key.
How to customize this workflow to your needs
- Edit the Prompt Text: Change the text in the "Set prompt" node to customize the image you want to generate. This can be adjusted to include dynamic input from other parts of your n8n workflow.
- Change Image Generation Settings: In the "Create prediction" node, you may modify any parameters such as aspect ratio, safety filter level, or even the model being used by changing the URL.
- Add More Logic: If you want to add more complex logic or branching conditions based on the image generation results, modify the "Check for success" and "Check for errors" nodes accordingly.
- Modify Wait Duration: Depending on your application, you may want to adjust the waiting times in the "Wait" and "Pause" nodes to optimize processing time based on expected image generation speed.
n8n Workflow: Basic Workflow Structure Example
This n8n workflow demonstrates a foundational structure for building automations, incorporating manual triggers, data manipulation, conditional logic, API requests, and error handling. It serves as a template for more complex workflows by showcasing essential n8n nodes and their interconnections.
What it does
This workflow outlines a common automation pattern, allowing you to manually initiate a process, prepare data, make decisions, interact with external services, and handle potential issues.
- Starts manually: The workflow is triggered by a user clicking the 'Execute workflow' button in the n8n interface.
- Edits Fields: Data can be transformed or set using the "Edit Fields (Set)" node. This is a placeholder for any data preparation needed before further processing.
- Applies Conditional Logic: An "If" node allows for branching logic based on specific conditions. Data can be routed down different paths depending on whether a condition evaluates to true or false.
- Makes an HTTP Request: An "HTTP Request" node is included, representing an interaction with an external API or web service. This is where the workflow would typically send or retrieve data from another platform.
- Introduces a Delay: A "Wait" node can be used to pause the workflow for a specified duration, useful for rate limiting, waiting for external processes, or scheduling.
- Handles Errors: A "Stop and Error" node is present to explicitly stop the workflow and report an error, providing a mechanism for graceful failure handling when unexpected conditions occur.
- Provides Documentation: A "Sticky Note" node is used for in-workflow documentation, explaining parts of the workflow or providing context.
Prerequisites/Requirements
- An active n8n instance.
- No external API keys or accounts are strictly required for this basic structure, but they would be necessary if you were to implement specific functionality in the "HTTP Request" node.
Setup/Usage
- Import the workflow:
- Copy the provided JSON code.
- In your n8n instance, click on "Workflows" in the left sidebar.
- Click "New Workflow" or import the JSON directly.
- Configure nodes (as needed):
- Edit Fields (Set) (Node 38): Modify the fields to set or transform data relevant to your specific use case.
- If (Node 20): Define your conditional logic (e.g., check a value, compare strings) to route the workflow appropriately.
- HTTP Request (Node 19): Configure the URL, method, headers, and body for the API call you intend to make.
- Wait (Node 514): Adjust the delay duration if you need to pause the workflow.
- Stop and Error (Node 528): Customize the error message if desired.
- Sticky Note (Node 565): Update the note with relevant information for your workflow.
- Execute the workflow:
- Click the "Execute Workflow" button on the "When clicking ‘Execute workflow’" node (Node 838) to manually run the workflow.
- Alternatively, activate the workflow by toggling the "Active" switch in the top right corner if you configure a different trigger (not included in this base example).
Related Templates
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
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
AI-powered code review with linting, red-marked corrections in Google Sheets & Slack
Advanced Code Review Automation (AI + Lint + Slack) Who’s it for For software engineers, QA teams, and tech leads who want to automate intelligent code reviews with both AI-driven suggestions and rule-based linting — all managed in Google Sheets with instant Slack summaries. How it works This workflow performs a two-layer review system: Lint Check: Runs a lightweight static analysis to find common issues (e.g., use of var, console.log, unbalanced braces). AI Review: Sends valid code to Gemini AI, which provides human-like review feedback with severity classification (Critical, Major, Minor) and visual highlights (red/orange tags). Formatter: Combines lint and AI results, calculating an overall score (0–10). Aggregator: Summarizes results for quick comparison. Google Sheets Writer: Appends results to your review log. Slack Notification: Posts a concise summary (e.g., number of issues and average score) to your team’s channel. How to set up Connect Google Sheets and Slack credentials in n8n. Replace placeholders (<YOURSPREADSHEETID>, <YOURSHEETGIDORNAME>, <YOURSLACKCHANNEL_ID>). Adjust the AI review prompt or lint rules as needed. Activate the workflow — reviews will start automatically whenever new code is added to the sheet. Requirements Google Sheets and Slack integrations enabled A configured AI node (Gemini, OpenAI, or compatible) Proper permissions to write to your target Google Sheet How to customize Add more linting rules (naming conventions, spacing, forbidden APIs) Extend the AI prompt for project-specific guidelines Customize the Slack message formatting Export analytics to a dashboard (e.g., Notion or Data Studio) Why it’s valuable This workflow brings realistic, team-oriented AI-assisted code review to n8n — combining the speed of automated linting with the nuance of human-style feedback. It saves time, improves code quality, and keeps your team’s review history transparent and centralized.