Why Outline instead of just leaving it in Pipedrive?

Pipedrive is built to manage pipeline, not to be read as reference. Outline is where the team searches for how something was done, so a won-deal page there gets found by the next rep, where a CRM record doesn't.

Does it update the page if the deal changes after closing?

Not by default; it writes once per deal. If you want post-close edits reflected, match on the deal ID and call update_document instead of creating a second page.

PipedriveOutline

Log won Pipedrive deals to Outline

A Pipedrive + Outline agent flow

A deal closes in Pipedrive and the knowledge that made it close, the objections, the pricing, who championed it, lives in the sales rep's head and a few activity notes nobody else reads. The next rep working a similar account starts from zero. This recipe turns each closed deal into a durable entry in Outline, the wiki the team actually reads, so won deals become a searchable record instead of rows in a CRM. Your agent lists deals filtered to recently won, reads the value, owner, and close date, and calls create_document to drop a structured page into the right collection, one per deal, with a link back to Pipedrive. Pipedrive answers on request, so the agent runs on a cadence, daily or weekly, finds the deals won since last time, and writes a document for each.

The flow

Pipedrivedeals_list

List deals with pagination and filtering options.

Outlinecreate_document

Creates a new document.

Step by step

Filter to the deals worth recording
Tell the agent to list deals filtered to a won status and a recent window, and point it at one Outline collection like 'Won Deals'. You usually don't want open or lost deals cluttering the wiki.
Read the deal detail
The agent calls deals_list with that filter and pages through. For each deal it can call deals_get and notes_list to pull the value, owner, close date, and the activity notes that explain how it closed.
Write the Outline document
It calls create_document in the target collection with a title like the company name plus the close date, a body summarizing value, owner, timeline, and key notes, and a link back to the Pipedrive deal.
Track what's already written
Store each Pipedrive deal ID against the Outline document it created. Next run the agent skips deals that already have a page, so a re-run doesn't write the same deal twice.

Tell your agent

Every Monday, list Pipedrive deals marked won in the last seven days. For each one without an existing Outline document, create a document in the 'Won Deals' collection titled with the company name and close date, summarizing the deal value, owner, timeline, and the key activity notes, with a link to the Pipedrive deal. Don't rewrite deals you've already logged.

Setup

This flow needs both servers connected to your agent. Follow each install guide:

Pipedrive install guide Outline install guide

Worth knowing

create_document needs the Outline collection ID, not the collection name. Resolve it once with list_collections and reuse the ID for every write.
deals_list paginates and filters, but the deal record alone won't carry the notes that explain the win. The agent has to follow up with notes_list or deals_list_updates per deal to get the narrative worth writing down.
Pipedrive amounts come back in the deal's currency as a number, so a value of 50000 is fifty thousand units of that currency, not cents. Render the currency alongside the figure so the wiki entry isn't ambiguous.

Questions

Why Outline instead of just leaving it in Pipedrive?: Pipedrive is built to manage pipeline, not to be read as reference. Outline is where the team searches for how something was done, so a won-deal page there gets found by the next rep, where a CRM record doesn't.
Does it update the page if the deal changes after closing?: Not by default; it writes once per deal. If you want post-close edits reflected, match on the deal ID and call update_document instead of creating a second page.