Microsoft Teams

Posts ticket events to a Teams channel as Adaptive Cards. Connected through the Stoneity bot, it also keeps a thread per ticket, adds Resolve and Assign to me buttons and answers chat commands.

Simple setup: Workflow

1. In Teams, open the channel, choose Workflows → Post to a channel when a webhook request is received (or a legacy Incoming Webhook connector) and copy the generated URL.
2. In Stoneity open Settings → Apps → Marketplace → Microsoft Teams → Install.
3. Paste the URL, choose the events and optionally the boards, then save.
4. Under Installed apps click Test to send a sample card.

This mode only sends. For threads, buttons and commands, connect the bot instead.

Full setup: Stoneity bot

The bot needs the Stoneity Teams app package to be uploaded to your tenant once. Your administrator builds it from the repository (deploy/teams-app/build.sh) and uploads it under Teams admin centre → Manage apps → Upload new app. Nothing in it is workspace specific; every workspace uses the same package and is told apart by the link code below.

1. Install the app in Stoneity, leaving the webhook URL empty. Choose the events, the boards and the board used by the new command.
2. Open Installed apps → Microsoft Teams → Settings and copy the channel link code (for example K7P-3QX).
3. In Teams, add the Stoneity app to the team, then in the channel type:

@Stoneity link K7P-3QX

The bot confirms the connection, the channel name appears in the installation settings, and events start arriving. One installation is connected to one channel; add a second installation for a second channel.

Commands

@Stoneity new Printer on floor 3 is down
@Stoneity INC-1042
@Stoneity help

Notes

• The bot is a single Stoneity-owned Azure Bot registration. If your server does not have it configured, only the Workflow mode is offered.
• Requests from Teams are accepted only with a valid Bot Framework token whose serviceurl matches the activity, and Stoneity only ever calls back Bot Framework addresses.
• Card buttons carry a signature bound to the installation, the ticket and the action, so a copied card cannot act on another workspace.