Webhooks waiting behind a batch
One process handled everything.
BoldBellowsn8n queue mode and scaling setup for instances that slow down when a big batch runs
n8n queue mode and scaling setup with workers, Redis and a production database, tested under load before it carries live work
Queue mode splits n8n into a main instance that takes triggers and workers that run executions, with Redis passing jobs between them and a shared database, so capacity grows by adding workers. BoldBellows measures the executions per hour at peak, the longest-running workflows and the memory each uses before deciding how many workers are needed, separates the main instance from the workers, puts Redis and a production database between them and tests the setup under load before it carries live work, then carries out n8n queue mode and scaling setup in a measured order: current load is measured from the executions list, the database is moved to Postgres if it is not already, Redis is added as the queue, the main instance is configured to accept triggers and hand off work, workers are started with a concurrency suited to the memory of the server, webhook handling can be split out if triggers need to stay fast, and the setup is tested with a realistic burst before it takes live work. Monitoring shows queue depth, worker use and failures. Backups and the encryption key are checked. Custom n8n queue mode and scaling setup can cover several environments.
View Pricing
From $1,665, billed once.
- n8n queue mode
- Workers and Redis
- Tested under load
The standards for n8n queue mode scaling
- Load measured firstreal peak, real heavy workflows
- Main and workers separatedtriggers never wait behind big jobs
- Production database and Redisthe queue has a home
- A burst testbefore live work moves over
- Owned exceptionsEvery blocked record names the person who resolves it
- Costs shown earlythe entry package is $1,665, with the delivery range beside it
01the single-process problem
One process doing everything makes every webhook wait for the biggest job
The instance began as a Docker container on a small server. As workflows multiplied, a nightly import started to block the webhooks that arrive in the same hour, so orders waited behind a batch. Memory climbed, the container restarted and executions in flight were lost. Someone read that queue mode would fix it, flipped a setting and found that workers need Redis, a shared database and the same encryption key, and nothing worked. The experiment was rolled back and the instance is still slow.
Memory climbing, then a restart
Executions in flight were lost.
A setting flipped without a plan
Workers lacked Redis and the key.
The same workflows, on an instance that scales
Before: every event is a new queued execution
- Each n8n notification creates a new queued execution
- One process runs webhooks and heavy jobs together
- Restarts lose executions in flight
After: one queued execution, found by its key
- The main instance, the worker and the queued execution decides create or update
- A main instance takes triggers and workers run the jobs
- Queue depth and worker use are monitored
02how it works
How a burst of work becomes a queue that workers clear
The route judges the change first, then finds the queued execution by its key and writes only what is missing.
- Read and judge the change. The n8n event is verified, its account, resource and time are recorded, and the workflow execution is tested against your written rule.
- Measure, separate, connect. Load is measured, the database moves to Postgres, Redis is added, and the main instance and workers are configured to share the same key.
- Test, monitor, switch. A realistic burst is run, queue depth and worker use are monitored, and live work moves over once the test passes.
Limits inside n8n that the route stays within
- Workers add capacity. In queue mode a main instance receives triggers while workers execute them, with Redis carrying the jobs and one shared database underneath, so more capacity means more workers.
- Workers share a key and a database. Every worker must use the same database and the same encryption key as the main instance, or credentials cannot be read, so these are set up and tested before any workflow moves.
- Repair path. When a write cannot be confirmed, Queue Mode Scaling is searched by the main instance, the worker and the queued execution before any second attempt.
03What ships in the build
How scaling is done: measure, separate and test
Essentials decides which changes count and fixes identity. Workflow builds and writes each queued execution. Control keeps watching Queue Mode Scaling after launch.
EssentialsWorkflowControl
Eligibility reader Essentials
Checks each incoming n8n workflow execution against your written rule and records the verdict.
Stable identity ledger Essentials
Stores the n8n reference, the queue mode scaling action and its result, so every later event can be matched to earlier work.
Field map guard Essentials
Only the n8n values on the written map are shaped for Queue Mode Scaling; everything else stays where it began.
Load measurement Workflow
Reads the executions list to find peak load and the heaviest workflows.
Queue architecture Workflow
Sets up the main instance, workers, Redis and the shared Postgres database.
Worker tuning Workflow
Sets concurrency to suit the memory and CPU of each server.
Burst test Control
Runs a realistic burst before live work moves over.
Queue monitoring Control
Shows queue depth, worker use and failures, with alerts.
Exception board Control
Lists every blocked, ambiguous or refused Queue Mode Scaling write with an owner and an age.
N8n queue mode and scaling setup implementation sits alongside n8n queue mode and scaling setup integration and n8n queue mode in the written brief. Related searches include custom n8n queue mode and scaling setup, n8n queue mode and scaling setup service, n8n queue mode and scaling setup workflow, n8n queue mode and scaling setup error handling, n8n queue mode and scaling setup historical migration, n8n queue mode and scaling setup agency, n8n queue mode and scaling setup, n8n docker compose queue mode, n8n queue mode and scaling setup optimization, n8n postgres redis setup, n8n queue mode and scaling setup cost, scale n8n self hosted, n8n high availability, n8n queue mode and scaling setup setup, n8n production scaling, n8n worker concurrency, n8n queue mode and scaling setup developer, hire n8n queue mode and scaling setup expert, n8n webhook processor, n8n workers redis, n8n queue mode and scaling setup compliance, n8n scaling consultant, n8n queue mode and scaling setup specialist, n8n queue mode and scaling setup consultant, n8n queue mode and scaling setup duplicate prevention and n8n performance at scale.
04Who it's for
For finance operations teams and scale n8n beyond one process, with a main instance, workers, Redis and a production database, tested under load before launch
Automation becomes infrastructure as it grows, and infrastructure needs capacity that can be added without a rebuild.
DevOps engineer
"Scale without guesswork."
Load is measured and the setup is tested.
Technical founder
"Stop the slowdowns."
Heavy jobs no longer block webhooks.
Operations lead
"See capacity."
Queue depth shows when to add a worker.
Developer
"Keep credentials working."
Workers share the key and database.
IT lead
"Plan backups."
The database and key are backed up.
Agency owner
"Plan capacity for clients."
Each client environment gets its own sized setup.
05Compare
N8n to Queue Mode Scaling through a single n8n process that slows down whenever a big batch runs, a zap or queue mode with a main instance, workers, Redis, a shared database and monitoring
Each can restart a container. Only one measures the load, separates the workers and proves the setup under a burst.
| How the instance slows | One process | A flipped setting | Our queue setup |
|---|---|---|---|
| What starts the work | Someone notices a change | Any configured event fires | YesA qualified workflow execution passes an explicit admission rule |
| How identity is decided | Staff search names or email | A visible field is assumed unique | YesOne process and a hopeful setting |
| What reaches Queue Mode Scaling | Whatever someone copies | A flat field bundle | YesA measured, separated, tested queue |
| After an uncertain result | Two people compare both systems | The task retries or stops | YesLooks up, compares, then repairs or assigns |
An older event arrives after a newer state
The event time is compared with the stored state, so a late n8n change is logged and cannot overwrite a newer queued execution.
A heavy import and a flood of webhooks arrive in the same minute
Webhooks are accepted by the main instance and queued, the import runs on a worker, and queue depth peaks and then clears. The main instance, the worker and the queued execution is searched and the candidate is compared with what was intended, then one of four results is recorded. Only an absent queued execution is ever created.
Connect n8n to Queue Mode Scaling through the main instance, the worker and the queued execution first; every queued execution and every repair check depends on it.
PricingWorkers, queues and capacity set the price
Pricing scaling: workers and environments
Every option for n8n queue mode scaling has a price you can see. Essentials is $1,665, and the calculator adds the rest.
One setup fee · Range shown first · PDF handover included
View Pricing
Pricing
Build your n8n to Queue Mode Scaling price
Pick a package, answer three short questions about how n8n data should reach Queue Mode Scaling, and your price and turnaround move as you choose.
06The process
Six steps from one process to a scaled instance
Six steps, each with a named output, take the route from brief to a monitored launch.
Measure the load
We read your executions list for peak load, long-running workflows and memory use.
Approve access
Narrow permissions, a named account and a written list of matching keys are put in place for n8n before anything else.
Agree the architecture
The number of workers, the database, Redis hosting and the cutover plan are written down and signed off.
Test the awkward cases
Repeats, late events, missing values and permission loss are run against a test copy of Queue Mode Scaling first.
Launch with notes
Go-live begins at an agreed checkpoint, and a PDF then explains each rule and safeguard.
Watch the first weeks
For the first month we review the checkpoint log with you, look at retries and drift, and fix anything the real data reveals.
07Turnaround
The clock, package by package
Days begin to count after you approve access to n8n.
Essentials
6 to 10 business days
Workflow
10 to 16 business days
Control
16 to 24 business days
08Before we start
Inputs we need from you
Someone with authority over n8n to grant read access
Server access to your n8n installation, its database and the hosting where Redis and workers will run
N8n API access and the events you want the route to use
A written rule for the workflow execution that counts
A named person who owns exceptions and mapping decisions
Any existing automations in n8n or Queue Mode Scaling that touch the same data
09Security and ownership
Only approved fields travel, and neither product is patched
Each n8n object the queue mode scaling route reads is listed, and each place it writes is listed too, before any build begins.
Neither product is modified
N8n and Queue Mode Scaling are reached through their published interfaces; nothing inside either is changed.
Scoped, revocable access
The route asks for read rights where it only needs to read.
Field minimization
Only allowlisted values reach Queue Mode Scaling. Notes, payment details and other n8n data stay in n8n.
Repair begins with a lookup
A retry reads Queue Mode Scaling by the main instance, the worker and the queued execution first, so a doubtful reply never turns into a second queued execution.
Minimal logging
Diagnostics record status codes and checkpoints, nothing sensitive.
Full handover
At the end you receive the full documentation and can run the route without us.
10In their words
What BoldBellows clients say
Verified reviews from operations and finance teams who trust BoldBellows to keep their data moving correctly.
AI Workflow Automation for Agencies
Running a digital agency with many clients was overwhelming. BoldBellows built one automation dashboard that tracks tasks, sends updates and creates client reports automatically.
Clients love the transparency and we love the time we get back. Productivity is up, and project delays have dropped to almost zero.
AI Customer Journey Automation
We wanted a smoother path from first contact to purchase. BoldBellows built an AI system that guides each customer there automatically.
It sends personalized messages, recommends products and follows up at just the right moment. Customer retention has improved dramatically.
AI Lead Qualification & Sales Automation
Our sales team wasted hours chasing cold leads. BoldBellows built an AI lead-scoring system that reads behavior, email engagement and buying signals.
It filters out weak leads and sends personalized follow-ups automatically, so our team only talks to people who are ready to buy. Conversions rose 40% in the first month. It paid for itself straight away.
AI Video & Voice Automation
We publish product videos every week, and BoldBellows introduced us to AI video automation. The system writes the script, voices it and produces the finished video in minutes.
The quality is remarkable: professional voiceovers, clean visuals and smooth editing. Production time went from three days to under 30 minutes, and we scaled our video marketing without adding cost.
AI Email & Smart Inbox Management
Our inbox used to be chaos. BoldBellows built an AI email system that sorts messages, drafts replies and flags anything urgent.
It learns how we write and gets better every week. We reply faster and no longer miss important messages. It feels like having a personal assistant working around the clock.
AI Booking & Scheduling Automation
Our coaching business needed a better way to schedule. BoldBellows automated all of it: bookings, reminders, cancellations and follow-ups.
No-shows fell by 60% and clients enjoy how smooth it is. It feels personal, not robotic. One of the best upgrades we’ve made.
AI Translation & Localisation
When we expanded abroad we needed fast, accurate translations. BoldBellows built an AI translation system that turns our content into several languages instantly.
The translations read naturally and suit each culture. We now serve customers in five new countries without hiring translators. BoldBellows helped us go global.
AI HR & Recruitment Automation
Our HR team was drowning in applications. BoldBellows automated screening, skills-based filtering and interview scheduling.
It saves us hours every week and means we only interview qualified people. Hiring is now faster, better organized and more professional.
AI Accounting & Invoice Automation
BoldBellows automated our whole invoicing process: creating invoices, sending reminders and tracking payments.
Late payments dropped sharply, and our accounting team finally has time for strategy instead of repetitive admin. Worth every penny.
AI Chatbot & Customer Support
BoldBellows built an AI support chatbot for our online boutique, and it has changed how we run the business. We used to have two full-time staff answering the same questions all day. Now the AI handles order tracking, product recommendations and even refund requests on its own.
What surprised me most is how natural it sounds. Customers compliment the ‘agent’ without realizing it’s AI. Our support workload dropped by 75% and customer satisfaction went up dramatically.
AI Content & Social Media Automation
Our marketing agency couldn’t keep up with content. BoldBellows set up an AI content engine that writes blog posts and captions and even designs our social media creatives.
It spots trends and suggests topics for us, so we stay ahead of competitors. We now produce three times the content with the same team, and engagement has soared. They didn’t just automate our workflow, they lifted our whole brand.
AI Data Entry & Reporting Automation
We used to spend hours collecting data and building weekly reports by hand. BoldBellows automated all of it.
The reports are clean, visual and easy to read, and our managers rely on them for quick decisions. Human error is gone and our numbers are more accurate across the board.
AI E-commerce Listings Automation
BoldBellows automated our product listings. The AI writes descriptions, organizes photos and publishes listings across several marketplaces.
It even answers customer questions instantly. Our store looks more professional and sales have noticeably increased.
AI Document & Contract Automation
Onboarding was slow because we wrote every contract by hand. BoldBellows automated the lot: contracts, welcome emails and client setup.
What took 48 hours now takes under 10 minutes, and clients regularly tell us how professional it feels.
AI Social Comment & DM Automation
We get thousands of comments and messages every week. BoldBellows built an AI system that replies instantly, filters spam and surfaces the important ones.
Engagement is up and our page looks active around the clock. It’s like having a full social media team that never stops.
AI CRM Automation
Our CRM was barely used because updating it by hand was tedious. BoldBellows automated data entry, tagging, segmentation and follow-ups.
Now the CRM is always up to date and our campaigns are far more accurate. It improved our whole sales pipeline.
AI Voice Assistant
BoldBellows built a custom AI voice assistant for our customer hotline. It answers questions, books appointments and handles simple requests.
Customers love how fast it is, and our call-centre workload dropped dramatically. One of the smartest upgrades we’ve made.
AI Automation Partner
BoldBellows is hands-down the best AI automation partner we’ve worked with. Their systems are fast, reliable and built around how our business actually works.
Every automation they’ve delivered, from customer service to content, runs flawlessly. We’ve saved time, cut costs and grown faster than we expected.
11FAQ
Scaling n8n: what engineers and owners ask
If you are weighing this up, these are the points that usually matter.
Is it worth building n8n queue mode scaling when a zap exists?
If you only need an n8n that stays responsive when workload grows, a zap will do it. It will not run heavy workflows without blocking webhooks, add capacity by adding workers and see when it is needed. Closing those gaps is what this build is for.
What is queue mode?
A setup in which a main n8n instance takes triggers and workers run the executions, with Redis passing jobs between them.
Do we need Postgres?
A shared production database such as Postgres is needed so all workers read the same data.
What goes wrong if the key differs?
Workers cannot read stored credentials, so every worker must use the same encryption key.
How do you test it?
With a realistic burst of executions before live work is moved over.
Can we add workers later?
Yes. Capacity grows by starting more workers, and the monitoring shows when.
Can I get a fixed price for n8n queue mode and scaling setup?
Yes. Environments and workers drive one price, which you approve in writing before anything moves.
Do we get to approve what queue mode scaling reads in n8n?
The database, the queue, the encryption key and each worker's limits are written down together, and the sheet becomes the build's reference once approved.
Can we set the conditions under which queue mode scaling runs?
Yes. The n8n queue mode scaling route can follow rules you define, and the lowest package is $1,665.
What if the n8n platform behaves differently next year?
Each external dependency is recorded. If one changes, the route refuses to guess and flags the record. Repair after the review period is a new, priced task.
Next stepMake n8n handle the busy hour
Give n8n workers, a queue and a burst test
Share how many executions your busiest hour brings and which workflows are heaviest, and a quote follows that you can accept or decline before any server is touched.
- From $1,665, paid once
- Load measured first
- Burst tested
- No monthly fee from us
Tell us about the complications and we will fold them into a custom quote.