M365 AgentInstall

Summary

M365Agent Message Reply - Reply to a message in an M365 Agent conversation

Inputs

• authKind (required) — Authentication method: classicBot (Azure Bot Service + Entra App) or agent365 (Entra Agent Identity)
• conversationSource (required) — Where conversation routing info comes from: From Envelope (default, uses envelope for replies) or Specify Manually (provide serviceUrl/conversationId)
• text (required) — Message content. For @mentions, use the Options collection.
• serviceUrl — Bot Connector service URL for the target channel (required if conversationSource=manual)
• conversationId — The conversation ID. For Teams channels this looks like 19:xxx@thread.tacv2 (required if conversationSource=manual)
• channelId — Azure Bot Service channel the conversation belongs to
• activityId — Required only for Reply / Update / Delete operations against a specific activity. Leave empty for proactive sends.
• options — Collection: workflowFooter (boolean), mentions (fixedCollection), rawActivityOverride (string), suggestedActions (collection)
• to — Override the recipient list. By default targets the inbound clicker from envelope
• identityMode — Only for authKind=agent365: autonomous (agent's Blueprint identity) or agentUser (agent's own M365 user)
• userSelectorMode — Only for authKind=agent365 + identityMode=agentUser: byUpn or byObjectId
• agentUsername — UPN of the agentic user (e.g. agent@contoso.com)
• agentUserId — Object ID of the agentic user

Output shape

The workflow item continues with the sent activity metadata; typical n8n item passthrough

Returns the modified item; exact output structure follows n8n node conventions

Examples

Example 1: Reply with default From Envelope source

Set conversationSource=From Envelope (default). Provide text and optional mentions/suggestedActions. The node extracts conversationReference from the inbound trigger envelope.

Links

• n8n community nodes installation guide