FromTeamsBotNodeConfiguration

Namespace: Meshmakers.Octo.MeshAdapter.Nodes.Trigger

Configuration for the FromTeamsBot trigger node — hosts an HTTP endpoint that receives Microsoft Bot Framework activities (the messaging endpoint configured on the Azure Bot resource, e.g. POST /{tenant}/teamsBot). Inbound counterpart of TeamsBotReply@1. Enables bidirectional Teams conversations: employees upload invoices and ask questions in a 1:1 chat with the bot.

public record FromTeamsBotNodeConfiguration : TriggerNodeConfiguration, INodeConfiguration, IEquatable<NodeConfiguration>, ITriggerNodeConfiguration, IEquatable<TriggerNodeConfiguration>, IEquatable<FromTeamsBotNodeConfiguration>

Inheritance Object → NodeConfiguration → TriggerNodeConfiguration → FromTeamsBotNodeConfiguration
Implements INodeConfiguration, IEquatable<NodeConfiguration>, ITriggerNodeConfiguration, IEquatable<TriggerNodeConfiguration>, IEquatable<FromTeamsBotNodeConfiguration>

Remarks:

File attachments are downloaded and normalised into the same EmailData/ AttachmentData shape produced by FromEmail@1/FromMicrosoftGraph@1, so the downstream OCR/AI/document pipeline is channel-agnostic. Channel messages carry SharePoint reference attachments (downloaded via Microsoft Graph using the resolved FromTeamsBotNodeConfiguration.ServerConfiguration); 1:1 chats carry application/vnd.microsoft.teams.file.download.info attachments with a pre-authenticated download URL.

Properties

ServerConfiguration

WellKnownName of the MicrosoftGraphConfiguration global configuration. Its ClientId/ClientSecret double as the bot App ID/secret; its AzureTenantId/ClientId/ClientSecret are used to obtain a Graph token for downloading channel (SharePoint) file attachments.

public string ServerConfiguration { get; set; }

Property Value

String

Route

Relative route of the messaging endpoint (the tenant prefix is added by the adapter). Must match the messaging endpoint configured on the Azure Bot resource. Default /teamsBot.

public string Route { get; set; }

Property Value

String

ValidateInboundToken

When true (the default, AB#5010), the inbound Bot Framework JWT (Authorization header) is fully validated before the pipeline runs: cryptographic signature against the Bot Framework's published signing keys (FromTeamsBotNodeConfiguration.OpenIdMetadataUrl), issuer, audience (the bot App ID) and lifetime. Set to false ONLY for local development against the Bot Framework Emulator, which sends no token — never on a publicly reachable messaging endpoint: without validation anyone who can reach the route can inject documents and query the assistant.

public bool ValidateInboundToken { get; set; }

Property Value

Boolean

BotAppId

Expected audience of the inbound token (the bot App ID). When empty, the resolved configuration's ClientId is used. Only relevant when FromTeamsBotNodeConfiguration.ValidateInboundToken is true.

public string BotAppId { get; set; }

Property Value

String

OpenIdMetadataUrl

OpenID metadata document the Bot Framework signing keys are resolved from. The default is the public-cloud endpoint; override for sovereign clouds (e.g. Azure Government) or tests. Only relevant when FromTeamsBotNodeConfiguration.ValidateInboundToken is true.

public string OpenIdMetadataUrl { get; set; }

Property Value

String

ValidTokenIssuers

Accepted token issuers. Empty = the Bot Framework public-cloud issuer (https://api.botframework.com). Override together with FromTeamsBotNodeConfiguration.OpenIdMetadataUrl for sovereign clouds. Only relevant when FromTeamsBotNodeConfiguration.ValidateInboundToken is true.

public String[] ValidTokenIssuers { get; set; }

Property Value

String[]

CallerBinding

public CallerBindingMode CallerBinding { get; set; }

Property Value

CallerBindingMode

Description

public string Description { get; set; }

Property Value

String

Constructors