n8n execution test-1

You think you know how n8n executes a workflow?

Alright prove it.

Look at this workflow and comment which node executes first and what happens after that.

Don’t run it.

Just look at it and make your call.

Hints: The workflow starts from the Manual Trigger and then splits into two branches, and both branches eventually lead back toward the same If node. The top branch has DATA → Split Out, while the bottom branch has DATA1 → Network Call Wait.

Now think about the execution:

A. Top → Bottom: Start with the top branch, execute it left → right, finish it, then move to the bottom branch.

B. Bottom → Top: Start with the bottom branch, execute it left → right, finish it, then move to the top branch.

C. Switch between branches: Start with the top branch, execute until the If, switch to the bottom branch, then continue from there.

D. Both branches at the same time: n8n starts executing both branches in parallel.

Which one do you think it is?

I've been experimenting with a Telegram + n8n workflow for generating 3D anatomy visuals from a simple anatomy term.

The use case is straightforward: for medical study, anatomy education, or creating educational medical content, you may need visualizations of many different organs while keeping the images consistent in style.

Instead of manually writing a new prompt for every organ, the workflow separates the anatomical subject from the visual instructions.

For example, the user only sends:

kidney

The workflow then:

• validates that the input contains a single anatomical subject
• extracts the actual anatomy term
• combines it with a predefined Master Prompt
• sends that context to GPT-4.1
• generates a structured image-generation prompt
• sends the resulting prompt to Nano Banana 2
• waits for the generation to complete
• returns the final image through Telegram

The important part is the Master Prompt.

It contains the rules that should remain stable across generations:

• 3D medical rendering style
• anatomical accuracy requirements
• background and overall tone
• lighting
• camera position and composition
• rendering quality
• visual constraints and negative instructions

The anatomy itself is the variable.

So the workflow can receive:

kidney heart liver brain

without having to manually redesign the entire prompt for each one.

The architecture is essentially:

Telegram → validation → anatomy extraction → Master Prompt + subject → GPT-4.1 → Nano Banana 2 → Telegram

This also solves an issue I noticed when testing direct image generation.

If the raw anatomy term is sent straight to an image model, each generation can drift in lighting, composition, background, rendering style, and sometimes anatomical details.

Adding a dedicated prompt-construction step gives the image model a much more controlled specification before generation.

So the workflow isn't really about generating one anatomy image.

It's about creating a repeatable generation system where the subject can change while the visual specification remains controlled.

Built with:

• n8n
• Telegram Bot
• OpenAI GPT-4.1
• Nano Banana 2

The same approach could be useful for building consistent anatomy study materials, medical educational content, or a larger library of 3D anatomical visualizations without manually prompting every image.

Try it yourself:
https://github.com/cuebicai/n8n-workflows/tree/main/3D-anatomy-studio

I wanted to see how far I could push AI image generation with automation.

The idea is simple:

>Send an organ name like kidney or heart on Telegram and get back a realistic 3D anatomy visualization.

No manual prompt writing. The workflow handles the rest.

The Problem

AI image generation can be inconsistent between subjects.

A kidney might have one background and lighting style, while a heart gets a completely different look.

I wanted the anatomy to change while the visual identity stays consistent.

The Workflow

The automation:

• Validates that the user entered one anatomical subject
• Extracts the actual anatomy part
• Applies a structured Master Prompt
• Generates the final image prompt
• Sends it to Nano Banana 2
• Waits for generation
• Sends the finished image back to Telegram

The Master Prompt controls the fixed visual system:

• 3D medical rendering
• Background and tone
• Lighting
• Camera and composition
• Anatomical accuracy
• Rendering quality
• Negative constraints

So:

kidney → same visual style
heart  → same visual style
liver  → same visual style
brain  → same visual style

Only the subject changes.

Stack

• n8n
• Telegram
• OpenAI GPT-4.1
• Nano Banana 2

The interesting part for me is separating what to generate from how it should look. It makes the workflow reusable instead of relying on a completely new prompt every time.

Just send the anatomy part. The workflow handles the rest.

For the past few weeks, I've been pretty quiet not because I stopped building actually it's been the complete opposite.

I've been working on what I believe is one of the biggest updates to my project so far.

When I first started building it my goal was simple.

Make self-hosting n8n ridiculously easy.

No server setup.

No manual configuration.

No spending hours installing Docker, configuring SSL, setting up reverse proxies, or troubleshooting deployments.

Just launch your own instance and start building automations.

Over the past few months I've helped quite a few people get their own n8n instances running.

Seeing people actually use something I built has been one of the most rewarding parts of this journey.

But after watching more and more people deploy their instances, I kept coming back to one question.

What happens after deployment?

Because that's where the real challenge begins.

Once your workflows are running in production, deployment is no longer the hard part.

Keeping everything running reliably is.

You start asking questions like:

• Is my n8n instance still running?
• Are my workers healthy?
• Is PostgreSQL responding?
• Is Redis connected?
• Is my domain still reachable?
• Is my SSL certificate about to expire?
• Is CPU or RAM usage getting too high?
• Is disk space running out?
• Has bandwidth suddenly spiked?
• If something breaks, will I know before my users do?

If you've self-hosted n8n, you've probably been there.

