Auto-Route Issue by Label

Overview

This flow automatically watches a GitHub repository for newly opened issues, reads their labels, and posts a formatted notification to the appropriate Microsoft Teams channel based on label-driven routing rules. It keeps triage lean by surfacing bugs, security issues, and documentation gaps to the right specialist channels — and everything else goes to a generic triage channel so nothing is lost.

Use Case

Engineering teams often struggle with noisy GitHub notifications: the "everything feed" in Teams or email buries high-signal issues under low-priority chatter. This flow lets a GitHub admin wire up label-based triage once, then lets the responsible channels own their queues. Bug reports land in the dev channel. Security findings route to the security response team. Doc issues drop into the documentation channel. Unlabeled issues go to triage so someone can apply the right label and restart the routing.

The flow is ideal for teams that:

• Reduce noise in shared dev channels by routing issues to specialist channels.
• Ensure security-labeled issues always reach the security team first.
• Catch unlabeled issues in a dedicated triage channel rather than dropping them.
• Decouple routing rules from channel ownership — each team owns its queue.

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.

Add or rename routing labels

Edit the Compose Route Key expression to match your label vocabulary (e.g. defect instead of bug).

Add new routing buckets

Duplicate an existing case in the Switch and add a new flowlibs_Teams<Name>ChannelId env var to map a fresh label to its own channel.

Adjust priority ordering

Re-order the nested if() calls in Compose Route Key if your team's priority differs from security → bug → docs.

Change polling interval

Edit the trigger recurrence block. Faster polling gives near-real-time routing but increases API consumption.

Replace message templates

The Teams HTML body strings inside each Switch case are independent — give each channel its own style without affecting others.

Fan-out instead of route

Replace the Switch with parallel Condition branches if an issue labeled both bug and security should notify both channels.

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.

triggerOutputs()?['body/number']

item()?['name']

if(contains(body('Select_Label_Names'), 'security'), 'security', if(contains(body('Select_Label_Names'), 'bug'), 'bug', if(contains(body('Select_Label_Names'), 'docs'), 'docs', 'triage')))

concat('https://github.com/', variables('varRepoOwner'), '/', variables('varRepoName'), '/issues/', triggerOutputs()?['body/number'])