# Execute sub-workflows in parallel

**URL:** <https://community.n8n.io/t/execute-sub-workflows-in-parallel/144892>\
**Category:** Feature Requests\
**Created:** [July 7, 2025, 2:55am UTC](https://community.n8n.io/t/execute-sub-workflows-in-parallel/144892 "2025-07-07T02:55:15Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Renza\_Polza](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/renza_polza/32/136118_2.png) [@Renza\_Polza](https://community.n8n.io/u/Renza_Polza)\
**Post date:** [November 9, 2025, 2:10pm UTC](https://community.n8n.io/t/execute-sub-workflows-in-parallel/144892/2 "2025-11-09T14:10:19Z")

</div>

I think this would be a good usecase for this requested feature:

> [@Parallell execution semantics](http://community.n8n.io/t/parallell-execution-semantics/82089):
>
> The idea is: These days all languages support parallel execution. E.g. Java had this since Java5 I remember. (Of course behind the scenes, CPU power is distributed between different cores and different threads - which makes it in reality more / less “really” parallel - but this matters not for the user). I do believe it can matter for the user to have, in n8n, a construct to simulate such parallellisme. I believe this could be done with just 2 Nodes and 2 variables: A splitting Node (from …

---

_[View the full topic](https://community.n8n.io/t/execute-sub-workflows-in-parallel/144892)._
