[N8N BUG] Outlook Node "Reply to a message"

[Arthur_Moreau]

Bug Report — Outlook node: conflict between two fields named message (body vs messageId) causing AI Agent ambiguity

Title
Outlook node — two message fields (body & messageId) cause ambiguity for AI Agent

Description / Context
I’m building a flow in n8n using the Outlook node in reply mode. In my input data, I have two fields both named message:

• One for the body (content) of the message to send
• One for the message ID (the ID of the email to reply to)

When I pass this into an AI Agent node, the agent cannot disambiguate which message field to use, resulting in a collision / ambiguity.
This prevents me from using the simple “reply” pattern with AI + Outlook integration, and forces me to use a workaround (e.g. creating a new message instead of replying), which breaks the conversation.

Steps to Reproduce

1. Create an Outlook node configured for reply operation
2. Set its parameters such that both Message fields are filled by A
3. Connect the Outlook node output into an AI Agent node
4. Execute the workflow
5. The AI Agent fails to start because it can’t resolve the duplicate message key

Expected Behavior

• The framework or node should disambiguate the duplicate keys (for example: call one Message Id, and the other Message)
• The Outlook node could rename or alias one of them (e.g.Message Id, Message)

Actual Behavior

• The AI Agent node receives ambiguous input and cannot reliably determine which message field is intended
• The flow fails or behaves unpredictably in this scenario

Environment

• Hosting : cloud

Workarounds Tried

• I bypassed this by creating a new message instead of reply, but this doesn’t look as professional

Suggested Fixes / Improvements

• Rename / alias fields so there is no key collision

Severity / Impact
This is a blocking issue for workflows where AI Agent must reply to emails via Outlook, because it prevents seamless integration using reply pattern while preserving threading.