Skip to main content
Upstream connectors put Triage’s diagnostic questions inside the tools requesters already use, starting with Microsoft Teams. This page explains the Intake Gateway that sits between a chat surface and the Triage decision core, the card lifecycle that keeps the diagnostic honest, and the hand-off to composerID. It is written for platform engineers and risk reviewers evaluating an intake surface.
Upstream connectors are Triage’s intake surfaces: where the diagnostic questions are asked and the intent is born. They are never composerID destinations. composerID carries the decision downstream. Each guide describes its route and setup:
  • Microsoft Teams: Personal bot, Adaptive Cards and Microsoft Entra ID SSO. Current development guidance uses the Teams SDK.
  • Slack: Roadmap. Same gateway; the Block Kit renderer ships in the reference implementation.
  • Google Chat: Roadmap. Same gateway; the Cards v2 renderer ships in the reference implementation.
  • ServiceNow: Roadmap. Service Portal and Employee Center widget; the portal route is separate from conversational chat.
  • ServiceNow Chat: Documented integration pattern. Virtual Agent topics, the external Bot Integration API, employee identity and live-agent handoff. Customer setup and tenant acceptance are required.
The destination catalogue lists every downstream system with its coverage status. The surfaces on this page are Triage’s intake, not destinations, so they are not in it.

How it fits together

Nothing about the diagnostic moves into the chat platform. The questions, the scoring, the routing and the audit spine stay where they live today. The Intake Gateway only translates between chat cards and the same decision API the web intake uses. Solid arrows are the forward path. Dashed arrows are the return path: a handoff status, a destination link when available, or an enrichment request. A publish acknowledgement alone does not prove that a destination saved the record.

Three components

Teams app package

A manifest and icons describe the Teams app and its bot. App distribution, installation and Entra permission consent are separate tenant controls. The hosting and identity configuration are agreed during setup.

Intake Gateway

Receives bot activities, verifies the requester through Entra ID SSO, renders questions as Adaptive Cards and translates submissions back into answers. It holds temporary answers, conversation position and the identifiers needed to update messages. Renderer-agnostic: Slack and Google Chat are the same core with a different renderer.

Decision core, unchanged

The gateway calls the same evaluate contract as the web intake. Scoring, routing, anti-gaming pattern detection and Compliance File generation run server-side and are identical wherever the questions were asked.

From first question to published record

Steps 1 to 8 are the upstream connector. From step 9 the flow is standard composerID publishing: the five stages in How integrations work.
1

The requester opens the bot

The requester opens the Triage bot in Teams, or is pointed at it the moment they ask for work in a channel. Where it runs: Teams.
2

Identity is verified

Entra ID SSO reuses the existing sign-in where possible, with consent or a sign-in fallback when required. Contextual data requires separately authorised access. Where it runs: the gateway, against Entra ID.
3

The first question arrives

An Adaptive Card carries the prompt, embedded guidance and choice answers. Where it runs: gateway to Teams.
4

The answer locks

The answer is submitted and the card is replaced in place by its locked state: no inputs remain. Where it runs: the gateway.
5

The next question arrives

One card per question, in fixed order, for however many questions the tenant’s diagnostic defines. Where it runs: gateway to Teams.
6

The decision core scores and routes

On the final answer the gateway hands the complete answer set to the decision core. Scoring and routing produce the channel decision. Where it runs: the Triage decision core.
7

The Intent Record is minted

One traceable Intent ID. The Compliance File records the intake surface and the verified requester identity on the audit spine. Where it runs: the Triage decision core.
8

The completion card is sent

The card shows the outcome and explanation authorised for the requester, together with the intent:// reference. The offline example also displays illustrative confidence. Where it runs: gateway to Teams.
9

composerID preflights and publishes

composerID preflights the intent against the destination’s tenant requirements and publishes it into the system or systems of record, idempotently. Where it runs: composerID.
10

The receipt returns to the thread

