Start free
Read & reportControlled changes

See your Pipedrive numbers in Claude.

Explore people, companies, leads, products and deal history beside sales reports. Changes you can allow for teammates and AI tools: field updates, new records, owner changes, notes, activities, deal stages, won or lost status and deletes. Allowed changes apply right away and are recorded in history.

  • Pipeline, deals and owners in a sheet that refreshes itself
  • A weekly sales report without rebuilding it in Pipedrive
  • Clean up names and titles from Datapipe, recorded in history
PipedriveClaudeClaude

Start free Connect Pipedrive

Updated November 2026

Pipedrive reportSample data
Deal value and currencyArchived deals and leadsProducts and prices
Northwind renewalNorthwind renewal$80.00
Acme expansionAcme expansion$125.50
Harbor pilotHarbor pilot$42.00
Refreshes on your schedule in Claude

Who uses Datapipe with Pipedrive

Sales leaders

Review pipeline by stage and owner every Monday without exporting.

Revenue operations

Spot messy records in a report and fix them without handing out admin access.

Agencies

Show clients which campaigns turned into deals.

What you can do with Pipedrive

Read and report

Read sixteen additional datasets for current and archived deals/leads, people, organizations, activities, products, pipelines, stages, field definitions and one deal's field-change history.

  • Pipedrive deals
  • Deals inventory (v2)
  • Archived deals
  • People
  • and 13 more

Explore metrics and dimensions

Controlled changes

  • Update contact name
  • Update company name
  • Update deal title
  • Update any approved person field
  • Update any approved organization field
  • Update any approved deal field
  • Create a person
  • Create a organization
  • Create a deal
  • Assign a person to another owner
  • Assign a organization to another owner
  • Assign a deal to another owner
  • Add a note to a person
  • Add a note to a organization
  • Add a note to a deal
  • Schedule an activity on a person
  • Schedule an activity on a organization
  • Schedule an activity on a deal
  • Delete a person
  • Delete a organization
  • Delete a deal
  • Move a deal to another stage
  • Mark a deal won, lost or open

Changes stay off until you allow them. Allowed changes apply to Pipedrive right away, and history keeps the values before and after.

See what you can change

Full read details

The original updated-deal report now uses the current v2 endpoint; amounts retain record currency and custom values stay JSON.

Examples for your team

Read & report

Review the work behind your pipeline

Compare linked activity IDs, due dates and completion flags with current deal stages.

  1. Scheduled refresh
  2. Latest Pipedrive data
  3. Updated report

Limit: Current inventory does not reconstruct last month's pipeline state.

Read & report

Understand the account's custom fields

Read field codes, types, options and compound subfields before interpreting custom values.

  1. Scheduled refresh
  2. Latest Pipedrive data
  3. Updated report

Limit: Private definitions load through the connected account and stay out of public pages.

Read & report

Prepare the deal review

Refresh the deal report before the sales meeting.

  1. Scheduled refresh
  2. Latest Pipedrive data
  3. Updated report

Limit: Keep the source's deal names and values visible in the shared reporting destination.

Controlled change

Make a deal title easier to recognize

A teammate sets a clearer title on an existing deal in Pipedrive.

  1. Allowed
  2. Applied
  3. Recorded

Limit: History keeps the old title.

Fix things in Pipedrive without opening it

Spot it, fix it

See the problem in your report, then make the fix in Datapipe instead of opening Pipedrive, finding the record and retyping it.

More people can help

Teammates and AI tools you allow can make changes without getting edit access to Pipedrive.

You decide what can change

Changes stay off until you allow them. Every change is recorded with who made it and the values before and after.

Jobs you can stop doing by hand in Pipedrive

Update contact name

  • Fix contact names from web forms

    TodayFind people saved as "avery CHEN" or "AVERY" and retype each name in Pipedrive.

    With DatapipeSort the people report by name to find them. Fix the name for each from Datapipe. Email, phone and owner stay unchanged.

  • Remove job titles typed into names

    TodayOpen contacts named "Avery Chen (CEO)" and delete the extra text by hand.

    With DatapipeChatGPT reads the people report and cleans up the names in Pipedrive.

Exactly what this can change

Renames an existing contact. Pipedrive automations may react. Email, phone, owner, organization and marketing status are unchanged.

Supported fields: Contact name.