You open Grafana.

Then Prometheus.

Then your VPS dashboard.

Then your logs.

Then Uptime Kuma.

Then SSH into the server.

You're constantly jumping between tools just to answer one simple question:

"Is everything okay?"

That made me realize something.

Deploying n8n is only the first step.

Running it in production is a completely different problem.

So for the past few weeks that's exactly what I've been building.

An integrated monitoring system that continuously checks every deployed instance.

Behind the scenes metrics are collected every few minutes, evaluated against monitoring rules, and turned into information that's actually useful instead of just showing raw metrics.

Right now it includes:

• 📈 Live CPU, RAM, storage, and bandwidth monitoring
• 📊 Historical performance charts
• 💚 Health checks for n8n, PostgreSQL, Redis, workers, and other services
• 🌐 Domain availability and SSL monitoring
• ⏱️ A 24-hour health timeline
• 🚨 Automatic incident detection
• 📧 Severity-based email notifications

Building this completely changed how I think about self-hosting.

Getting an application online is relatively easy.

Keeping it healthy every day is the part that takes the real work.

I'm genuinely curious how everyone here handles this today.

Do you use Prometheus and Grafana?

Uptime Kuma?

Netdata?

Custom scripts?

Or have you built your own monitoring setup around n8n?

I'd love to hear what your stack looks like and what has worked well for you.

I built an AI-powered 360° ghost mannequin t-shirt video generator using n8n.

Now whenever I send the front and back images of a t-shirt to my Telegram bot and select the body type, the automation automatically:

• downloads both t-shirt reference images
• analyzes the garment using AI vision
• identifies colors, graphics, typography, construction, and proportions
• builds a structured master specification for the t-shirt
• generates a specialized AI video prompt
• uses the front image as the authoritative front reference
• uses the back image as the authoritative back reference
• reconstructs realistic side and intermediate views
• generates a photorealistic 360° ghost mannequin rotation video
• monitors the video generation process automatically
• sends the finished video back to Telegram

The entire video generation process runs automatically from just two t-shirt images and a body type selection.

Built with:

• n8n
• Telegram Bot
• OpenAI GPT-4.1
• Seedance 2 mini via Kie AI
• ImgBB

The workflow was designed to reduce the work required to turn basic t-shirt product images into 360° e-commerce videos.

Instead of manually creating a 3D model, setting up a turntable animation, or writing a new video prompt for every t-shirt, the workflow first analyzes the garment and builds a structured master specification.

A second AI model then compiles that specification into a production-ready video prompt before generating the final 360° rotation.

This improves:

• front and back design preservation
• typography and artwork consistency
• garment proportion accuracy
• side-view reconstruction
• rotation consistency
• overall video realism

while reducing manual prompt writing, 3D modeling, video editing, and repetitive work.

Just send the front and back images of a t-shirt, select the body type, and receive a finished 360° ghost mannequin product video.

Try it yourself: https://github.com/cuebicai/n8n-workflows/tree/main/360-3d-t-shirt-mockup-ai-video-generator

Creating professional 360° apparel videos usually requires expensive 3D software, manual modeling, product photography, or complex CGI pipelines.

I wanted to see how far I could push AI.

The goal was simple:

>Upload the front and back images of a garment, choose the body type, and automatically generate a realistic 360° rotating ghost mannequin product video that is ready for e-commerce.

No manual prompt writing.

No video editing.

No 3D modeling.

Everything happens automatically.

The Problem

Creating high-quality apparel rotation videos is surprisingly difficult.

A typical workflow often involves:

• Photographing multiple angles of the garment
• Building or scanning a 3D model
• Cleaning the mesh
• Creating realistic cloth simulation
• Matching front and back artwork
• Rendering a turntable animation
• Editing and exporting the final video

Even with AI, most models struggle to:

• Preserve the front and back design accurately
• Generate believable side views
• Maintain garment proportions
• Keep artwork aligned during rotation
• Avoid flickering or temporal inconsistencies

For e-commerce, even small changes in print placement or garment shape can make the result unusable.

The Solution

I built an automated AI workflow using n8n that generates a photorealistic 360° ghost mannequin apparel video from only two reference images.

The user simply uploads:

• Front garment image
• Back garment image
• Body shape (Men's or Women's fit)

Everything else is handled automatically.

How the Workflow Works

The workflow consists of two AI pipelines running in parallel.

Pipeline 1 — Image Processing

The uploaded garment images are first analyzed using AI Vision.

The workflow automatically:

• Uploads and stores both reference images
• Extracts image metadata
• Detects garment characteristics
• Identifies the apparel type
• Understands colors, graphics, typography, construction, and proportions

This structured analysis becomes the foundation for the next stage.

Pipeline 2 — Video Prompt Generation

Instead of manually writing prompts, the workflow generates a structured master specification describing every aspect of the garment and scene.

The specification includes:

• Reference image interpretation
• Garment reconstruction rules
• Camera behavior
• Composition
• Lighting
• Background consistency
• Animation
• Rendering quality
• Preservation constraints
• Negative constraints

A second AI model then compiles this structured specification into a production-ready prompt optimized specifically for AI video generation.

This approach produces much more consistent results than writing prompts manually.

Video Generation

Once the prompt is generated, the workflow automatically prepares the API request and submits it for video generation.

The AI reconstructs one physically consistent 3D garment by using:

• The first image as the authoritative front
• The second image as the authoritative back

It then generates realistic intermediate views including:

• Left side
• Right side
• Shoulder profile
• Side seams
• Garment depth
• Three-quarter angles

Finally, it creates a smooth 360° rotating ghost mannequin video while preserving the garment's structure and artwork.

Automation Features

The workflow also handles the entire generation lifecycle automatically.

It:

• Uploads reference images
• Builds the master specification
• Generates the optimized AI prompt
• Starts video generation
• Polls the generation status
• Retrieves the completed video
• Sends the finished result directly to Telegram

The user never needs to monitor the generation manually.

Tech Stack

• n8n
• Telegram Bot
• OpenAI GPT-4.1
• Seedance 2 mini (via Kie AI)
• ImgBB
• Structured AI Prompt Compiler

Workflow Architecture

Telegram Form
        │
        ▼
Upload Front & Back Images
        │
        ▼
Extract Image Metadata
        │
        ▼
AI Garment Analysis
        │
        ├────────────────────────────┐
        │                            │
        ▼                            ▼
Image Generation              Master Specification
                                      │
                                      ▼
                           AI Prompt Compiler
                                      │
                                      ▼
                       Seedance 2 mini Video Generation
                                      │
                                      ▼
                            Status Monitoring
                                      │
                                      ▼
                           Telegram Video Delivery

Why I Built It

I wanted a workflow that could produce consistent apparel product videos without relying on handcrafted prompts for every garment.

By separating the process into structured analysis, specification generation, prompt compilation, and video rendering, the workflow becomes reusable for different garments while maintaining consistent output quality.

It also makes experimenting with different AI video models much easier, since only the final prompt compiler needs to change.

Current Result

The workflow can now automatically generate:

• AI garment analysis
• Structured master specification
• Production-ready AI video prompt
• Photorealistic 360° ghost mannequin rotation
• Commercial-style product presentation
• Automatic Telegram delivery

The entire process runs end-to-end with minimal user input just two reference images and a body type selection.

New Feature: One-Click n8n Version Updates & Rollbacks

One of the most requested improvements for self-hosted n8n is making upgrades less painful.

If you've ever updated n8n manually, you know the process usually involves SSH access, Docker commands, restarting containers, and hoping everything works as expected. And if a new release introduces a compatibility issue, rolling back can be just as time-consuming.

To make that easier, I've added one-click n8n version updates and rollbacks to Cuebic AI.

What you can do

• Upgrade to the latest supported n8n version with a single click
• Roll back to a previous version whenever needed
• Switch n8n versions without redeploying your instance
• Keep your workflows, credentials, and configuration intact throughout the process

The goal is simple: updating your self-hosted n8n instance should be as easy as deploying it.

Why this matters

Updating regularly gives you access to:

• New n8n features
• Performance improvements
• Bug fixes
• Security updates

And when an update doesn't play nicely with an existing workflow, having a rollback option makes it much safer to upgrade without worrying about downtime.

Feedback welcome

If you self-host n8n, I'd love to hear how you're currently handling version updates.

• What's your current update process?
• Have you ever had to roll back after an upgrade?
• Are there any safeguards or version management features you'd like to see?

Always interested in hearing feedback from the n8n community.

I've been experimenting with a workflow that automatically turns a t-shirt design into a production-ready apparel mockup.

Instead of manually opening a mockup generator, positioning the artwork, adjusting placement, and exporting product images, I send a design image to a Telegram bot and the workflow handles the rest automatically.

The workflow:

• analyzes the artwork using AI vision
• extracts typography, graphics, colors, layout, and design characteristics
• generates a specialized apparel mockup prompt
• creates a premium 3D t-shirt mockup
• preserves the original artwork with high fidelity
• applies the design as a realistic garment print
• monitors the generation process automatically
• sends the finished mockup back to Telegram

Built with:

• n8n
• Telegram Bot
• OpenAI 4.1
• Nano Banana 2
• ImgBB

One thing I noticed while testing:

Generating apparel mockups directly from a design image often produces distorted artwork, inaccurate colors, or inconsistent print placement.

The workflow performs much better when it first analyzes the uploaded design and generates a structured apparel-rendering prompt before creating the final mockup.

This improves:

• artwork fidelity
• typography preservation
• color accuracy
• print placement quality
• garment realism
• overall mockup consistency

For those selling apparel online, designing merch, or running print-on-demand stores:

Do you think AI-generated mockups could eventually replace graphic designers and traditional editing software for creating apparel product images?

Try it yourself:
https://github.com/cuebicai/n8n-workflows/tree/main/3D-t-shirt-mockup-generator

I built an AI-powered 3D apparel mockup generator using n8n.

Now whenever I send a t-shirt design image to my Telegram bot, the automation automatically:

• downloads the design image
• analyzes the artwork using AI vision
• extracts typography, graphics, colors, layout, and design characteristics
• generates a specialized apparel mockup prompt
• creates a premium 3D t-shirt mockup
• preserves the original artwork with high fidelity
• applies the design as a realistic garment print
• monitors the generation process automatically
• sends the finished mockup back to Telegram

