M365 AgentInstall

Summary

Update raw attachment in M365 Agent conversation

Inputs

• authKind — Authentication method. Default: classicBot. Options: classicBot (Azure Bot + Entra App), agent365 (Entra Agent Identity, no Azure Bot resource).
• conversationSource — Source of conversation routing info. Default: envelope. Options: envelope (uses current item's conversationReference for replies/updates/deletes), manual (requires serviceUrl and conversationId filled by user).
• serviceUrl — Bot Connector service URL for the target channel. Required when conversationSource is manual and resource is rawAttachment. Placeholder: https://smba.trafficmanager.net/emea/
• conversationId — Conversation ID. Required when conversationSource is manual and resource is rawAttachment. For Teams channels format: 19:…@thread.tacv2. Can use expression like {{ $JSON.channelId }}.
• channelId — Azure Bot Service channel the conversation belongs to. Default: msteams. Options: directline, emulator, msteamscopilot, msteams, webchat.
• activityId — Required only for Reply/Update/Delete against a specific activity. Leave empty for proactive sends.
• contentType (required) — Attachment MIME / card content type. Placeholder: application/vnd.microsoft.card.adaptive
• content (required) — Attachment content — the object that goes into Attachment.content. Default: ={} (empty JSON object).
• options — Collection of optional attachment properties. Items: contentUrl (string), name (string), rawActivityOverride (string, raw JSON to replace constructed Activity body), thumbnailUrl (string).
• identityMode — Only when authKind is agent365 and resource is rawAttachment and operation is update. Default: autonomous. Options: autonomous (agent acts as Blueprint app identity), agentUser (agent acts as its own M365 user, requires sidecar transport and separate license on the agentic user account).
• userSelectorMode — Only when authKind is agent365, resource is rawAttachment, operation is update, and identityMode is agentUser. Default: byUpn. Options: byUpn (select by user principal name), byObjectId (select by Azure AD object ID).
• agentUsername — UPN of the agentic user. Defaults to credential's Default Agent Username. Expression: {{ $credentials.defaultAgentUsername || '' }}. Only shown when authKind=agent365, resource=rawAttachment, operation=update, identityMode=agentUser, userSelectorMode=byUpn.
• agentUserId — Object ID of the agentic user. Only shown when authKind=agent365, resource=rawAttachment, operation=update, identityMode=agentUser, userSelectorMode=byObjectId. Placeholder format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.

Output shape

The operation returns the updated n8n item containing the modified activity with the raw attachment. Exact return shape is not explicitly declared in the node's properties or source signatures; workflow authors should expect the standard M365 Agent update response format.

If conversationSource is set to 'envelope', the conversationReference is automatically resolved from the current item. When set to 'manual', the workflow must provide valid serviceUrl and conversationId values. The content and contentType parameters are always required for the attachment payload. Raw activity override allows protocol-level customization (e.g., custom channelData, experimental Activity shapes) by supplying a full JSON activity body that overrides the constructed payload.

Examples

Example 1: Update an attachment in an existing Teams conversation using conversation reference from the item envelope.

Set authKind to classicBot (or agent365), leave conversationSource as envelope (default), ensure content and contentType are provided. The node will use the conversationReference from the incoming item to locate and update the attachment.

Example 2: Proactively update an attachment in a specific conversation outside the item envelope.

Set conversationSource to manual, provide serviceUrl (e.g., https://smba.trafficmanager.net/emea/), conversationId (e.g., 19:xxxx@thread.tacv2), contentType, and content. Optionally set channelId, activityId, and options as needed.

Links

• n8n community nodes installation guide