Translator Meeting Minutes Distribution

Overview

This flow translates a meeting's minutes into each attendee's preferred language using Microsoft Translator V3, generates a per-language Word document from a template, and emails each attendee their localized copy with the document attached. Every delivery is logged to Dataverse and the source record is marked Distributed. In multilingual meetings, a single-language record leaves some participants guessing; automated, per-attendee localized minutes ensure everyone gets an accurate, fluent record of decisions and action items.

Use Case

A team with multilingual participants records meeting minutes once (in any source language) into a Dataverse table. When the record is created, the flow looks up the attendee roster, translates the minutes into each attendee's preferred language, produces a branded Word document per language, and emails each person their own version, then logs the run for audit.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Microsoft Dataverse	shared_commondataserviceforapps	SubscribeWebhookTrigger ListRecords CreateRecord UpdateRecord
Microsoft Translator	shared_microsofttranslatorv	Translate
Word Online (Business)	shared_wordonlinebusiness	CreateFileItem
Office 365 Outlook

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.

De-duplicate languages

To translate once per unique language instead of once per attendee, build a distinct-language list and group attendees by language before the loop.

Source minutes from a document

Swap the minutestext column for a SharePoint/Word GetFileContent read if minutes live in a file rather than a Dataverse field.

PDF output

Follow the Word populate with Word Online GetFilePDF to email an immutable PDF instead of a .docx.

Action items

Parse and translate action items, then create Planner tasks per owner.

Trigger on status change

Switch the trigger to Update with filteringattributes = flowlibs_status to fire only when a row is marked Ready, rather than on every Create.

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.

@coalesce(triggerOutputs()?['body/flowlibs_correlationid'], guid())

@concat('flowlibs_meetingkey eq ''', variables('varMeetingKey'), '''')

@first(body('Translate_Minutes'))?['TranslatedText']

@coalesce(triggerOutputs()?['body/flowlibs_sourcelanguage'], parameters('EnvVar_MinutesSourceLanguage'))

Customize & download