This error happens because the Gmail “Send and Wait for Response” node needs n8n to keep the workflow open with an execution id, which is something like a ticket number, but since your workflow starts from an MCP client, n8n doesn’t create that ticket, so when Gmail tries to wait it fails. The fix is to not use “Send and Wait”; instead, just send the email normally, and then use a Gmail Trigger node in another workflow to catch the reply and continue the process.
The problem I want to solve is: We need to enable Decision Model and Notation (DMN) execution as part of our A2A integration with MCP through n8n.
Essentially, the challenge is: How can we achieve DMN workflows within our A2A MCP integration, given that n8n does not currently support this functionality?
The intended flow is:
An A2A agent sends a request that triggers an email.
When it reaches to n8n MCP Server Trigger, the gmail tool then send and wait for the recipient’s response.
Once the user clicks “Approve” in the email, n8n should revert it back to the source agent and it should continue with the subsequent flow.