Update company name

  • Match company names to legal names

    TodaySearch organizations for "acme" and "ACME Corp." and retype each name to match the contract.

    With DatapipeSort the organizations report by name to spot the variants. Fix the name per organization from Datapipe.

  • Rename an organization after a rebrand

    TodayHear a customer rebranded, find the organization and update its name before the next pipeline review.

    With DatapipeJordan sets the new name. Linked contacts, labels and address stay unchanged.

Exactly what this can change

Renames an existing organization. Pipedrive automations may react. Ownership, address, labels and linked contacts are unchanged.

Supported fields: Company name.

Update deal title

  • Rename deals to one format

    TodayRename deals by hand so pipeline reviews read "Company · Product · Quarter".

    With DatapipeRename them from the deals report. Value, stage and owner stay unchanged, and each old title stays in history.

  • Replace placeholder deal titles

    TodayFind deals still titled "New deal" or "Avery Chen deal" and type a real title before the pipeline review.

    With DatapipeSort the deals report by title. ChatGPT writes a title from each deal's organization.

Exactly what this can change

Renames an existing deal. Pipedrive automations may react. Value, pipeline, stage, status, owner and associations are unchanged.

Supported fields: Deal title.

Update any approved person field

  • Fill in a custom lead source field

    TodayOpen each person who came from a webinar and pick the source from a custom option field.

    With DatapipeChatGPT matches your webinar sign-ups to the people report and sets the source for each person. Each change is recorded with the before and after values.

  • Link people to the right organization

    TodayFind people saved without an organization and attach each one by hand.

    With DatapipeSet the organization ID for each person from the people report. History shows the old and new organization.

Exactly what this can change

Changes the person fields the owner selects, including custom text, number, date and single-option fields and the linked organization. Pipedrive automations may react. Owner has its own action; email, phone, labels and marketing status are not changed.

The owner, an admin or a project manager picks the supported writable fields for this action before anyone can make changes.

Update any approved organization field

  • Record the industry on new organizations

    TodayLook up each company and choose its industry in a custom field.

    With DatapipeChatGPT reads the organizations report and picks an industry option for each.

  • Set a custom renewal date on customer accounts

    TodayCopy the renewal date from the contract into each organization.

    With DatapipeA teammate sets the date on each organization. History keeps the before and after values.

Exactly what this can change

Changes the organization fields the owner selects, including custom text, number, date and single-option fields. Pipedrive automations may react. Owner has its own action; email, phone, labels and marketing status are not changed.

The owner, an admin or a project manager picks the supported writable fields for this action before anyone can make changes.

Update any approved deal field

  • Correct a deal value after a revised quote

    TodayOpen the deal and retype the value and expected close date when the quote changes.

    With DatapipeChange the value and close date together in one update. History keeps the old and new numbers.

  • Push out close dates that already passed

    TodayFilter for overdue deals and edit each expected close date before the forecast call.

    With DatapipeSort the deals report by close date. ChatGPT sets a new date for each, and every change is recorded in history.

Exactly what this can change

Changes the deal fields the owner selects, including custom text, number, date and single-option fields, value, currency, probability, expected close date and the linked person or organization. Pipedrive automations may react. Owner, stage and won or lost status have their own actions; email, phone, labels and marketing status are not changed.

The owner, an admin or a project manager picks the supported writable fields for this action before anyone can make changes.

Create a person

  • Add a contact met at an event

    TodayType the person's name and company from a badge scan into Pipedrive.

    With DatapipeA teammate creates the new person with the fields the owner allowed. Every value is recorded in history.

  • Add a billing contact a customer emailed you

    TodayCopy the name from the message into a new person record.

    With DatapipeChatGPT creates the new person from the details you paste.

Exactly what this can change

Creates one new person with the fields the owner selects. A name is required. It belongs to the connected Pipedrive user, and Pipedrive automations may react. It can be removed later with the delete action or in Pipedrive.

The owner, an admin or a project manager picks the supported writable fields for this action before anyone can make changes.

Create a organization

  • Create an organization for a new customer

    TodayOpen Pipedrive and add the company before the first deal.

    With DatapipeCreate the new organization with its name and allowed fields. It belongs to the connected user.

  • Add a partner company before a shared deal

    TodayAsk someone with access to set up the partner organization.

    With DatapipeA teammate creates the organization from Datapipe.

Exactly what this can change

