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 inbound Bot Framework JWT (Authorization header) is validated before the pipeline runs. Default false for local development against the Bot Framework Emulator / a private dev tunnel.

public bool ValidateInboundToken { get; set; }

Property Value

Boolean

Remarks:

HARDENING: the current check validates the token's issuer, audience and expiry claims but does NOT yet verify the cryptographic signature against the Bot Framework signing keys (that requires an OpenID/JWKS dependency and the ability to return HTTP 401, which the adapter's HTTP hosting does not expose yet). Enable full signature validation before exposing this endpoint publicly (test-2/prod).

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

Description

public string Description { get; set; }

Property Value

String

Constructors