Connect Microsoft Teams

Connect Microsoft Teams so your workflows can post notifications to your Teams channels. Once connected, Teams becomes a destination you can pick inside a workflow action — you don't send anything from this screen.

Find it under Settings ▸ Connections ▸ Integrations.

The connectors list

The Integrations page lists the third-party services you can connect. Today that's a single connector: Microsoft Teams. Its card shows the connector name and the tagline "Send workflow notifications to Microsoft Teams channels." When your organization is already connected, the card shows a Connected badge.

Select the Microsoft Teams card to open its detail pane, where you connect, reconnect, or disconnect.

Connect Microsoft Teams

If you're not connected yet, the detail pane shows a Get started section. Select Connect Microsoft Teams.

Nash sends you to Microsoft to authorize access — this is a full-page redirect, not a popup, so you'll leave the portal for Microsoft's sign-in and consent screens. Microsoft asks you to approve access to post messages in your Teams channels and to upload files to them, so a workflow action can deliver both messages and file attachments. After you approve, Microsoft returns you to the Integrations page and the connection shows as Connected.

Note

The Connections group is available to non-provider organizations. If you don't see Integrations under Settings, reach out to Nash.

Reconnect or disconnect

Once connected, the detail pane shows a Connection section with two actions:

• Reconnect — sends you back through Microsoft's authorization again. Use this if the connection stops working or you need to re-approve access.

Note

If you connected Teams before file delivery was supported, the card may show as not connected even though nothing changed on your side. That's because the connection needs to be re-approved to grant the newer file-upload access. Select Reconnect and approve again on Microsoft's screen to restore it. Whether your workflows can deliver file attachments to Teams varies by organization — reach out to Nash if you're not sure. - Disconnect — opens a confirmation dialog. Confirming removes the connection between your organization and Microsoft Teams.

Warning

Disconnecting stops any workflow actions that send Teams notifications until you reconnect. Disconnect only when you intend to turn those notifications off.

Where you use a connected Teams

Connecting here doesn't send messages on its own — it makes Teams available as a notification destination in your workflows. You pick the specific team and channel in the Send a Teams message workflow action, not on this screen.

To build that, see what workflows are and add a Send a Teams message action to a workflow. The action is where you choose the destination and write the message; the connection you set up here is what lets it deliver.