Pipedrive New Deal Document Generation

Overview

This flow auto-generates a branded quote/proposal document from Pipedrive deal and product data, with no manual document assembly. On a schedule it finds deals that have reached the Proposal stage, merges the deal header fields and product line items into a branded HTML proposal, archives it to SharePoint, attaches it to the Pipedrive deal, and emails it to the deal contact. A Dataverse ledger guarantees each deal is processed only once.

Why it matters: Manual quote creation is slow and inconsistent. Generating proposals from CRM data on stage change keeps them accurate, on-brand, and fast.

Build note: the proposal is composed as branded HTML inside the flow (the Adobe PDF Services DocGen template-file input is not accepted by the API-first authoring path), keeping the flow connector-first (Pipedrive, SharePoint, Outlook, Dataverse) with no premium document dependency and Flow Checker 0 errors / 0 warnings. Swapping in a PDF rendering connector later only requires changing the Compose_Proposal_Html render step; everything around it is unchanged.

Use Case

A sales team wants a branded proposal produced automatically the moment a deal reaches the Proposal stage, stored for the record, attached to the deal, and sent to the customer - without anyone re-keying CRM data into a template.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Pipedrive	shared_pipedrive	ListDeals GetDeal
SharePoint	shared_sharepointonline	CreateFile
Office 365 Outlook	shared_office365	SendEmailV2
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords

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.

Branding

Edit the markup in Compose_Proposal_Html (colors, logo, layout). The accent color is #5b2a86.

PDF output

Replace the archive/attach/email payload with a render step (e.g. a PDF connector) fed by Compose_Proposal_Html; the surrounding wiring is unchanged. flowlibs_ProposalTemplatePath is reserved for a template-based render.

Trigger cadence

Change the Recurrence interval, or pair with a Pipedrive webhook for near-real-time generation.

e-sign / approval

Route the proposal through DocuSign for signature, or gate generation behind a discount approval.

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.

@{concat(coalesce(body('Get_Deal')?['data']?['title'],'Proposal'),'-proposal.html')}

@and(equals(string(item()?['stage_id']), variables('varProposalStageId')), equals(coalesce(item()?['status'],''),'open'))

@equals(length(coalesce(body('Check_Existing')?['value'], json('[]'))), 0)

{ "html": "<tr><td>@{item()?['name']}</td></tr>" }

@{coalesce(body('Get_Deal')?['data']?['person_id']?['email']?[0]?['value'], variables('varRecipientFallback'))}

@{concat(variables('varPipedriveBase'),'/deals/',items('Apply_to_each_Deal')?['id'],'/products?api_token=',variables('varPipedriveToken'))}

Customize & download