Viva Engage Kudos to HR Recognition Log

Overview

This solution turns informal praise on Viva Engage into governed, reportable recognition data. A 15-minute logger flow reads new posts in a designated praise community, deduplicates them, writes a recognition record to Dataverse, increments a per-recipient running count, and notifies the HR Teams channel. A monthly roll-up flow then publishes a "most appreciated" leaderboard to leadership.

Why it matters: Recognition drives engagement but is invisible to HR when it lives in social posts. Capturing it creates durable data for culture programs, reviews, and leadership visibility.

Build status: Built via the API-first (workflow-table clientdata) path. Both flows ship Off and verify 0 errors / 0 warnings in Flow Checker. Going live requires only authorizing the three connections and setting the environment-variable values.

Use Case

HR wants employee recognition captured and reportable, fed automatically from organic Viva Engage praise — with a per-person tally and a monthly leadership summary, rather than manual tracking.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Viva Engage	shared_yammer	GetMessagesInGroupV3
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords CreateRecord UpdateRecord
Microsoft Teams	shared_teams	PostMessageToConversation

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.

Praise detection

By default every non-system post in flowlibs_VivaPraiseCommunityId counts as a kudos. Set flowlibs_PraiseKeyword (e.g. kudos, shoutout) to only count posts containing that word.

Recipient extraction

Compose RecipientName takes the first @mention in the post body. Adjust this expression to match your praise format.

Polling cadence

Change Flow 1's Recurrence (default 15 min) to trade latency for API calls.

Leaderboard size & cadence

flowlibs_TopRecipientCount controls how many recipients appear; Flow 2's Recurrence controls how often leadership is updated.

Values tagging / rewards

Extend the log table with a company value or reward tier column and stamp it on Create Log Record.

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.

@and(equals(item()?['system_message'], false), contains(toLower(coalesce(item()?['body']?['plain'], item()?['content_excerpt'], '')), toLower(variables('varPraiseKeyword'))))

@concat('flowlibs_messageid eq ''', string(items('For_Each_Kudos')?['id']), '''')

@add(int(coalesce(first(outputs('List_Recipient_Summary')?['body/value'])?['flowlibs_recognitioncount'], 0)), 1)

flowlibs_recognitioncount desc with $top = @int(variables('varTopCount'))

Customize & download