New GitHub Issue to Teams Notification

Overview

When a new issue is created in a GitHub repository, this flow posts a formatted card to a configured Microsoft Teams channel. The card displays the issue title, labels, assignee, and a direct link to the issue on GitHub.

Use Case

Development teams track GitHub issues but don't want to context-switch to GitHub constantly. This flow keeps the team informed of new work directly in Teams, where they already collaborate, eliminating missed issues and reducing notification fragmentation.

The flow is ideal for teams that:

• New issues instantly visible in Teams — no GitHub polling needed
• Card format includes issue metadata (labels, assignee) at a glance
• Direct link to the issue — one-click jump to GitHub
• Fully configurable trigger — no code changes to re-target repos
• Beginner-friendly — simple action sequence with no complex logic

Flow Architecture

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.

Deploy to another environment

Import the solution, update the GitHub trigger to point to your target repository, update the Teams channel reference in the PostMessageToConversation action, bind connection references (GitHub, Teams), and turn the flow on.

Filter by label

Add a condition on the issue labels array so only priority labels (e.g., 'bug', 'urgent') trigger a Teams post.

Add assignee mention

Use @concat('@', triggerBody()?['issue']?['assignee']?['login']) in the Teams message to @-mention the assigned developer.

Customize card layout

Edit the HTML body in the Teams action to surface more fields — milestone, created date, additional issue URLs.

Multi-channel routing

Add a switch statement to post to different Teams channels based on the issue label (e.g., bug -> #triage, feature -> #roadmap).

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.

@triggerBody()?['issue']?['title']

@triggerBody()?['issue']?['number']

@triggerBody()?['issue']?['html_url']

@triggerBody()?['issue']?['assignee']?['login']

@triggerBody()?['issue']?['labels']