The entire mockup creation process runs automatically from a single design image.

Built with:

• n8n
• Telegram Bot
• OpenAI 4.1
• Nano Banana 2
• ImgBB

The workflow was designed to eliminate manual mockup creation and reduce the time required to turn a design into a professional product image.

Instead of manually positioning artwork inside a mockup generator, it first analyzes the uploaded design and generates a specialized apparel rendering prompt before creating the final mockup.

This improves:

• artwork fidelity
• typography preservation
• color accuracy
• print placement quality
• garment realism
• overall mockup consistency

while reducing manual editing and repetitive design work.

Just send a t-shirt design and receive a finished e-commerce-ready apparel mockup.

Try it yourself:
https://github.com/cuebicai/n8n-workflows/tree/main/3D-t-shirt-mockup-generator

Creating apparel mockups sounds simple, but getting professional results usually requires multiple tools, manual editing, and a lot of trial and error.

I wanted a way to turn a design into a realistic e-commerce-ready mockup without opening Photoshop or spending time manually creating product images.

The Problem

Most apparel mockups are either expensive, time-consuming to create, or require design experience.

A typical workflow often looks like:

• Create or receive a t-shirt design
• Open a mockup generator
• Search for a suitable mockup
• Position and scale the artwork
• Adjust placement and sizing
• Export multiple versions
• Repeat for every new design

The process becomes even more repetitive when testing multiple designs or preparing products for a store.

I wanted a workflow that could take a single design image and automatically generate a professional apparel mockup.

The Solution

I built an AI-powered 3D T-Shirt Mockup Generator using Telegram and n8n.

Now I simply send a t-shirt design image to a Telegram bot.

The workflow automatically:

• Uses AI vision to analyze the artwork
• Extracts typography, graphics, colors, layout, and design characteristics
• Generates a specialized apparel mockup prompt
• Creates a premium 3D t-shirt mockup
• Preserves the artwork with high fidelity
• Applies the design as a realistic garment print
• Monitors generation status automatically
• Sends the finished mockup back to Telegram

Everything runs automatically with no manual prompt writing required.

Tech Stack Used

• n8n
• Telegram Bot
• OpenAI 4.1
• Nano Banana 2
• ImgBB

Workflow Architecture

Telegram → Image Upload → Artwork Analysis → AI Mockup Prompt Generation → 3D Mockup Generation → Status Monitoring → Telegram Delivery

How The Mockups Are Generated

One challenge I found was preserving the original design while still generating a realistic apparel mockup.

The workflow uses AI vision to understand the uploaded artwork and generate a structured prompt specifically for apparel rendering.

The generated mockups focus on:

• Artwork fidelity
• Typography preservation
• Accurate colors
• Realistic print integration
• Natural fabric folds
• Garment texture
• Professional studio lighting
• Commercial product presentation

The goal is not to redesign the artwork but to present it as a realistic product.

Mockup Style

The workflow generates premium ghost-mannequin style apparel mockups.

This creates the appearance of a garment being worn while keeping the body invisible.

The result includes:

• Natural garment volume
• Realistic chest and shoulder contours
• Fabric tension and draping
• Professional studio presentation
• Seamless paper backdrop
• Clean e-commerce aesthetic

This helps the final image feel much closer to a real product photograph than a flat design preview.

Why I Built It

I wanted a faster way to visualize designs before publishing them to a store or sharing them with customers.

Instead of manually creating mockups, I can now send a design directly from my phone and receive a professional mockup automatically.

Current Result

The workflow now functions like a small AI apparel studio.

I can upload a single t-shirt design and automatically receive:

• A design analysis
• A specialized mockup prompt
• A premium 3D apparel mockup
• A production-ready product image

I built an AI-powered UGC video ad creator using n8n.

Now whenever I send a product photo to my Telegram bot, the automation automatically:

• downloads the product image
• analyzes the product using AI vision
• extracts product details and visual characteristics
• generates a professional marketing image prompt
• creates an upgraded advertising-ready product image
• generates a detailed UGC video production script
• creates a UGC-style product video using Veo 3
• monitors the video generation process automatically
• sends the finished video back to Telegram

The entire creative process runs automatically from a single product image.

Built with:

• n8n
• Telegram Bot
• OpenAI
• Nano Banana
• Veo 3
• Google Sheets

The workflow was designed to reduce manual prompt engineering and improve first-generation video quality.

Instead of generating videos directly from the original product image, it first creates an optimized marketing image and then uses that image to generate the final video ad.

This improves:

• product presentation
• scene consistency
• lighting quality
• overall video generation results

while reducing the number of failed generations and wasted credits.

Just send a product photo and receive a finished AI-generated UGC video advertisement.

Try it yourself:
https://github.com/cuebicai/n8n-workflows/tree/main/ugc-video-generator

How i built an AI-powered UGC video ad creator using n8n.

Now whenever I send a product photo to my Telegram bot, the automation automatically:

• downloads the product image
• analyzes the product using AI vision
• extracts product details and visual characteristics
• generates a professional marketing image prompt
• creates an upgraded advertising-ready product image
• generates a detailed UGC video production script
• creates a UGC-style product video using Veo 3
• monitors the video generation process automatically
• sends the finished video back to Telegram