Creates one new organization with the fields the owner selects. A name is required. It belongs to the connected Pipedrive user, and Pipedrive automations may react. It can be removed later with the delete action or in Pipedrive.

The owner, an admin or a project manager picks the supported writable fields for this action before anyone can make changes.

Create a deal

  • Open a renewal deal ahead of time

    TodayRemember to create next year's renewal with the right value and stage.

    With DatapipeYour subscription report shows renewals coming up. Create the deal with title, value and starting stage from Datapipe.

  • Log an upsell a rep mentioned in a meeting

    TodayWait for the rep to find time to enter the deal.

    With DatapipeA teammate creates the deal from the meeting notes. History shows who added it and with what value and stage.

Exactly what this can change

Creates one new deal with the fields the owner selects. A title is required, and the owner can allow a starting stage. It belongs to the connected Pipedrive user, and Pipedrive automations may react. It can be removed later with the delete action or in Pipedrive.

The owner, an admin or a project manager picks the supported writable fields for this action before anyone can make changes.

Assign a person to another owner

  • Hand a rep's contacts to a teammate before leave

    TodayOpen each person and change the owner while the rep is away.

    With DatapipeSet the new owner for each person from the people report. Each handover is recorded in history.

  • Route a new contact to the rep for their region

    TodayLook up the region and reassign the person by hand.

    With DatapipeChatGPT reads the person's country and assigns the right rep as owner.

Exactly what this can change

Makes another active Pipedrive user the owner of one person. The new owner may get a Pipedrive notification, and automations may react. Nothing else on the person changes.

Supported fields: New owner's Pipedrive user ID.

Assign a organization to another owner

  • Move accounts to a new account manager

    TodayReassign each organization by hand after a territory change.

    With DatapipeSet the new owner for each organization. Nothing else on the organization changes.

  • Give an inbound company to the rep who booked the call

    TodayCheck the calendar and change the organization owner.

    With DatapipeA teammate assigns the rep as owner from Datapipe.

Exactly what this can change

Makes another active Pipedrive user the owner of one organization. The new owner may get a Pipedrive notification, and automations may react. Nothing else on the organization changes.

Supported fields: New owner's Pipedrive user ID.

Assign a deal to another owner

  • Reassign deals when a rep leaves

    TodayFilter the leaver's open deals and change each owner.

    With DatapipeSort the deals report by owner. Reassign each open deal from Datapipe.

  • Hand a large deal to a senior rep

    TodayOpen the deal and change the owner after the pipeline review.

    With DatapipeJordan assigns the senior rep as owner. Value and stage stay the same.

Exactly what this can change

Makes another active Pipedrive user the owner of one deal. The new owner may get a Pipedrive notification, and automations may react. Nothing else on the deal changes.

Supported fields: New owner's Pipedrive user ID.

Add a note to a person

  • Log what a contact said on a call

    TodayOpen the person after the call and type a note.

    With DatapipeAdd a note with the call summary to that person. It appears on their timeline.

  • Record a contact's preferences

    TodayRemember to write down that someone prefers email in the mornings.

    With DatapipeChatGPT drafts the note from your message and adds it in Pipedrive.

Exactly what this can change

Adds one note to an existing person, written as the connected Pipedrive user. Teammates who follow the person may see it in their updates. The person itself is unchanged.

Supported fields: Note.

Add a note to a organization

  • Note a change at a customer company

    TodayOpen the organization and type what changed after you hear news.

    With DatapipeA teammate adds the note to the organization. History keeps the exact text.

  • Leave context for the next account manager

    TodayWrite a handover note on each organization before a reassignment.

    With DatapipeChatGPT writes a handover note on each organization from its deals.

Exactly what this can change

Adds one note to an existing organization, written as the connected Pipedrive user. Teammates who follow the organization may see it in their updates. The organization itself is unchanged.

Supported fields: Note.

Add a note to a deal

  • Write down the next step after a demo

    TodayOpen the deal and type the next step before you forget.

    With DatapipeAdd the note to the deal from Datapipe right after the demo.

  • Record why a quote changed

    TodayAdd a note to the deal explaining the new price.

    With DatapipeA teammate adds the note from Datapipe. The deal's value stays as it is.

Exactly what this can change

Adds one note to an existing deal, written as the connected Pipedrive user. Teammates who follow the deal may see it in their updates. The deal itself is unchanged.

Supported fields: Note.

