Connector library

Implemented source AI & Language

Microsoft Bot Framework connector.

Read selected Direct Line API 3.0 conversation activities and send a bounded text message using managed bearer credentials, opaque watermarks and explicit uncertain-send results.

Connector download

Download Microsoft Bot Framework

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.0 Choose version
Release
2026-10-04
Package
Implemented source
Schema credentials
Bearer token
Connection settings
Direct Line Region
Package size
9 KB
SHA-256
dfff7e2408b52d62acd491fb7b9e94b00b77dcd280106f031b13add7b6fcff56

Version history

What's new

  1. v0.2.0.0Latest · 2026-10-04 · Implemented source

    Read selected Direct Line activity batches and send bounded text to an existing conversation with managed bearer credentials.

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

    Historical readable HTTP scaffold.

Included in this version

Included actions

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

List activities

Read one selected activity batch and preserve its opaque watermark.

Send text

Send one text activity to an existing conversation; a checked receipt does not prove a bot reply.

Vendor API

API and access

Implementation considerations
  • Selected activity batches: Read activity IDs, types and bounded text with an opaque watermark.
  • Text activities: Send one bounded message to an existing conversation and return its checked receipt.
  • Caller-managed activity reads; no automatic polling or WebSocket trigger is included.
  • Use managed Direct Line bearer credentials and the bot's configured global, Europe or India endpoint. Conversation creation and token issuance/refresh remain external.
  • A null watermark preserves the input cursor. An empty backlog does not end the conversation. Caller owns cursor persistence, deduplication, pacing and transcript handling.
  • A receipt does not prove a bot reply or business outcome. Failed attempted sends remain unknown and are never replayed; reconcile possible bot-triggered effects before repeating.
  • This package calls the documented REST channel without the retired Bot Framework SDK. No streaming, reconnect, uploads, attachments or arbitrary activity input is included.

Support

Need help with Microsoft Bot Framework?

Tell us what you need to connect or change.