The entire creative process runs automatically from a single product image.

Built with:

• n8n
• Telegram Bot
• OpenAI
• Nano Banana
• Veo 3
• Google Sheets

The workflow was designed to reduce manual prompt engineering and improve first-generation video quality.

Instead of generating videos directly from the original product image, it first creates an optimized marketing image and then uses that image to generate the final video ad.

This improves:

• product presentation
• scene consistency
• lighting quality
• overall video generation results

while reducing the number of failed generations and wasted credits.

Just send a product photo and receive a finished AI-generated UGC video advertisement.

Try it yourself:
https://github.com/cuebicai/n8n-workflows/tree/main/ugc-video-generator

To create UGC-style product ads without spending hours writing prompts, generating assets, and manually stitching everything together.

Most AI video tools can generate videos, but getting a good result usually requires multiple steps and a lot of trial and error.

The Problem

Creating AI product ads is still more manual than most people think.

A typical workflow looks like:

• Find or create a product image
• Analyze the product
• Write a detailed image prompt
• Generate a better marketing image
• Write a video prompt
• Generate the video
• Retry multiple times if the result isn't good

The process becomes even more expensive when every failed generation costs credits.

I wanted something that could take a single product photo and handle the entire creative process automatically.

The Solution

I built an AI UGC video ad generator using Telegram and n8n.

Now I simply send a product image to a Telegram bot.

The workflow automatically:

• Downloads the product image
• Uses AI vision to analyze the product
• Extracts product details and visual characteristics
• Generates a professional marketing image prompt
• Creates an upgraded product image
• Generates a detailed video production script
• Creates a UGC-style video using Veo 3
• Monitors generation status automatically
• Sends the finished video back to Telegram

Everything runs automatically with no manual prompt engineering required.

Tech Stack Used

• n8n
• Telegram Bot
• OpenAI
• Nano Banana
• Veo 3
• Google Sheets

Workflow Architecture

Telegram → Product Analysis → AI Image Prompt → Image Generation → AI Video Script → Veo 3 Video Generation → Telegram Delivery

Why I Added The Image Generation Step

I found that generating a video directly from the original product image often produced inconsistent results.

Instead, the workflow first creates a higher-quality marketing image that is optimized for advertising.

This improved:

• Product presentation
• Scene consistency
• Lighting quality
• Video generation results

while reducing the number of retries needed.

Cost Optimization

Video generation is usually the most expensive step.

By automatically creating a stronger source image and a detailed structured video prompt first, the workflow produces better results on the first attempt and reduces wasted generations.

That helps keep overall generation costs lower.

Current Result

The workflow now works like a small AI creative studio.

I can send a product image directly from my phone and automatically receive:

• An analyzed product profile
• A marketing-ready image
• A generated UGC script
• A finished AI video advertisement

Still improving the workflow, but it's already producing some surprisingly good product ads with very little manual work.

Nobody warns you about what happens after the install.

You follow the docs, everything spins up, first few workflows run clean. You think you've figured it out.

Then real usage hits.

Not "test a webhook" usage. Actual clients, actual data, actual load and suddenly your instance is doing things nobody documented. Freezing mid-execution. Dropping webhooks. Failing silently while you're asleep. You wake up to a client message asking why their automation hasn't run in six hours.

That's when self-hosting gets humbling.

I went through this slowly and painfully over the past year. Every issue below cost me real time. Sharing it so you don't have to learn it the same way.

1. CPU hitting 100% and the whole instance freezing

What happened: A workflow with a loop making API calls would quietly push CPU to 100% and lock everything up. Not just that workflow — everything. The instance would just sit there, frozen, accepting no new executions.

What fixed it: Reduced concurrency limits, broke the workflow into smaller sub-workflows, and replaced tight loops with proper batching. The instance went from freezing regularly to running clean.

2. Loops quietly destroying your system

What happened: Even with wait nodes added, loops were stacking executions faster than they were finishing. The queue grew until the system buckled.

What fixed it: Stopped relying on loops for anything continuous. Switched entirely to scheduled triggers and batch processing. Much more predictable, much easier to debug.

3. One workflow silently killing every other workflow

What happened: A single long-running workflow would hold the main process hostage. Webhooks queued up and never fired. Other automations sat waiting. From the outside it looked like everything was working — nothing was.

What fixed it: Switched to queue mode with dedicated workers. Execution separated from the main instance entirely. This was probably the single most impactful change I made.

4. Memory and disk slowly filling up with nobody noticing

What happened: n8n stores execution data by default and never cleans it up unless you tell it to. Weeks in, RAM and disk are quietly maxed out and you have no idea why.

What fixed it: Enabled pruning:

EXECUTIONS_DATA_PRUNE=true
EXECUTIONS_DATA_MAX_AGE=72

Should honestly be the default. Set this before you need it, not after.

5. Container dying instantly on large payloads

What happened: A workflow processing a large JSON response would spike memory and kill the container mid-execution. No graceful failure. Just gone.

What fixed it: Started limiting payload sizes at the workflow level and splitting heavy processing into smaller chained steps. Stopped passing large data directly between nodes.