Schedule an activity on a person

  • Schedule a follow-up call with a contact

    TodayOpen the person and add a call activity for next week.

    With DatapipeAdd a call with a subject and due date to the person. It appears in the connected user's activities.

  • Book a check-in after onboarding

    TodayRemember to add a meeting activity for each new customer contact.

    With DatapipeChatGPT adds one meeting activity per new contact from your onboarding report.

Exactly what this can change

Adds one activity, such as a call, meeting or task, linked to an existing person and assigned to the connected Pipedrive user. Datapipe adds no attendees, so nobody gets an invitation; reminders follow that user's Pipedrive settings. The person itself is unchanged.

Supported fields: Subject, Activity type key, for example call or meeting, Due date, Note.

Schedule an activity on a organization

  • Plan a quarterly review with a customer

    TodayAdd a meeting activity to the organization each quarter.

    With DatapipeAdd the meeting with a due date to the organization from Datapipe.

  • Remind yourself to send a renewal reminder

    TodayCreate a task activity on the organization before renewal.

    With DatapipeA teammate adds the task with a due date. Nobody is invited.

Exactly what this can change

Adds one activity, such as a call, meeting or task, linked to an existing organization and assigned to the connected Pipedrive user. Datapipe adds no attendees, so nobody gets an invitation; reminders follow that user's Pipedrive settings. The organization itself is unchanged.

Supported fields: Subject, Activity type key, for example call or meeting, Due date, Note.

Schedule an activity on a deal

  • Set the next step on a stalled deal

    TodayOpen each deal with no planned activity and add a call.

    With DatapipeSort the deals report by last activity. ChatGPT adds a call to each stalled deal.

  • Add a contract review task

    TodayCreate a task on the deal for legal review.

    With DatapipeAdd the task with subject and due date to the deal from Datapipe.

Exactly what this can change

Adds one activity, such as a call, meeting or task, linked to an existing deal and assigned to the connected Pipedrive user. Datapipe adds no attendees, so nobody gets an invitation; reminders follow that user's Pipedrive settings. The deal itself is unchanged.

Supported fields: Subject, Activity type key, for example call or meeting, Due date, Note.

Delete a person

  • Remove test contacts created during setup

    TodaySearch for test people and delete each one in Pipedrive.

    With DatapipeDelete each test person from the people report. Pipedrive keeps deleted items for 30 days, then removes them.

  • Delete a duplicate contact after copying its details

    TodayCopy the useful details to the main person, then delete the extra one.

    With DatapipeUpdate the main person first, then delete the duplicate as a separate change.

Exactly what this can change

Deletes one person. Pipedrive marks it deleted and removes it for good after 30 days; Datapipe can't restore it. Linked records are handled as Pipedrive decides.

Supported fields: Delete.

Delete a organization

  • Delete a test organization

    TodayFind the organization made while testing and delete it.

    With DatapipeCheck its linked records, then delete that organization from Datapipe.

  • Remove a duplicate company record

    TodayMove deals to the main organization, then delete the extra one.

    With DatapipeA teammate deletes it once the deals are moved.

Exactly what this can change

Deletes one organization. Pipedrive marks it deleted and removes it for good after 30 days; Datapipe can't restore it. Linked records are handled as Pipedrive decides.

Supported fields: Delete.

Delete a deal

  • Delete a deal created by mistake

    TodayOpen the deal and delete it before it skews the forecast.

    With DatapipeDelete the deal from Datapipe. Pipedrive removes it for good after 30 days.

  • Clean out test deals after a demo

    TodaySearch for deals named "Test" and delete each one.

    With DatapipeSort the deals report by title to find them, then delete each one from Datapipe.

Exactly what this can change

Deletes one deal. Pipedrive marks it deleted and removes it for good after 30 days; Datapipe can't restore it. Linked records are handled as Pipedrive decides.

Supported fields: Delete.

Move a deal to another stage

  • Move a deal forward after a successful demo

    TodayOpen the deal and drag it to the next stage.

    With DatapipeA teammate moves the deal to the next stage. Value and owner stay the same.

  • Move stalled deals back a stage

    TodayReview the pipeline and step back each deal that hasn't moved in a month.

    With DatapipeSort the deals report by last stage change. ChatGPT moves each one back a stage, and history keeps the old stage.

Exactly what this can change

