Hey everyone. I’m trying to use a Gmail trigger and a manual trigger to a merge node. However, the moment I add the second trigger, the execute workflow button changes and makes me choose which trigger to run. Because of this, I’m not able to move forward and the merge node does not recieve both inputs to merge into one. Is this an error with the new update or is there a setting I need to change in order to get this to run?
Hi,
This sounds like the intended behaviour, if you are relying on some input from your Gmail trigger then you would need to either execute that node to get some data into the merge or alternatively add mock data to the gmail trigger that you can use for testing.
I assume the final result should only have the gmail trigger, otherwise i dont understand the purpose here, maybe you can share the workflow so we can see what you are trying to do 
Hello,
I’m running a gmail trigger to push a pdf “binary” file and a get url node into a merge node. I need somewhere to store the pdf temporarily. I saw this work on a training video and can’t seem to replicate this step because I’m being asked to choose one execution over the other. I’m not sure if a newer update caused this or if there is a work around. Here is a screenshot of what I have so far.
Hey,
In your current setup “Get file upload URL” runs in a separate execution so would not be executed and available to the merge node, you could have that node in between the Gmail trigger and the Merge node so it executes when the gmail is triggered and both inputs are then available to the merge node.
You should not need to add a temporary storage as the binary output of the file download is available in memory for the execution (but not persisted afterwards). Which is fine if you are just taking the data and sending it to another endpoint.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.