HTTP request instead of execute workflow

Questions
1

Hi All,

I am currently running n8n in queue mode and have some workflows which are interacting with other workflows by using the “Execute Workflow” node.
What i saw in my analysis it, that when my worker beginns to work and runs a workflow which triggers another workflow, the same worker also works on the Sub-Workflow.
So now i was wondering, if i use a HTTP-Request instead to trigger the workflow, it should use probably a free worker to handle the workflow. THat would maybe speed up my execution time, as i can split the one workflow out to other ones.

I was just wondering, do i miss anything about this assumption, or is it just that simple? Hopefully a quite simple question to answer haha

Thanks in Advance
Chris

Information on your n8n setup

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

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:
4

Hi @Schlech,

Nah, you got it! Subworkflows are executed as part of the main workflow on the same worker. They don’t “cost” an extra execution either and don’t need to be active to be called. So if you’re on cloud/enterprise and have a max limit of executions/active wfs it’s handy. But on self-hosted this doesn’t affect you so go with the HTTP Requests :v: