Gmail Send & Wait Node Doesn't Return ALL Responses

[JeffM]

I’m using the Gmail Send & Wait for client review. For response type I’ve selected Custom Form. I have 4 drop downs and 4 text fields. Unfortunately, I can’t attach a pic of the entire node, but I’ve attached a sample.

In my workflow, I have two Send & Wait nodes…one at beginning, one at end. The first works great and collects all data entered into the form. The second node never returns all data. If four text fields have text, it’ll collect text from three and label the other as “null”.

As I type, I wonder if having two of these nodes in one workflow is problematic. Perhaps I should create a sub-workflow?

Any suggestions would GREATLY be appreciated. Thank you!

N8N version: 1.80.3

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[solomon]

I don’t know about the conflicts of having two nodes in the same workflow.

But if you could share your JSON here, I’d gladly take a look at your logic.
Just select your nodes, copy and paste here in a code block

like this

[JeffM]

Thanks SO much! You’re very kind to do that. The problem node is Gmail-Final Approval.

[solomon]

My result is even worse…

With a simple workflow like this:

All I get is one item

But this setup works:

@Jon another bug?

[JeffM]

Thanks SO much for testing! So, is the takeaway a simpler form may be the way to go? I can remove the drop downs from the second Send & Wait node and just keep the textfields and adjust my filter to just look for populated textfields.

For the heck of it, I’m going to try creating a new sub-workflow for my current 2nd Gmail node. I’ll report back.

BUT, it definitely sounds like a bug. Appreciate your help!

[solomon]

Sure thing!

I haven’t had the chance to test it thoroughly enough to pinpoint the exact cause of the bug. If you can narrow it down and figure out the exact steps to reproduce it, I’ll create a report on GitHub.

I’m sure the development team will give it the attention it deserves.

[JeffM]

Success! I deleted all the dropdowns and just kept the four text fields. I alerted my code node after this one to interpret empty fields as “Approved”. After a couple of tests, it now recognizes all data. Thank you again!

[solomon]

Happy to help! I’m glad you could solve this

Please mark this topic as solved by choosing a solution