Moves one deal to a different stage, which can also move it to another pipeline. Pipedrive automations may react. Value, owner and won or lost status are unchanged.

The owner, an admin or a project manager picks the supported writable fields for this action before anyone can make changes.

Mark a deal won, lost or open

  • Mark a deal won when the contract is signed

    TodayOpen the deal and click Won once the signed contract arrives.

    With DatapipeA teammate marks that deal Won. Pipedrive's win rate updates.

  • Mark a lost deal with the reason

    TodayClick Lost and type why the customer chose someone else.

    With DatapipeMark it Lost with the reason from your call notes. The reason stays on the deal.

Exactly what this can change

Marks one deal as won or lost, or opens it again. This changes win rates and revenue figures in Pipedrive, and automations may react. Stage, value and owner are unchanged.

Supported fields: Status, Lost reason (only when marking lost).

Recorded changeExample

PipedriveUpdate contact nameContact · Avery Chen · made by Jordan Blake

FieldBeforeAfter
Contact nameavery CHENAvery Chen

Applied to PipedriveRecorded in Changes history

You control who can change what

  1. A change is allowed for this data source
  2. A teammate or AI tool makes it
  3. It applies right away, or waits for approval if you set that
  4. Recorded with the values before and after

Source changes are managed on the Changes page in Datapipe. Approval is optional: set it for risky changes, for every change, or for one person. AI tools such as ChatGPT can never widen their own access. Who can turn this on?

Provider rules and limits

Provider permissions still apply, and automations in Pipedrive may react to changes.

Only fields supported by an allowed action can be changed; for some actions the owner, an admin or a project manager also picks the individual writable fields.

Before you connect

What you need

An API key or token from your Pipedrive account.

Read and write

Read access for reports. The 23 change actions need edit access in Pipedrive and stay off until the owner, an admin or a project manager allows them.

Limits and exclusions

Current inventories ignore report dates and do not reconstruct historical pipeline state. Custom values, price entries and field options stay JSON; typed custom columns are not included.

Full details and limits

Sixteen additional reports join the original updated-deal report, which now uses the current supported service. Current inventories ignore report dates and do not reconstruct historical pipeline state. A selected deal's change report returns provider-available field history, without filtering by report dates or promising a complete account audit log. Amounts retain record currency; probabilities and tax retain percentage points. Custom values, price entries and field options stay JSON; typed custom columns are not included. Visibility, plan and read permissions apply; expanded reports may require reconnecting with additional read access. Optional deal, person and organization name changes remain separate: each action stays off until it is allowed for this data source, and every change is recorded in history.

Reports you can build

17 reporting datasets, each with its own fields. Pick one in the app, then choose your columns.

