Google Contacts New Contact to CRM Lead

Overview

This flow turns newly-added Google Contacts into routed CRM leads in Dataverse. On an hourly schedule it reads the full Google Contacts list, detects contacts it has not seen before (via a Dataverse dedup ledger), and for each new contact: creates a CRM lead with a simple score, assigns an owning rep by territory (email-domain -> rep map), creates a first-touch follow-up task, records the contact in the seen-ledger, and notifies the assigned rep in a Teams channel.

Why it matters: Contacts captured in Google often never reach the CRM. Auto-creating scored, owned leads with a first-touch task and a rep notification guarantees follow-up and a governed record of new-contact intake.

Status: Built — ships Off (demo). Going live requires only authorizing the three connections and setting the environment-variable values.

Use Case

Sales/Operations reps add prospects to Google Contacts and the team wants each one in the CRM with an owner, a follow-up task, and a heads-up to the responsible rep — without manual re-entry. The Google Contacts connector has no usable new-contact trigger, so a scheduled diff with a Dataverse dedup ledger provides exactly-once lead creation.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Google Contacts	shared_googlecontacts	PeopleApiListContactsV4
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords CreateRecord
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.

Salesforce / Dynamics target

Swap the three Dataverse CreateRecord actions for the Salesforce connector (CreateRecord / lead object) to write leads into a different CRM.

Dedup against the CRM, not just the ledger

Add a ListRecords on the lead table by email before Create Lead to skip contacts that already exist as customers.

Smarter scoring

Replace the Create Lead flowlibs_leadscore expression with rules over job title, company size, or domain reputation.

Territory routing

Extend flowlibs_TerritoryMap with more domains, or change the territory key from email domain to address region by reading addresses[0].formattedValue.

Poll frequency

Adjust the Recurrence trigger interval; the ledger keeps creation exactly-once regardless of cadence.

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_Contact')?['emailAddresses'])?['value'], ''))}

@{toLower(last(split(outputs('Compose_Primary_Email'),'@')))}

@{coalesce(json(variables('varTerritoryMap'))?[outputs('Compose_Domain')], variables('varDefaultRep'))}

@if(empty(first(items('Apply_to_each_Contact')?['organizations'])), 40, 70)

@concat('flowlibs_contactemail eq ''', outputs('Compose_Primary_Email'), '''') then @equals(length(outputs('Get_Seen_Ledger')?['body/value']), 0)

@{addDays(utcNow(), variables('varDueDays'))}

Customize & download