Webhook sequential processing?

[itsmeayyub]

I have a question about how webhooks handle data:

If a webhook receives two pieces of data simultaneously, will it process both at the same time, or handle one data piece at a time, starting the second after the first workflow has finished?

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[dkindlund]

It’s parallelized by default – meaning, n8n will attempt to process multiple inbound webhooks simultaneously. There is no built-in rate limiting or concurrency control; you would need to use something like hookdeck.com – but even then, it’s not a ideal/perfect solution.

See this thread for more details:

Add concurrency in workflow settings

The idea is: I need in workflow settings a way to set the number of concurrent jobs for each workflow. My use case: I have a given workflow which must be capable of handling concurrent executions. I also have a workflow which SHOULD not run concurrent execution because sharing a common resource. The --concurrency option is not a solution because it applies to all workflows. I think it would be beneficial to add this because: No the only one in this case Worker concurrency! Any resources to …