Translator Localized SMS Notifications

Overview

FlowLibs - Translator Localized SMS Notifications is a reusable, HTTP-callable cloud flow. Other flows or apps POST a recipient business key plus a message, and this flow looks up the recipient's preferred language in Dataverse, translates the message with Microsoft Translator V3, sends it via Twilio SMS, logs the send to a Dataverse audit table, and returns a JSON response to the caller.

Why it matters: A single-language SMS underperforms with international customers. Centralizing localization in one shared service means every appointment, delivery, or alert notification reaches each customer in their own language without each calling flow re-implementing translation logic.

Ships Off - going live requires only authorizing the three connections and setting environment-variable values.

Use Case

A business runs many notification flows (appointments, deliveries, OTPs, alerts). Rather than each flow handling translation and SMS itself, they call this one endpoint with a contact key and the English message. The service resolves the contact's language, translates, sends, and logs - returning sent (200) or contact_not_found (404) with a correlation id for tracing.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Microsoft Translator	shared_microsofttranslatorv	Translate
Twilio	shared_twilio	SendMessage
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords CreateRecord

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.

Length guard

Add a Condition that warns or splits when a translated message exceeds the SMS segment limit (translations often expand vs English).

Glossary / brand terms

Wrap protected terms or set Translator category to keep brand names untranslated.

Channel fallback

If a contact has no mobile number, branch to email instead of returning 404.

Opt-out enforcement

Check flowlibs_optstatus before sending and skip non-consented contacts.

Production hardening

Secure the trigger URL (it's an open HTTP endpoint) and consider rate limiting at the caller.

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(triggerBody()?['sourceLanguage'], parameters('EnvVar_DefaultSourceLanguage'))

@coalesce(outputs('Compose_First_Contact')?['flowlibs_languagecode'], variables('varFallbackLanguage'))

@coalesce(first(body('Translate_Message'))?['TranslatedText'], triggerBody()?['messageText'])

@not(equals(variables('varPhone'), ''))

@coalesce(body('Send_Localized_SMS')?['sid'], body('Send_Localized_SMS')?['Sid'], '')

Customize & download