Generate & upload images with Leonardo AI, WordPress and Twitter
Prompt-to-Image Generator & WordPress Uploader (n8n Workflow)
This workflow generates high-quality AI images from text prompts using Leonardo AI, then automatically uploads the result to your WordPress media library and returns the final image URL.
It functions as a Modular Content Production (MCP) tool - ideal for AI agents or workflows that need to dynamically generate and store visual assets on-demand.
โ๏ธ Features
-
๐ง AI-Powered Generation
Uses Leonardo AI to create 1472x832px images from any text prompt, with enhanced contrast and style UUID preset. -
โ๏ธ WordPress Media Upload
Uploads the image as an attachment to your connected WordPress site via REST API. -
โ๏ธ Twitter Media Upload
Uploads the image to twitter so that you can post the image later on to X.com using the media_id -
๐ Returns Final URL
Outputs the publicly accessible image URL for immediate use in websites, blogs, or social media posts. -
๐ Workflow-Callable (MCP Compatible)
Can be executed standalone or triggered by another workflow. Acts as an image-generation microservice for larger automation pipelines.
๐ง Use Cases
For AI Agents (MCP)
- Plug this into multi-agent systems as the "image generation module"
- Generate blog thumbnails, product mockups, or illustrations
- Return a clean
image_urlfor content embedding or post-publishing
For Marketers / Bloggers
- Automate visual content creation for articles
- Scale image generation for SEO blogs or landing pages
- Supports media upload for twitter
For Developers / Creators
- Integrate with other n8n workflows
- Pass prompt and slug as inputs from any external trigger (e.g., webhook, Discord, Airtable, etc.)
๐ฅ Inputs
| Field | Type | Description |
|--------|--------|----------------------------------------|
| prompt | string | Text prompt for image generation |
| slug | string | Filename identifier (e.g. hero-image) |
Example:
{
"prompt": "A futuristic city skyline at night",
"slug": "futuristic-city"
}
๐ค Output
{
"public_image_url" : "https://your.wordpress.com/img-id",
"wordpress":{...obj},
"twitter":{...obj}
}
๐ Workflow Summary
- Receive Prompt & Slug Via manual trigger or parent workflow execution
- Generate Image POST to Leonardo AI's API with the prompt and config
- Wait & Poll Delays 1 minute, then fetches final image metadata
- Download Image GET request to retrieve generated image
- Upload to WordPress Uses WordPress REST API with proper headers
- Upload to Twitter Uses Twitter Media Upload API to get the media id incase you want to post the image to twitter
- Return Result Outputs a clean public_image_url JSON object along with wordpress and twitter media objects
๐ Requirements
- Leonardo AI account and API Key
- WordPress site with API credentials (media write permission)
- Twitter / x.com Oauth API (optional)
- n8n instance (self-hosted or cloud)
- This credential setup:
httpHeaderAuthfor Leonardo headershttpBearerAuthfor Leonardo bearer tokenwordpressApifor upload
๐งฉ Node Stack
Execute Workflow Trigger/Manual TriggerCode(Input Parser)HTTP Requestโ Leonardo image generationWaitโ 1 min delayHTTP Requestโ Poll generation resultHTTP Requestโ Download imageHTTP Requestโ Upload to WordPressCodeโ Return final image URL
๐ผ Example Prompt
{
"prompt": "Batman typing on a laptop",
"slug": "batman-typing-on-a-laptop"
}
Will return:
{
"public_image_url": "https://articles.emp0.com/wp-content/uploads/2025/07/img-batman-typing-on-a-laptop.jpg"
}
๐ง Integrate with AI Agents
This workflow is MCP-compliantโplug it into:
- Research-to-post pipelines
- Blog generators
- Carousel builders
- Email visual asset creators
Trigger it from any parent AI agent that needs to generate an image based on a given idea, post, or instruction.
n8n Workflow: Generate and Upload Images
This n8n workflow is designed to generate images using an external AI service, process them, and then prepare them for further use, potentially for platforms like WordPress or Twitter as suggested by the directory name. It focuses on the image generation and initial processing steps.
What it does
This workflow automates the following steps:
- Trigger: It can be executed manually or triggered by another workflow, making it a reusable component.
- Image Generation Request: It makes an HTTP request to an external API, presumably to an AI image generation service, to create an image.
- Wait for Processing: It introduces a pause, likely to allow the external AI service sufficient time to generate and process the image.
- Code Execution: It executes custom JavaScript code, which could be used for various purposes such as:
- Extracting specific data from the API response (e.g., image URLs, metadata).
- Transforming data formats.
- Implementing custom logic based on the image generation result.
- Merge Data: It merges the output from the code execution with the initial trigger data, potentially enriching the image generation request with additional context.
- Aggregate Data: It aggregates the processed image data, preparing it for subsequent actions in a streamlined format.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running instance of n8n.
- External AI Image Generation Service: Access to an API for an AI image generation service (e.g., Leonardo AI, Midjourney, DALL-E). The HTTP Request node will need to be configured with the appropriate endpoint, API key, and request body for this service.
- API Key/Credentials: Any necessary API keys or authentication tokens for the external AI image generation service.
Setup/Usage
- Import the Workflow:
- Copy the provided JSON code.
- In your n8n instance, go to "Workflows" and click "New".
- Click the three dots in the top right corner and select "Import from JSON".
- Paste the JSON code and click "Import".
- Configure the HTTP Request Node (Node 19):
- Edit the "HTTP Request" node.
- Set the
URLto your AI image generation service's API endpoint. - Set the
Method(e.g., POST). - Configure
Headers(e.g.,Authorizationwith your API key,Content-Type: application/json). - Define the
Bodywith the prompt and any other parameters required by your AI image generation service.
- Configure the Wait Node (Node 514):
- Adjust the
Time to Waitvalue based on how long your AI image generation service typically takes to process requests.
- Adjust the
- Configure the Code Node (Node 834):
- Edit the "Code" node.
- Modify the JavaScript code to parse the response from the AI image generation service and extract the relevant image data (e.g., image URL, image ID). This is where you'd typically handle the specific structure of the AI service's response.
- Save and Activate:
- Save the workflow.
- Activate the workflow to enable it.
- Execute:
- You can manually trigger the workflow by clicking "Execute Workflow" on the "Manual Trigger" node.
- If integrated with another workflow, it will be triggered automatically.
This workflow provides a robust foundation for integrating AI image generation into your automated processes.
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
๐ 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.