Question on the full N8N stack (main, webhook and worker)

Questions
,
1

Hi,

I have deploy the full stack (main, worker and webhook process) and I have several questions:

  1. The main process trigger every executions of workflow. With webhook processors, the main process still in charge to trigger execution from a webhook call (or it will be the WEbhook Processor) ?
  2. There a limit of number of Webhook Processor for a main processor ? Can have 100 webhook processor for a main processor ?
  3. What is the difference between EXECUTIONS_TIMEOUT and EXECUTIONS_TIMEOUT_MAX ? How they interact ? Link to the documentation
  4. What is the difference between N8N_HOST and N8N_EDITOR_BASE_URL ? Can they be on a different domains name (ex: n8n.popo.com and admin.n8n.tutu.co) ?

Thx
Sylvain

2

Hi @sGendrot,

With webhook processors, the main process still in charge to trigger execution from a webhook call

This depends on how you configure your load balancer. Usually, you’d route webhook requests directly to the webhook processors as suggested here (meaning the main processor won’t have to deal with them): Configuring queue mode | n8n Docs

There a limit of number of Webhook Processor for a main processor ? Can have 100 webhook processor for a main processor ?

Nope, no hard limit I am aware of.

What is the difference between EXECUTIONS_TIMEOUT and EXECUTIONS_TIMEOUT_MAX ? How they interact ? Link to the documentation

EXECUTIONS_TIMEOUT will specify the default timeout value for your workflows (which you can overwrite in the UI), while EXECUTIONS_TIMEOUT_MAX will specify a maximum value that cannot be overridden. So setting something like EXECUTIONS_TIMEOUT=30 and EXECUTIONS_TIMEOUT_MAX=60 means your workflows have a default setting like this:

image
image1378×864 91.8 KB

And n8n would prevent users from setting timeouts > 60 seconds:

image
image1378×896 78.1 KB

What is the difference between N8N_HOST and N8N_EDITOR_BASE_URL ? Can they be on a different domains name (ex: n8n.popo.com and admin.n8n.tutu.co) ?

From quickly checking this in our code, N8N_EDITOR_BASE_URL seems to be used exclusively to overwrite the URL sent out in the conformation emails for newly invited users of your n8n instance.

3 Likes
3

Thx for the precisions.

If I understand correctly, the full process of a HTTP call with Webhook processor and Worker will be this:

n8n-webhook
n8n-webhook793×492 67.1 KB

4

Hi @sGendrot, I believe you’re spot on here, but @krynble would be the best person to confirm the exact behaviour of n8n in queue mode.

1 Like
5

Hey @sGendrot and @MutedJam

You are both on point with the answers and diagram. This is precise.

One information I’d add is that, just as your diagram shows, the Main process has no relation to running executions when you have Webhook + Worker.

In this deployment scenario, the Main instance’s responsibilities are:

  • Edit, activate and deactivate workflows
  • View executions
  • Trigger any non-HTTP related execution, such as timers, database triggers, pollers, etc
2 Likes