# Execute Workflow: Incorporate "Set" Functionality

**URL:** <https://community.n8n.io/t/execute-workflow-incorporate-set-functionality/21191>\
**Category:** Nodes\
**Tags:** node\
**Created:** [December 27, 2022, 6:14pm UTC](https://community.n8n.io/t/execute-workflow-incorporate-set-functionality/21191 "2022-12-27T18:14:26Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Luke\_Austin](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/luke_austin/32/10505_2.png) [@Luke\_Austin](https://community.n8n.io/u/Luke_Austin)\
**Post date:** [December 27, 2022, 6:14pm UTC](https://community.n8n.io/t/execute-workflow-incorporate-set-functionality/21191/1 "2022-12-27T18:14:26Z")

</div>

## Hi! As it says, it would be very helpful if the “Execute Workflow” node could also have the functionality of the Set node.

## My use case:

I frequently find myself placing a “set” node before calling a sub function in another workflow, in order to pass some dynamic variables / add variables to the data i am passing to that workflow.

Integrating the two together would be a great timesaver and simplify my workflows at least!

I often end up like this - (real life workflow):

 ![image](https://europe1.discourse-cdn.com/n8n/original/3X/2/6/262609cf7ba2c47e9ef1a78dd169b3aa3aa09e14.png)