# "Execute Workflow Trigger" Node - returned data

**URL:** <https://community.n8n.io/t/execute-workflow-trigger-node-returned-data/44883>\
**Category:** Questions\
**Created:** [April 23, 2024, 2:46pm UTC](https://community.n8n.io/t/execute-workflow-trigger-node-returned-data/44883 "2024-04-23T14:46:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![FelixL](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/felixl/32/24866_2.png) [@FelixL](https://community.n8n.io/u/FelixL)\
**Post date:** [April 23, 2024, 2:46pm UTC](https://community.n8n.io/t/execute-workflow-trigger-node-returned-data/44883/1 "2024-04-23T14:46:13Z")

</div>

I hope this is not a duplicate (I’ve not found anything in Feature requests, nor here in Questions)

Is there another way to set the output of a subworkflow than the positon of the nodes on the canvas?  
Usually its not a problem when developing a workflow, but when updating a subworkflow its really easy to mess up when you change just a little thing.  
Perfect solution would be something like the “Respond to http request” node, just for the “Execute Workflow Trigger” node.

Example:  
this Subworkflow should output the result (count) of the aggregation node, but when the nodes are not on their correct position it returns the false result.

This does not work:

## Information on your n8n setup

- \*\*n8n version:\*\*1.37.3
- \*\*Database (default: SQLite):\*\*postgres
- \*\*n8n EXECUTIONS\_PROCESS setting (default: own, main):\*\*queue
- \*\*Running n8n via (Docker, npm, n8n cloud, desktop app):\*\*docker
- \*\*Operating system:\*\*Ubuntu

---

<div class="post-metadata">

**Author:** ![barn4k](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/barn4k/32/8170_2.png) [@barn4k](https://community.n8n.io/u/barn4k)\
**Post date:** [April 23, 2024, 6:30pm UTC](https://community.n8n.io/t/execute-workflow-trigger-node-returned-data/44883/2 "2024-04-23T18:30:56Z")

</div>

hello @FelixL

That’s because of this

 ![image](https://europe1.discourse-cdn.com/n8n/original/3X/9/b/9b117cc3fd6a39ecc78bb7051e20e049fd4688ae.png)

As n8n doesn’t execute nodes asynchronously, they will be executed in an order. That order depends on the workflow settings (execution order). To avoid such an issue, you should use the merge node to connect the http node and pipedrive node as inputs. Set the operation to return only input with pipedrive.

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/195824_2.png) [@system](https://community.n8n.io/u/system)\
**Post date:** [July 22, 2024, 6:31pm UTC](https://community.n8n.io/t/execute-workflow-trigger-node-returned-data/44883/3 "2024-07-22T18:31:15Z")

</div>

Closed on July 22, 2024, 6:31pm UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.