Issue Status Lookup in Teams

Overview

A manual-trigger flow that takes a pasted GitHub issue URL and posts a rich status card to a designated Microsoft Teams channel. The card shows the issue title, OPEN/CLOSED badge (color-coded), opener, current assignee, labels, comment count, and a deep link back to GitHub — so a triage huddle or PM standup can see live issue state without leaving Teams.

Category: Teams · Integration · Developer Productivity

Audience: Developers, Project Managers

Use Case

Engineering and Project Management teams frequently reference GitHub issues during Teams chats — pasting a raw URL leaves the team guessing at current state. This flow converts any https://github.com/{owner}/{repo}/issues/{n} URL into a formatted HTML status card so the team sees real-time state (open/closed), assignee, labels, and comment count with a single click.

The flow is ideal for teams that:

• PM running a triage call pastes an issue URL into the flow's Run panel so the card appears in the triage channel.
• Developer posting a blocker escalation grabs a current snapshot before asking the team for help.
• Release manager validates that a bug reportedly fixed is actually closed.

Flow Architecture

Environment Variables

Connectors & Connections

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Change the repository or Teams destination

Edit the four env vars (flowlibs_GitHubOwner, flowlibs_GitHubRepository, flowlibs_TeamsGroupId, flowlibs_TeamsChannelId) in the target environment — no flow edit required.

Add body/description to the card

Get_Issue_Details already returns body.body (markdown). Insert an additional HTML block in Build_Issue_Card_Html that slices the first ~400 chars of body('Get_Issue_Details')?['body']?['body'] and HTML-escapes it. Note that GitHub issue bodies are markdown; rendering as HTML without conversion yields raw markdown in the Teams card.

Support multiple repos at runtime

Replace the single Init_varGitHubRepository with a parse step that reads the repo name from the pasted URL: split(last(split(first(split(triggerBody()?['text'], '/issues/')), '/repos/')), '/') and a similar expression for the owner. Drop both Init_var* assignments.

Upgrade to a Teams message-extension trigger

Replace the manual Request trigger with Teams OnMessageActionExecuted for a right-click-on-message UX. Parse the issue URL from the selected message body.

Handle private repos with different auth

GitHub connection references can be swapped per environment via solution unpack — no flow edit needed.

Error handling for bad URLs

Wrap Parse_Issue_Number_From_URL in a Scope with a Run-after-failed fallback Compose that posts an Invalid GitHub issue URL card. Currently the flow fails with a runtime error if the URL does not contain

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@int(first(split(first(split(last(split(triggerBody()?['text'], '/issues/')), '#')), '?')))

@if(equals(toLower(string(outputs('Get_Issue_Details')?['body']?['state'])), 'open'), '#2da44e', '#8250df')

@if(greater(length(body('Select_Label_Names')), 0), join(body('Select_Label_Names'), ', '), '(none)')

@coalesce(outputs('Get_Issue_Details')?['body']?['assignee']?['login'], '(unassigned)')

@coalesce(outputs('Get_Issue_Details')?['body']?['html_url'], triggerBody()?['text'])