Pipedrive to ERP Order Sync on Won

Overview

When a Pipedrive deal is won, this flow creates the corresponding sales order in the ERP / finance system (Dataverse) from the deal's value, currency, customer and owner, cross-links the order back into Pipedrive, and emails finance. It keeps sales and finance in lockstep without re-keying won deals.

Status: Built — solution FlowLibs - Pipedrive to ERP Order Sync on Won, flow ships Off (demo). Going live requires only: authorize the three connections, set the env var values, and turn the flow On.

Build note (connector reality): The Pipedrive connector has no native "deal won" trigger and no ListDealProducts / UpdateDeal operations. So a Recurrence poll + status filter replaces the won-trigger, the order is built from the deal header (value/currency/customer/owner) instead of per-line products, and the cross-link back to Pipedrive uses AddActivity (a follow-up task on the deal) instead of UpdateDeal. This keeps the flow 100% connector-first with no HTTP fallbacks and no inline credentials.

Use Case

A sales + finance team wants every won deal to automatically produce a finance order, deduplicated and cross-linked, so finance is notified the moment a deal closes and nobody re-enters orders by hand.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Pipedrive	shared_pipedrive	ListDeals AddActivity
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords CreateRecord
Office 365 Outlook	shared_office365	SendEmailV2

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.

QuickBooks / Xero target

Swap the Create ERP Sales Order Dataverse step for the QuickBooks/Xero connector's create-order action; branch on varOrderTarget to support multiple targets.

Line-item products

The Pipedrive connector exposes no deal-products operation. To carry per-line products/pricing, add a built-in HTTP call to GET /v1/deals/{id}/products (bind the API token to a new flowlibs_ env var) and loop the lines into ERP order lines.

Tax / discount

Extend the order table with tax-code and discount columns and map them through.

Trigger latency

Tighten the Recurrence interval (e.g. every 15 minutes) for near-real-time sync; the dedup ledger keeps it safe at any frequency.

Cross-link richness

AddActivity records the order id on the deal; switch to a Pipedrive note or a custom deal field (via REST) if a non-task cross-link is preferred.

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(body('List_All_Deals')?['data'], createArray())

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

@concat('flowlibs_dealid eq ''', string(items('Apply_To_Each_Won_Deal')?['id']), '''')

@equals(length(coalesce(body('Check_Existing_Order')?['value'], createArray())), 0)

@coalesce(item()?['org_name'], item()?['org_id']?['name'], item()?['person_name'], item()?['person_id']?['name'], 'Unknown')

Customize & download