What each dataset reports
  • Pipedrive deals

    Deals and their value.

  • Deals inventory (v2)

    Current accessible CRM inventory, independent of report dates; it does not reconstruct historical state. Visibility, read permissions and provider plans apply. IDs remain strings, missing values remain null and collections stay JSON. Amounts retain the record currency; totals across currencies must not be added without conversion. Recurring revenue and contract values require an eligible plan and can be null. Non-archived deals. Unlike the original updated-deal report, dates do not filter this inventory. Custom fields stay provider-returned JSON; typed per-account columns are not included.

  • Archived deals

    Current accessible CRM inventory, independent of report dates; it does not reconstruct historical state. Visibility, read permissions and provider plans apply. IDs remain strings, missing values remain null and collections stay JSON. Amounts retain the record currency; totals across currencies must not be added without conversion. Recurring revenue and contract values require an eligible plan and can be null. Archived deals use their dedicated endpoint, separate from active inventory. Archive access does not recover deleted records.

  • People

    Current accessible CRM inventory, independent of report dates; it does not reconstruct historical state. Visibility, read permissions and provider plans apply. IDs remain strings, missing values remain null and collections stay JSON. Emails, phone numbers, labels and custom values remain collections. Contact-sync-only fields may be unavailable; no contacts are edited by this read.

  • Organizations

    Current accessible CRM inventory, independent of report dates; it does not reconstruct historical state. Visibility, read permissions and provider plans apply. IDs remain strings, missing values remain null and collections stay JSON. Address and labels retain their native structure. Deal/activity counts are requested explicitly; organization annual-revenue currency is not inferred.

  • Activities

    Current accessible CRM inventory, independent of report dates; it does not reconstruct historical state. Visibility, read permissions and provider plans apply. IDs remain strings, missing values remain null and collections stay JSON. Read due dates, native time-of-day/duration strings, completion time and linked CRM IDs. Due time and duration are not converted to timestamps or numeric hours. This does not schedule or complete an activity.

  • Products

    Current accessible CRM inventory, independent of report dates; it does not reconstruct historical state. Visibility, read permissions and provider plans apply. IDs remain strings, missing values remain null and collections stay JSON. Price entries retain amount, currency and cost context as JSON; prices are not summed across currencies. Product tax stays percentage points. This is catalog state, not stock movement history.

  • Pipelines

    Current accessible CRM inventory, independent of report dates; it does not reconstruct historical state. Visibility, read permissions and provider plans apply. IDs remain strings, missing values remain null and collections stay JSON. Pipeline ordering and probability configuration describe the current sales process, not historical conversion rates.

  • Pipeline stages

    Current accessible CRM inventory, independent of report dates; it does not reconstruct historical state. Visibility, read permissions and provider plans apply. IDs remain strings, missing values remain null and collections stay JSON. Stage probabilities retain percentage points; days-to-rotten is the provider's configured day count. Names and ordering are current configuration.

  • Leads

    Current accessible CRM inventory, independent of report dates; it does not reconstruct historical state. Visibility, read permissions and provider plans apply. IDs remain strings, missing values remain null and collections stay JSON. Amounts retain the record currency; totals across currencies must not be added without conversion. Recurring revenue and contract values require an eligible plan and can be null. Uses the still-supported v1 lead inventory and offset pagination; leads do not have a v2 list equivalent. Leads inherit deal-field definitions. Custom lead values and conversion actions are not included.

  • Archived leads

    Current accessible CRM inventory, independent of report dates; it does not reconstruct historical state. Visibility, read permissions and provider plans apply. IDs remain strings, missing values remain null and collections stay JSON. Amounts retain the record currency; totals across currencies must not be added without conversion. Recurring revenue and contract values require an eligible plan and can be null. Uses the still-supported v1 lead inventory and offset pagination; leads do not have a v2 list equivalent. Leads inherit deal-field definitions. Custom lead values and conversion actions are not included.

  • Deal field definitions

    Current accessible CRM inventory, independent of report dates; it does not reconstruct historical state. Visibility, read permissions and provider plans apply. IDs remain strings, missing values remain null and collections stay JSON. Current field codes, types, options and compound subfields describe the connected account's schema. Definitions and collections stay JSON; typed custom-value columns are not created. Private field names/options are loaded only in connected reports.

  • Person field definitions

    Current accessible CRM inventory, independent of report dates; it does not reconstruct historical state. Visibility, read permissions and provider plans apply. IDs remain strings, missing values remain null and collections stay JSON. Current field codes, types, options and compound subfields describe the connected account's schema. Definitions and collections stay JSON; typed custom-value columns are not created. Private field names/options are loaded only in connected reports.

  • Organization field definitions

    Current accessible CRM inventory, independent of report dates; it does not reconstruct historical state. Visibility, read permissions and provider plans apply. IDs remain strings, missing values remain null and collections stay JSON. Current field codes, types, options and compound subfields describe the connected account's schema. Definitions and collections stay JSON; typed custom-value columns are not created. Private field names/options are loaded only in connected reports.

  • Product field definitions

    Current accessible CRM inventory, independent of report dates; it does not reconstruct historical state. Visibility, read permissions and provider plans apply. IDs remain strings, missing values remain null and collections stay JSON. Current field codes, types, options and compound subfields describe the connected account's schema. Definitions and collections stay JSON; typed custom-value columns are not created. Private field names/options are loaded only in connected reports.

  • Activity field definitions

    Current accessible CRM inventory, independent of report dates; it does not reconstruct historical state. Visibility, read permissions and provider plans apply. IDs remain strings, missing values remain null and collections stay JSON. Current field codes, types, options and compound subfields describe the connected account's schema. Definitions and collections stay JSON; typed custom-value columns are not created. Private field names/options are loaded only in connected reports.

  • Field changes for a deal

    Provider-available field-change history for one explicitly selected deal. Report dates do not filter the returned history. This is not a complete account audit log or a reconstruction of historical CRM snapshots. Provider time spelling and old/new value types are retained; access and history limits apply.

