Block 1 - Upload image2
- Type / Role
- n8n-nodes-base.httpRequest - httpRequest
- Config choices
- Version 4.2
This workflow is provided as-is. Please review and test before using in production.
MCP Tool — Replicate (Flux) Image Generator → WordPress/Twitter Generates images via Replicate Flux models and uploads to WordPress (and optionally Twitter/X). Built to act as an MCP module that ot...
n8n-nodes-base.httprequest, n8n-nodes-base.stickynote, n8n-nodes-base.manualtrigger, n8n-nodes-base.code, n8n-nodes-base.executeworkflowtrigger, n8n-nodes-base.merge, n8n-nodes-base.aggregate
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Jay Emp0.
Original n8n.io sourceMCP Tool — Replicate (Flux) Image Generator → WordPress/Twitter
Generates images via Replicate Flux models and uploads to WordPress (and optionally Twitter/X). Built to act as an MCP module that other agents/workflows call for on-demand image creation.
black-forest-labs/flux-schnell, black-forest-labs/flux-dev, black-forest-labs/flux-1.1-proLinks:
| Field | Type | Description |
|---|---|---|
| prompt | string | Text description for the image |
| slug | string | Filename slug for WP media |
| model | string | One of the configured Flux models |
Example:
{
"prompt":"Joker watching a Batman movie on his laptop",
"slug":"joker-watching-batman",
"model":"black-forest-labs/flux-dev"
}
{
"public_image_url": "https://your-wp.com/wp-content/uploads/2025/08/img-joker-watching-batman.webp",
"wordpress": {...},
"twitter": {...}
}
prompt, slug, modelPOST /v1/models/{model}/predictions (Prefer: wait)Operational pattern: I currently use this setup for my blog where i generate ~300 posts/month, each with 4 images (banner + 2 to 3 inline images) → ~1,000 images/month produced by this MCP.
💡 Hybrid Cost-Optimized Setup:
Leonardo per-image cost uses API Basic math: $9 / 3,500 credits = $0.0025714 per credit.
| Flux Model | Replicate | Leonardo API* |
|---|---|---|
flux-schnell |
$0.0030 (=$3/1,000) | $0.0180 (7 × $0.0025714) |
flux-dev |
$0.0250 | $0.0180 (7 × $0.0025714) |
flux-1.1-pro / Phoenix |
$0.0400 | $0.0257 (10 × $0.0025714) |
Replicate pricing: https://replicate.com/pricing
Leonardo pricing: https://leonardo.ai/pricing/
Leonardo API usage: https://docs.leonardo.ai/docs/commonly-used-api-values
Mix: 300 ×flux-dev on Leonardo,
700 ×flux-schnell on Replicate.
| Platform/Model | Images | Price per Image | Total |
|---|---|---|---|
Leonardo flux-dev |
300 | $0.0180 | $5.40 |
Replicate flux-schnell |
700 | $0.0030 | $2.10 |
| Total Monthly Spend | 1000 | — | $7.50 |
💵 If using Leonardo for both:
Savings: $10.50/month (≈58% lower) with the hybrid setup.
Code1 node.This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Generate images with Replicate and Flux |
|---|---|
| Complexity | intermediate |
| Nodes | 14 |
| Categories | Content Creation, Multimodal AI |
| Author | Jay Emp0 |
| Published | 09 Aug 2025 |
Use the JSON export at /data/workflows/7192/7192.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
MCP Tool — Replicate (Flux) Image Generator → WordPress/Twitter Generates images via Replicate Flux models and uploads to WordPress (and optionally Twitter/X). Built to act as an MCP module that ot...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Content Creation, Multimodal AI use case.