Pipedrive Deal Stage Automation

Overview

This flow keeps a Pipedrive sales pipeline mirrored and acted upon inside Microsoft 365. On a schedule it reads every deal, mirrors each one into a Dataverse pipeline-mirror table, posts a Teams notice whenever a deal moves to a new stage, hands off won deals (creates a Pipedrive onboarding activity and emails the delivery team), and flags stuck open deals (no activity past a configurable threshold) to the sales manager by email.

Why it matters: Deals stall in silence and won deals lose momentum at handoff. The Dataverse mirror gives a governed, queryable record of pipeline state and — by comparing the stored stage to the live stage — lets the flow detect real stage moves without any change trigger.

Status: Off (demo). Going live requires only authorizing the connections and setting the three env var values.

Use Case

A sales team on Pipedrive wants (1) stage changes surfaced to the account team in Teams, (2) a clean automatic handoff to delivery when a deal is won, and (3) manager visibility on stagnant deals — all without manual data entry, and with a Dataverse copy of the pipeline for reporting.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Pipedrive	shared_pipedrive	ListStages ListDeals AddActivity
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords CreateRecord UpdateRecord
Microsoft Teams	shared_teams	PostMessageToConversation
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.

Sync cadence

Change the Recurrence Every Hour interval to match your pipeline velocity.

Stage-specific actions

Extend Condition Stage Changed with a Switch on stage name (e.g. send a quote template when a deal reaches Proposal).

Stuck threshold & recipients

Edit varStuckThresholdDays, varSalesManagerEmail, varDeliveryTeamEmail.

Lost-deal handling

Add a Condition Deal Lost branch to capture lost reasons into the mirror table for win/loss reporting.

Forecast roll-up

Aggregate open-deal value from the mirror table for a weekly Teams forecast post.

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.

@equals(toLower(coalesce(items('Apply_to_each_Deal')?['status'],'')), 'won')

@not(equals(string(outputs('Compose_Previous_Stage_Id')), string(items('Apply_to_each_Deal')?['stage_id'])))

@and(equals(toLower(coalesce(items('Apply_to_each_Deal')?['status'],'')),'open'), less(coalesce(items('Apply_to_each_Deal')?['last_activity_date'],'1900-01-01'), formatDateTime(addDays(utcNow(), mul(-1, variables('varStuckThresholdDays'))),'yyyy-MM-dd')))

@coalesce(items('Apply_to_each_Deal')?['user_id']?['name'], items('Apply_to_each_Deal')?['owner_name'], 'Unknown')

flowlibs_dealid eq '<deal id>'

Customize & download