Microsoft Teams BotInstall

Summary

Send a proactive message to a Teams conversation using a stored reference key that identifies the target conversation and service URL.

Inputs

• Reference Key (required) — Key referring to a stored conversation reference identifying the Teams conversation to send message to.
• Message Text — Plain text content of the proactive message to send. Ignored if Activity JSON is provided.
• Activity JSON — Raw JSON defining the full activity payload to send; overrides Message Text if set.
• Mention Options — Options to include mentions in the message, such as auto mention sender, mention ID, mention name, and whether to prepend mention text.
• Execution Options — Controls debug output inclusion, output mode shaping (pass through, merge, response only), retry count, and retry delay for API requests.

Output shape

A list of items with JSON containing details about the outbound proactive message: resource, operation, HTTP method, request path, and response from the Teams API. Debug metadata may be included if enabled.

If the Reference Key is invalid or missing stored conversation info (service URL or conversation ID), the operation throws an error. Message content can be specified either by Message Text or by full Activity JSON. Mentions can be automatically added or customized via Mention Options. Execution Options allow control over retries and output formatting.

Examples

Example 1: Send a simple proactive message using a known reference key

Set Reference Key to identify the conversation, enter the Message Text, optionally configure Mention Options to mention the sender or a user, and execute to send the message.

Links

• n8n community nodes installation guide