How to Scale an n8n Web Audit Service for Multiple Concurrent Users?

Questions
,
1

Hello n8n community,

I’m building a service where users can request a website audit report through a simple web interface. The current, basic setup works like this:

  1. A user submits a website URL via a form on my web app.

  2. My app sends this URL to n8n (likely via a Webhook node).

  3. An n8n workflow is triggered, which runs tools like Lighthouse, SEO checkers, etc., to generate a report.

  4. The workflow then sends the generated report (e.g., a PDF or a link to it) back to the user, perhaps via email or by updating a status on my web interface.

The problem I’m facing is one of scaling and concurrency. If multiple users submit their URLs at the same time, my current n8n workflow can only process one URL at a time. This creates a queue where users have to wait an unacceptably long time if the system is busy, which is not viable for a commercial service.

My Core Question:
What is the best practice in n8n to handle this kind of multi-tenant, queue-based workload where many independent requests need to be processed efficiently?

2

Hi there, you need to implement the Queue Mode of n8n, where you can read it here

or if you prefer video, then you can watch this

but for short, queue mode is basically the right way to handle your case, because the way it goes, is it will have multiple instance of n8n, where one is in charge as like the boss, and routing task to the other instance of n8n for them to work on it, so it’s better for scalability, parallel execution, load balancing, etc.

hope it helps!

2 Likes
3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.