Gmail Send & Wait Node Returning Partial Form Data in Multi-Node Workflow

Below is some guidance based on our documentation and best practices with n8n form nodes:

• It appears that using two instances of the Gmail Send & Wait node with the Custom Form response type within a single workflow can lead to issues with field mapping. In your case, the second node seems to miss one text field while the first works as expected.
• In workflows that rely on webhook-based nodes (like Send & Wait nodes collecting form responses), using more than one in a single execution path may cause data collisions or conflicts with the incoming responses.
• One way to work around this is to isolate the response flows. Splitting the form response handling into separate sub-workflows can help ensure that each Send & Wait node uses its own context and webhook URLs. This separation limits any interference from one instance to another.
• In practice, you could have your primary workflow trigger one sub-workflow for client review using one Send & Wait node and then, after its completion, trigger the next sub-workflow that uses the second Send & Wait node. This strategy keeps each response handler independent and may resolve the data loss issue you’re experiencing.

Overall, using a sub-workflow (or even separate workflows) for each Send & Wait instance is a recommended approach if you start seeing inconsistent or incomplete form responses in a single workflow.