Metrics and dimensions

240 report fields across 17 datasets.

Hover or tap a field to see what it means. Custom fields from your own account appear after you connect.

Send Pipedrive data anywhere

Ask AI about your data

Claude or ChatGPT can read the same numbers. You ask in a normal sentence, and the answer stays with your report.

AI tools can also make allowed Pipedrive changes. They can never widen their own access.

Which opportunities in Pipedrive with values over $50k have had no activity for 14 days?

Four enterprise accounts totaling $240k in pipeline with stalled momentum and their assigned account executives.

Better than exporting by hand

Start from a goal

How it works

  1. Connect Pipedrive from Data sources with the read access your reports need.

  2. Pick where it goes. This one sends the numbers to Claude.

  3. Choose a dataset and its fields, then refresh on a schedule.

Sample report

Pipedrive reportSample data
Deal value and currencyArchived deals and leadsProducts and pricesPipelines and stagesContact detailsLinked activitiesDue and completion datesField definitions
Northwind renewalNorthwind renewal$80.00Lead1,2401,240Oct 271,240
Acme expansionAcme expansion$125.50Proposal640640Oct 28640
Harbor pilotHarbor pilot$42.00Won210210Oct 29210

Sample numbers, so you can see the shape. Your report uses your accounts.

Works well with Pipedrive

Add both to the same project. Each keeps its own report, so you can check them side by side or ask ChatGPT or Claude a question that needs both.

Questions

Free to start. Paid plans add more data sources and refresh faster.

Free and Starter refresh once a day. Pro refreshes every hour. Agency refreshes every 15 minutes on the first 50 data sources.

No. Name a project, add a data source, then choose a report and destination.

OAuth means you sign in with the service and grant access, without pasting an API key. Datapipe works with multiple partners to provide that sign-in. Some partners already provide it. Some integrations are API-only at present, so you paste a key or token. OAuth is coming soon for some. Some partners do not provide OAuth at all. The setup steps on each integration page say how that source connects. Signing in is only how the connection is made. It is not permission to change records. Where a source supports changes, those writes stay off until the workspace owner turns specific actions on and approves each one. We do not promise OAuth on every source, and we do not share dates.

The workspace owner, workspace admins and project managers. Changes start off. They choose which changes are allowed for each data source and who can make them: project operators and managers, selected teammates, and the AI tools those people connect. They can change this at any time.

No. Teammates make allowed changes in Datapipe, and Datapipe applies them through the connected Pipedrive account. Nobody else gets a Pipedrive login from this.

Yes, if that change is allowed for them. They work through Datapipe the same way a teammate does, within the same allowed changes and fields, and every change is recorded in the Changes history. AI tools can switch changes off, but they can never widen their own access. Asking for more waits for a person.

Yes, if you want. For each data source, approval can cover risky changes only (deleting, sending, publishing, refunds and price changes) or every change. You can also switch it on for one person, such as an intern. Those changes wait on the Changes page until the owner, an admin or a project manager approves them. Nobody but the owner approves their own change.

Datapipe sends each change once and records the result in the Changes history. If it cannot confirm that Pipedrive received it, the request is marked Uncertain and is never retried automatically, so you can check Pipedrive first.

Yes. Datapipe reads the reports on this page and can make 23 kinds of change: update contact name; update company name; update deal title; update any approved person field; update any approved organization field; update any approved deal field; create a person; create a organization; create a deal; assign a person to another owner; assign a organization to another owner; assign a deal to another owner; add a note to a person; add a note to a organization; add a note to a deal; schedule an activity on a person; schedule an activity on a organization; schedule an activity on a deal; delete a person; delete a organization; delete a deal; move a deal to another stage; mark a deal won, lost or open. Each one stays off until the owner, an admin or a project manager allows it for this data source. Allowed changes apply right away and are recorded in the Changes history. Provider permissions still apply.

This page lists 240 report fields across 17 datasets. You pick the columns when you build the report.

Available rows depend on the connected account, selected report type, its date rules and provider limits. Current-inventory reports show current records rather than earlier historical states.

One for each Pipedrive account you add to a project. Adding the same account to another project counts again. Reports and destinations do not use extra data sources.

Yes. The same numbers can go to a sheet, a chart, a warehouse, or an assistant.

Try Pipedrive with sample data first

Build the report first, then add Pipedrive when you are ready.

Start free Add data source