Connector library

Implemented source Collaboration & Productivity APIs

Microsoft Teams connector.

Post, read and reply to Microsoft Teams channel messages through Microsoft Graph with delegated authentication.

Connector download

Download Microsoft Teams

Versioned ZIP for your CXFabric tenant.

Use this connector in a flow

  1. Register the ZIP in your tenant, or add a new version if the connector is already installed.
  2. Create or select a credential if the action requires one.
  3. In a Draft flow, add an available action, choose its version, connect it, and map inputs.
  4. Test the step and flow; review output and failures before activation.

See readme.md in the ZIP for settings and limitations.

Version
v0.2.0.1 Choose version
Release
2026-10-03
Package
Implemented source
Schema credentials
Bearer token
Package size
6 KB
SHA-256
325075848ed3b33fc2fdc05ff504b33ee4f4d643d78283a6b1392dc05e6eaad9

Version history

What's new

  1. v0.2.0.1Latest · 2026-10-03 · Implemented source

    Improves action labels, mapping hints and connection groups while retaining the existing parameter keys, types, defaults, credentials and result contracts.

  2. v0.2.0.0Earlier · 2026-10-02 · Implemented source

    Replaces generic HTTP scaffolding with explicit vendor actions and selected credentials.

  3. v0.1.1.0Earlier · 2026-10-02 · Starter scaffold

    Historical package retained unchanged from repository commit f23d25b3ea418842aeabdc0e7bd91d97167da66b.

Included in this version

Included actions

Implemented in v0.2.0.1. Use a separate flow trigger; no webhook trigger is included.

Send channel message

Post a plain-text channel message using delegated ChannelMessage.Send permission.

Reply to channel message

Add a plain-text reply to an existing channel message.

Get channel message

Read a root channel message using ChannelMessage.Read.All permission.

Vendor API

API and access

Implementation considerations
  • Confirm number ownership, region, recording consent, messaging consent, template approval, and webhook signature behavior.
  • Use provider IDs and status callbacks rather than assuming a send or call request completed successfully.
  • Keep communication content, recordings, and transcripts governed by customer retention and deployment policies.
  • Microsoft Teams automation commonly uses Microsoft Graph permissions and tenant-level consent.
  • CXFabric should separate chat, channel, user, calendar, and notification behavior by approved scopes.

Support

Need help with Microsoft Teams?

Tell us what you need to connect or change.