I am trying to implement a gmail listener in a subworkflow. But when I execute the subworkflow, the [when called by another workflow node] doesn’t execute. The gmail listener trigger executes, and if I check the main workflow the output of the sub-workflow are not passed.
I tried executing both the [when called by another workflow node] and the gmail trigger it gave null as an output
A workflow is always triggered by one trigger. What you are doing here is a bit weird, as you expect 2 triggers?
I think you want to execute a subworkflow within your workflow that is triggered by gmail. So you need the normal Execute workflow node and trigger a subflow with that.
I am not certain what you want to do here, so explaining that would help us help you. Also could be worth it doing the courses to get more knowledge on how n8n works.
You are correct @BramKn I want to execute a subworkflow within my workflow. I tried using only one trigger for the subworkflow, but the output doesn’t get passed to the main workflow.
Hi @vctry
I think you are misunderstanding something here.
A subflow can never start with a gmail trigger.
It will always start with an execute workflow trigger.
That explains why it’s not passing the output of the last node. So how do you suggest I execute the gmail trigger.
Here is what I want to accomplish @BramKn, I need the gmail trigger to listen for new messages/inbox(replies) on a designated gmail. Which then passes it onto the next node
It should be as simple as having a gmail trigger and then your workflow after that. You can then use an execute workflow node to trigger a subflow in your workflow.
It might be good to get your n8n understanding up a bit by doing the courses. they should help you with understanding the basics of n8n.