Connect First AI Employee to Microsoft Teams.

Team chat2 routesRoute facts checked August 28, 2026

This page shows every cataloged route for this app and marks the most capable working path. The recommended route is serving now after you authorize your own account.

You authorize and keep control of the provider account. No page view means an account is connected.

Recommended route

Built-in report channel

Call summaries are posted through the Teams Workflow webhook you provide. This channel posts concise call summaries. Full transcripts remain in the dashboard and verified report email.

Every available route

More than one route is shown when it adds a real capability or gives you a customer-owned alternative. Recommended means most capable today, not already connected.

Built-in channel

Built-in report channel

Serving now

Recommended route

What it does

Call summaries are posted through the Teams Workflow webhook you provide.

Before you start

Create a Teams Workflow for the destination channel, then paste its webhook under Channels.

What it does not do

This channel posts concise call summaries. Full transcripts remain in the dashboard and verified report email.

Set it up

Sign in to First AI Employee and open Integrations.
Choose Microsoft Teams, then approve access in the provider’s own authorization screen.
Create a Teams Workflow for the destination channel, then paste its webhook under Channels.
Save the destination. Complete one non-production call and confirm the expected record in the provider.

n8n Cloud

Downloadable n8n Cloud workflow starter

Customer setup required

What it does

A completed call runs Post channel message in Microsoft Teams after you configure and enable the destination node.

Before you start

Microsoft Teams OAuth2. Authorize Microsoft Teams and choose the team and channel that receives call summaries.

What it does not do

This route receives completed calls only. The synthetic dashboard test stops before the destination, so it proves transport but not the provider write. Event-ID replay memory is bounded best effort, and one n8n webhook URL is stored per tenant.

Set it up

Download the app-specific starter from Integrations in your First AI Employee dashboard and import it into n8n Cloud.
Authorize Microsoft Teams, choose the customer-owned resource, and complete this requirement: Authorize Microsoft Teams and choose the team and channel that receives call summaries.
Configure and enable the destination node, then activate the workflow.
Copy the production /webhook/ URL into the dashboard automation connection. Test URLs and self-hosted n8n hosts are rejected.
Send the dashboard transport test, then run a real non-production completed call and confirm the destination record yourself.

Provider documentation

Set it up: Built-in report channel

Create a Teams Workflow for the destination channel, then paste its webhook under Channels.

Choose Microsoft Teams, then approve access in the provider’s own authorization screen.

Create a Teams Workflow for the destination channel, then paste its webhook under Channels.

Save the destination. Complete one non-production call and confirm the expected record in the provider.

Verify the complete result

Use the channel test, then confirm one real non-production call summary arrives in the selected destination.

Account ownership and data boundaries

The route sends only the event fields needed for the action you configure. Provider credentials stay in the approved connection or are sealed by First AI Employee where the guide explicitly says so.

Your provider and automation accounts remain yours.
A successful transport test is not the same as a verified provider write.
The pages never claim a native or two-way sync unless that exact capability exists.

Ready to connect it?

Use the dashboard to authorize your account, select the customer-owned destination, and test the complete downstream result.

Open Integrations in your dashboard Browse all app guides