Google Contacts Enrichment from Email Domain

Overview

Auto-enriches Google Contacts with company context. On an hourly schedule the flow reads every Google contact, infers the organization from the contact's email domain, looks up firmographic details from an enrichment API, finds the matching Dataverse account, and writes the result to a Contact Enrichment ledger table in Dataverse — tagged with a per-run correlation id.

Why it matters: Contacts without company context are hard to segment and route. Domain-based enrichment fills the gaps automatically and produces a governed, queryable record of what was enriched and how confident the match was.

Design note: The Google Contacts connector is read/create only — it has no update-contact operation — so enrichment results are written to a dedicated Dataverse ledger table and linked to the matching account. To physically write company/title back onto the Google contact, add an HTTP call to the Google People API (people.updateContact) with OAuth, noted in the customization guide.

Status: Built (API-first). Ships Off (demo). Flow Checker: 0 errors / 0 warnings.

Use Case

Sales/marketing wants every Google contact tagged with company firmographics and linked to a CRM account, without manual data entry, and with a confidence gate so only high-quality matches are stored.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Google Contacts	shared_googlecontacts	PeopleApiListContactsV4
HHTTP	http	GET enrichment API
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.

Write back to Google

To set company/title on the Google contact itself, add an HTTP PATCH to the Google People API (people.updateContact) with OAuth, since the connector has no update op.

Internal-first matching

Match against an internal account table before calling the paid enrichment API to reduce cost.

Confidence gate

Tune flowlibs_MinConfidence; raise it to store only high-certainty matches.

Cache by domain

The ledger already dedups by email; add a domain-level cache table to avoid re-calling the API for contacts at the same company.

Cadence

Change the Recurrence interval to scan more or less often.

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.

@toLower(coalesce(first(items('Apply_to_each_Google_Contact')?['emailAddresses'])?['value'],'none@none.invalid'))

@if(contains(outputs('Compose_Primary_Email'),'@'),toLower(last(split(outputs('Compose_Primary_Email'),'@'))),'')

@not(contains(split(variables('varFreeDomains'),','), outputs('Compose_Email_Domain')))

@equals(length(coalesce(outputs('Lookup_Existing_Enrichment')?['body/value'],createArray())),0)

@greaterOrEquals(int(coalesce(body('Lookup_Firmographics')?['confidence'],0)),variables('varMinConfidence'))

Customize & download