6. Workflows failing with zero indication anything was wrong

What happened: A token expired. An API quietly changed its response format. The workflow stopped producing results — no error, no log, nothing. The only way I found out was a client asking where their data was.

What fixed it: Built proper error workflows that fire on any failure and send alerts via Slack and email. Added basic validation at key nodes to confirm data actually looks right before continuing. You cannot trust silence.

7. Having no idea when the server went down

What happened: The instance went down. I didn't know. Clients noticed before I did. That's a bad position to be in.

What fixed it: Set up an external uptime monitor pinging a health endpoint every minute. Now I get an alert before anyone else does.

8. Webhooks breaking after every restart

What happened: Container restarts changed the webhook URLs. Every integration connected to those webhooks silently broke and had to be manually reconnected.

What fixed it: Set N8N_WEBHOOK_URL to a fixed domain. Webhooks have been stable ever since.

9. One mistake away from losing every credential permanently

What happened: Realised that if the encryption key was ever lost — server failure, bad migration, accidental deletion — every single stored credential would be unrecoverable. Not broken. Gone.

What fixed it: Backed up N8N_ENCRYPTION_KEY to secure external storage immediately. If you haven't done this yet, stop reading and do it now.

10. One bad workflow taking down every client's automation

What happened: Running multiple clients on a shared instance meant one runaway workflow could degrade or crash everything else. No isolation, no containment.

What fixed it: Either separate instances per client, or strict execution limits combined with queue mode. Shared instances without isolation are a liability at scale.

11. Version updates silently breaking production

What happened: Trusted the latest tag. An update changed something subtle. Workflows that ran fine for months started misbehaving with no clear error.

What fixed it: Pinned the n8n version. Now updates only happen after testing in a separate environment first. Boring but it works.

The honest takeaway

Small scale, n8n self-hosted is genuinely great. Cheap, flexible, powerful.

But production usage is a different environment entirely. The problems above aren't rare edge cases they're what happens when real workloads hit an instance that isn't configured for them.

If you're running n8n seriously you need execution control, active monitoring, proper cleanup, and isolation. Not eventually. From the start.

Happy to go deeper on any of these if you're dealing with something similar.

I built an AI-powered product ad generator using n8n where users upload a product image, choose a visual theme, and AI automatically creates cinematic marketing creatives in seconds.

Creating professional product ads usually requires design skills, editing software, and a lot of manual work.

For every new campaign, promotion, or product launch, businesses often need to:

• create ad concepts

• design layouts

• add promotional text

• match lighting and colors

• create multiple variations

• export creatives for different platforms

Doing this repeatedly becomes slow and expensive.

So I built a workflow that automates the entire process.

Now users simply upload a product image, enter a marketing tag line such as:

• 50% DISCOUNT

• LIMITED OFFER

• NEW COLLECTION

Then select one or more creative themes.

The workflow automatically:

• uploads the product image and generates a public URL

• loads theme prompts from Google Sheets

• dynamically builds AI prompts

• generates cinematic marketing creatives with AI

• creates multiple ad variations automatically

• monitors generation status

• delivers the final creatives directly to Telegram

The result is a complete AI-powered creative studio that can turn a single product photo into multiple professional marketing ads within seconds.

Built with:

• n8n

• Nano Banana 2

• IMGBB API

• Google Sheets

• Telegram Bot

No Photoshop. No manual design work. Just upload a product image and let AI create the ads.

I wanted a faster way to create high-quality product marketing creatives without manually designing ads every time.

Most small businesses and creators don’t have the time or design skills to create professional product ads for every promotion, campaign, or product launch.

So I built an AI-powered product ad generator using n8n where users can upload a product image, choose a visual theme, and AI automatically generates cinematic marketing creatives in seconds.

The Problem

Creating product ads manually is slow and repetitive.

Usually the process looks something like this:

• Upload product photos
• Remove backgrounds
• Find inspiration
• Design layouts
• Add promotional text
• Match colors and lighting
• Export multiple formats

Doing this repeatedly for every campaign becomes very time-consuming.

Especially for:

• ecommerce stores
• small businesses
• dropshippers
• social media marketers
• content creators

I wanted something more automated and scalable.

The Solution

Now users simply open a form, upload a product image, enter a tag line like:

• 59% DISCOUNT
• LIMITED OFFER
• NEW COLLECTION

Then select one or multiple creative themes such as:

• Urban Streetwear
• Sneaker Collection Wall
• Photography Studio
• Hidden Garden
• Modern Greenhouse

The workflow automatically:

• Uploads the product image to IMGBB
• Converts the image into a public URL
• Loads the selected theme prompts from Google Sheets
• Dynamically builds AI prompts
• Sends everything to Nano Banana 2
• Generates cinematic marketing creatives
• Monitors generation status automatically
• Fetches the final generated image
• Sends the completed ad creative directly to Telegram

Everything happens automatically in a few seconds.

Tech Stack Used

• n8n
• Nano Banana 2
• IMGBB API
• Google Sheets
• Telegram Bot

Workflow Architecture

Form Submission → Image Upload → Theme Processing → Prompt Generation → AI Image Generation → Status Polling → Telegram Delivery

How the Workflow Works

The workflow starts with an n8n form where users upload a product image and choose creative settings.