The completion card shows the handoff status and an authorised destination link when one is available. Acknowledgement and confirmed record creation remain distinct. If preflight needs a missing field, an enrichment request can return to the thread. Where it runs: composerID to gateway to Teams.

The card lifecycle keeps the diagnostic honest

The intake has deliberate properties, and they are what make the decision defensible. Cards make these properties visible; the gateway must enforce them through server-side validation. Removing a control from the screen is not a security boundary.
One card per message. The next question only arrives after the current one is answered.
After the server accepts the answer, the bot replaces its card with a read-only summary. The gateway also rejects replayed, stale or altered submissions.
Earlier cards are inert text, and the gateway rejects out-of-order or repeated answers.
Runs server-side in the decision core: identical to the web intake, invisible to the surface.
An unfinished reference session does not mint an Intent Record or Compliance File. Temporary gateway state needs an agreed retention policy; messages already posted in Teams remain subject to the customer’s Teams retention settings.

Identity and tenancy

Identity

Validate the incoming activity and obtain the requester identity through the configured Entra authentication flow. SSO can require consent or interactive sign-in. Bind the session to its verified tenant, requester and conversation before accepting answers. The audit record must use that verified identity, not identity fields submitted in a card.

Tenancy

Agree the app catalogue or custom-upload policy, installation scope and Entra permissions separately. The question configuration lives in Triage, not in the package. Changes to app capabilities or permissions can still require an updated package or renewed consent. See the Teams guide for the current setup and Microsoft references.

Where composerID takes over

The trigger: a completed assessment becomes an intent

Triage tells composerID that a decision was made the same way a destination tells it that a record changed: a signed webhook. POST /triggers/triage/{tenant} accepts the completion event, verifies the X-Signature-HMAC-SHA256-1 header against the tenant’s webhook signing key, and mints the intent. The Intent ID is derived from the assessment response id, so if Triage delivers the same completion twice, the second delivery returns the existing intent rather than creating another.
$TENANT and $WEBHOOK_KEY are the tenant and webhook_signing_key from minting sandbox credentials. The answers land in the intent payload through the tenant’s question map, the rank-1 channel becomes payload.channel, and the provenance (response id, score, completion time) is recorded under payload.source, never the diagnostic content itself.
The sandbox reads the completed assessment from the delivery (data.response). A deployment connected to a Triage tenant fetches it by responseId instead, and the delivery need carry only the id. The endpoint reference has the full shapes.
From the moment the Intent ID is minted, the flow is the standard composerID contract: preflight against the destination’s tenant requirements, an idempotent publish keyed {intent_id}-{version}-{destination}, external IDs and a receipt on the timeline, then the webhook and reconciliation contract that keeps the record truthful. Publishing and Events document each stage. Two returns are specific to the chat surface. Update the completion card using its stored message and conversation IDs. Show a destination link when it is returned by the agreed integration route, without treating the link itself as confirmation that the Intent ID was stored. The M and L definitions determine the evidence required for the displayed status.

The enrichment loop

If preflight finds a gap the diagnostic did not cover (a cost centre, a location code), the enrichment_request comes back to the same thread as another card.

Run the reference implementation

The upstream/ package is an offline reference: standard-library Python, no network, with an in-memory gateway and platform card renderers. It tests the state machine and card shapes, not a configured Teams messaging endpoint, live Entra token exchange or customer-tenant delivery. Those are covered by deployment acceptance.
The demo runs a scripted requester through the cards, completes the decision, mints the Intent ID on the spine, stamps a mock SAP Fieldglass tenant and prints the completion card with its deep link. The tests cover locked answers, fixed order, abandonment and the card shapes for every renderer.

Next steps

Microsoft Teams

Teams SDK, Adaptive Card compatibility, Entra ID sign-in and proactive updates.

Destination catalogue

Every downstream system composerID publishes into, with its coverage status.

How integrations work

The five publishing stages that begin once the Intent ID exists.