> For the complete documentation index, see [llms.txt](https://docs.aisera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aisera.com/aisera-platform/what-can-my-bot-do/ai-automation-optimize-flow/ai-workflow-studio/workflow-reference-guides/workflow-nodes/operations-nodes/parallel.md).

# Parallel

The Parallel node allows you to add sub-flows to your workflow that run at the same time.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfdgtLbvXGcgy-cBLuLw-7e_Y7cVS_pj5-OTjRUvLMtV7VVrj0NqGrHOiVTdeEOzGzv_69eF2zTrw1jTvSdmTF2RjTlz19_yHfibFf-I-3UTj6k5-0FqwlpyKL_2VDjnXILPKEbxSYYbUEImv4xCLa9mQQZ7_7QizZpovZuIw?key=sfGKh0R8e3YhQpYWUXasmA" alt=""><figcaption></figcaption></figure>

Specifically, you can use parallel processing with subflows that contain non-interactive nodes. \
You can’t use parallel processing with **User Interaction** nodes like **Message**, **User Input**, **Callback**, **AskForApproval** or **V2**).

* Parallel sub-flow processing is ideal for customers who need to perform a set of actions at the same time (such as performing multiple changes in different external systems).
* Parallel sub-flow processing makes the workflow more “clean”, since a single node substitutes a sequence of subflow nodes.