The uploaded image is first sent to IMGBB because the AI model requires a public image URL instead of raw binary files.

Selected themes are then split into separate items so the workflow can generate multiple ad variations automatically.

Theme prompts are stored inside Google Sheets which acts like a small prompt database. This makes the workflow easy to scale because new themes can be added without modifying the automation itself.

The workflow then dynamically builds the final AI prompt using:

• product image URL
• selected theme
• tag line
• aspect ratio
• output quality

That payload is sent to Nano Banana 2 which generates the final cinematic marketing creative.

Since image generation is asynchronous, the workflow waits a few seconds and continuously checks the generation status until the final image becomes available.

Once generation succeeds, the completed creative is automatically delivered to Telegram.

Example Features

The workflow currently supports:

• Multiple theme generation
• Dynamic prompt building
• Automated AI polling
• Telegram delivery
• Different aspect ratios
• Multiple output qualities
• Batch creative generation

Cost Per Image

Current generation cost is roughly:

• ~$0.04 per 1K image

Which is surprisingly affordable considering the output quality.

Why I Used AI Instead of Traditional Design Automation

Traditional automation still requires predefined templates and fixed layouts.

But product marketing creatives vary heavily depending on:

• product category
• lighting
• composition
• environment
• campaign style
• promotional text

Instead of building hundreds of static templates, I used AI to dynamically generate unique creatives based on prompts and themes.

This made the system much more flexible and scalable.

Current Result

The workflow now works like a small AI-powered creative studio.

Users can upload a single product image and automatically generate multiple professional marketing creatives optimized for ads and social media.

Still improving the system, but the current results are already extremely impressive for the generation cost and speed.

I built an AI-powered ecommerce product photo workflow using n8n.

Now whenever I send a raw product image to my Telegram bot, the automation automatically:

• removes the messy background
• cleans edge artifacts
• aligns and centers the product
• resizes the image for ecommerce use
• enhances lighting and presentation using AI
• generates a clean studio-style product photo
• preserves the original product shape, colors, labels, and branding
• sends the final ecommerce-ready image back to Telegram

The entire process takes just a few seconds.

Built with:

• n8n
• rembg
• Sharp
• OpenAI gpt-image-1
• Docker
• Telegram Bot

Most of the heavy processing happens locally using self-hosted tools.

The AI is only used for the final enhancement layer to keep outputs consistent and reduce hallucinations.

A lot of small ecommerce sellers still take product photos using their phones.

The biggest issues are usually:

• messy backgrounds
• bad lighting
• inconsistent image sizes
• poor product alignment
• shadows and edge artifacts
• time spent manually editing images
• expensive design tools or Photoshop workflows

For marketplaces and ecommerce stores, consistency matters a lot.

Most sellers do not have:

• a professional camera setup
• a product photography studio
• editing skills
• time to manually process every image

So I wanted to build a fully automated workflow where someone could:

1. Click a raw product photo
2. Send it to Telegram
3. Automatically receive a clean ecommerce-ready product image

The goal was to build a lightweight AI-powered product photo studio using:

• n8n
• self-hosted tools
• OpenAI image generation
• Docker containers
• custom image processing APIs

The workflow needed to:

• remove backgrounds
• clean edge artifacts
• resize and align products
• create consistent ecommerce-style outputs
• preserve the original product exactly
• avoid AI hallucinations
• stay cheap to run

Final Workflow

Telegram Image Input
↓
Download Telegram Image
↓
Primary Background Removal
↓
Product Alignment & Resize
↓
Edge Cleanup & Artifact Removal
↓
AI Product Enhancement
↓
Convert AI Output To Image
↓
Send Enhanced Product Image

Tech Stack

• n8n: Used as the orchestration layer for the entire pipeline.
• rembg: I used rembg running inside Docker for AI background removal.

Why rembg?

• open source
• lightweight
• fast
• self-hosted
• very cheap to run
• works well for product extraction

rembg Model Used: birefnet-general

This model produced cleaner product cutouts and better edge quality compared to the default models.

rembg API Endpoint: http://rembg:7000/api/remove

• Sharp + Express API: After removing the background, the product image still needed:

Why Sharp?

Sharp is extremely fast and lightweight for image processing.

It handles:

• resizing
• trimming
• transparent padding
• sharpness enhancement
• image cleanup
• format conversion

much faster than ImageMagick-based solutions.

The Sharp pipeline performs:

1. Trim dirty transparent edges
2. Resize the product
3. Center the composition
4. Add transparent spacing
5. Clean artifacts
6. Sharpen the final image

This creates a much cleaner input before sending anything to OpenAI.

That is important because cleaner AI inputs produce more stable outputs.

Sharp API Endpoint: http://sharp-api:3000/resize

Why I Split Processing Into Multiple Stages

I intentionally separated: Deterministic Processing

Handled locally using:

• rembg
• Sharp

These steps are predictable and controllable.

• AI Enhancement

Handled by OpenAI.

Used only for:

• realism
• lighting
• ecommerce presentation
• studio-style enhancement

This architecture reduced:

• hallucinations
• redesigns
• inconsistent outputs
• API costs

while improving reliability.

OpenAI Image Enhancement

Model Used: gpt-image-1

The OpenAI stage was NOT used for product generation.

Instead, it was used only to:

• improve lighting
• improve realism
• improve presentation
• create ecommerce-style composition
• generate clean studio backgrounds

while preserving the original product.

The Biggest Challenge

At first, the AI kept:

• redesigning products
• changing labels
• hallucinating objects
• altering shapes
• creating random luxury scenes

So I had to create a highly controlled prompting strategy.

Prompt Engineering Strategy

The final prompts strictly instructed the model to:

• preserve branding
• preserve shape
• preserve colors
• preserve labels
• preserve reflections
• preserve packaging
• remove unwanted artifacts
• avoid extra objects
• avoid human figures
• avoid props
• avoid creative reinterpretations

The goal was consistency instead of creativity.

Background Standardization

Instead of allowing random AI-generated scenes, I standardized the outputs using:

• soft light gray studio backgrounds
• subtle gradients
• soft realistic shadows
• centered composition

This creates a more professional ecommerce catalog appearance.

• Telegram Integration

Users interact with the workflow entirely through Telegram.

Flow:

1. User sends image
2. Workflow processes image
3. Final enhanced image is returned automatically

This makes the system extremely simple for non-technical users.

Infrastructure Setup

Everything runs using Docker containers connected through an internal Docker network.

Services Running

Service	Purpose
n8n	Workflow automation
rembg	AI background removal
sharp-api	Image processing
OpenAI API	AI enhancement

Cost Optimization

One of the biggest goals was keeping generation costs low.

Most preprocessing happens locally using self-hosted services.

That means OpenAI only handles the final enhancement layer.

Approximate cost: ~$0.04 per image

Why This Architecture Works Well

This workflow works surprisingly well because:

• local preprocessing stabilizes AI outputs
• deterministic cleanup reduces hallucinations
• Sharp standardizes composition
• OpenAI focuses only on enhancement
• the pipeline stays lightweight and scalable

Potential Future Improvements

Things I plan to improve later:

• automatic shadow generation
• multi-product support
• aspect-ratio presets
• marketplace-specific exports
• automatic watermarking
• AI quality scoring
• batch processing
• direct Shopify integration
• custom brand templates

Final Thoughts

This started as a simple experiment using n8n and a few self-hosted AI tools.

But the final result became a fully automated AI-powered ecommerce product photography pipeline.

The workflow can take:

• raw mobile product photos
• inconsistent lighting
• messy backgrounds

and automatically transform them into:

• clean
• centered
• ecommerce-ready
• studio-style product images

with almost no manual work.

And the best part is that most of the heavy lifting happens using self-hosted tools.

The AI layer is only used where it actually adds value.

I built an AI-powered expense tracking workflow using n8n.

Now whenever I send a receipt or invoice image to my Telegram bot, the automation automatically:

• extracts invoice details using OCR
• structures the messy OCR text with AI
• detects the merchant/business name
• extracts total amount, tax, invoice number, and date
• categorizes the expense automatically
• uploads the original receipt to Google Drive
• stores everything neatly inside Google Sheets
• sends a confirmation message back to Telegram

The entire process takes just a few seconds.

Built with:

• n8n
• OCRspace API
• OpenAI
• Telegram Bot
• Google Sheets
• Google Drive

No manual expense entry anymore.

I wanted a simple way to track expenses without manually typing invoice details into spreadsheets every time.

So I built a small automation system where I can just send a receipt photo to Telegram, and AI automatically extracts and stores everything for me.

The Problem

Most expense tracking apps still require a lot of manual work:

• Upload receipt
• Enter merchant name
• Add amount
• Select category
• Save invoice somewhere

Doing this repeatedly becomes annoying very quickly.

I wanted something faster and more automated.

The Solution

Now I simply send a receipt or invoice image to a Telegram bot.

The workflow automatically:

• Downloads the receipt
• Extracts text using OCR
• Uses AI to structure the invoice data
• Detects merchant name
• Extracts total amount
• Finds invoice number and date
• Categorizes the expense
• Uploads the original invoice to Google Drive
• Saves structured data into Google Sheets
• Sends me a success notification back in Telegram

Everything happens automatically in a few seconds.

Tech Stack Used

• n8n
• OCR.space API
• OpenAI
• Google Drive
• Google Sheets
• Telegram Bot

Workflow Architecture

Telegram → OCR → AI Structuring → Google Drive → Google Sheets → Telegram Confirmation

Example Extracted Data

The AI extracts structured fields like:

• invoice_biller
• invoice_number
• invoice_total_inc
• invoice_tax
• invoice_date
• invoice_category

Example:

• Biller: JUMBOKING
• Total: 89
• Category: Restaurant

Why I Used AI Instead of Regex

OCR text is messy and inconsistent.

Different invoices have:

• different layouts
• blurry text
• different date formats
• tax variations
• noisy OCR output

Instead of building hundreds of regex rules, I used AI to normalize and structure the data automatically.

This made the system much more reliable.

Current Result

The workflow now works as a personal AI-powered receipt inbox.

I can send invoices directly from my phone and everything gets:

• archived
• categorized
• stored
• tracked automatically

Still improving it, but the current setup is already saving a lot of manual work.