Pipedrive Lead Inbox to Qualified Deal

Overview

This flow automates lead qualification and routing from the Pipedrive Leads Inbox. On a schedule it reads open leads, scores each new lead against configurable qualification criteria, converts qualified leads into deals on the right pipeline/stage, assigns an owner, logs every lead to a Dataverse ledger (idempotent — no duplicate deals on re-poll), and alerts the sales channel in Microsoft Teams. Low-scoring leads are routed to nurture (logged with a Nurture outcome).

Why it matters: Manual lead triage is slow and inconsistent. Automated scoring + conversion gets qualified leads to a rep fast and keeps the inbox clean, while a Dataverse ledger gives a governed, auditable record of every routing decision.

Status: Built as an Off demo. Going live requires only authorizing the three connections and setting the environment variable values — no logic changes.

Use Case

A sales/marketing team wants inbound Pipedrive leads (web form, chat, import) qualified, converted, assigned, and notified automatically — with nurture for the rest — without a rep watching the Leads Inbox.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Pipedrive	shared_pipedrive	AddDealV2
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.

AI scoring

Replace the Compose scoring with an Azure OpenAI call over the lead notes/source for a richer score.

Territory / round-robin owner

Drive Init Owner User Id from a lookup (region/product) or a rotating counter instead of a single env var.

Nurture sync

Extend the Nurture branch to push low-score leads into Mailchimp / a marketing audience instead of only logging them.

SLA follow-up

Add a downstream flow that alerts a manager if a converted deal isn't actioned within N hours (join on flowlibs_correlationid).

Poll frequency

Change the Recurrence interval to match lead volume.

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.

@add(add(if(greaterOrEquals(int(coalesce(items('Apply_to_each_Lead')?['value']?['amount'],0)),variables('varValueThreshold')),50,10),if(not(equals(coalesce(string(items('Apply_to_each_Lead')?['organization_id']),''),'')),25,0)),if(not(equals(coalesce(string(items('Apply_to_each_Lead')?['person_id']),''),'')),25,0))

@concat('flowlibs_pipedriveleadid eq ''', string(items('Apply_to_each_Lead')?['id']), '''')

@equals(length(body('Check_Existing_Ledger')?['value']), 0)

@greaterOrEquals(outputs('Compute_Lead_Score'), variables('varQualifyThreshold'))

@{concat('user_id=', coalesce(variables('varOwnerUserId'),'0'))}

Customize & download