*Gap samples / Gap 3 - Integrations*

# Pipedrive integration: data flow (draft for engineering review)

This page is deliberately a draft. Public sources say EULER supports Pipedrive but say almost nothing about how. So the sample shows the other half of the job: a page structured to match the existing Salesforce and HubSpot Data Flow articles, with every fact sourced and every unknown turned into a question engineering can answer in one sitting.

**Gap:** 3 of 13 · **Reader:** Admin or RevOps on Pipedrive · **State:** Draft, about two-thirds questions

## Why this page needs to exist

Forms 2.0 names Pipedrive as one of the three CRMs Forms work with. eulerhq.com lists Pipedrive under CRMs and says the CRM integrations are bidirectional and map to any object or field. Yet the Integrations collection has HubSpot (6 articles), Salesforce (3) and QuickBooks (2), and nothing for Pipedrive. [Potential Duplicate](https://support.eulerapp.com/en/c/integrations/potential-duplicate) explains duplicate handling for HubSpot and Salesforce only, so a Pipedrive admin cannot tell what happens when an applicant already exists.

---

*Sample documentation starts here*

## Overview

EULER connects to Pipedrive so partner records, partner contacts and partner deals stay in sync, and so EULER Forms can write submissions into Pipedrive. **[VALIDATE AUTH METHOD]** Pipedrive's own objects are Organizations, People, Deals and Leads. The table below is the mapping engineering needs to confirm.

## How EULER reads from Pipedrive

| EULER record | Pipedrive object | How EULER identifies it | Fields read |
| --- | --- | --- | --- |
| Partner | [Organization?] | [label, custom field, or filter] | [name, ID, created, modified] |
| Partner contact | [Person?] | [linked to the partner Organization] | [first, last, email, title] |
| Partner deal | [Deal] | [custom field linking the deal to the partner] | [title, value, stage, pipeline, close date] |

## How EULER writes to Pipedrive

Writes go through EULER Forms. Each question's **API Value** **shall** match a real field key on the Pipedrive object, or the form's CRM sync fails. Run the form's **Test** before publishing. Both rules come from Forms 2.0 and apply to every CRM.

- Which objects can a form write to: [Organization, Person, Deal, Lead?]
- Are custom fields addressed by their Pipedrive field key or their name? [key / name]

## Duplicates

[What EULER searches before accepting a Partner Registration or Referral submission in Pipedrive, and which of Proceed with Creation, Mark as Approved and Reject are offered. This section should be added to Potential Duplicate as a third CRM.]

## What wrong looks like

**WRONG - PUBLISHING THIS PAGE AS IT IS**

```
"EULER syncs your Pipedrive Organizations, People
and Deals in real time."

Why it fails: no public source says which objects,
which direction, or how often. A confident sentence
that turns out wrong costs more support tickets than
the missing page did. Brackets stay until confirmed.
```

## Confirm with engineering

Fifteen minutes of answers turns this draft into the page.

1. Pipedrive connects through OAuth from Integrations, like Salesforce and HubSpot. Yes / no / correct me.
2. Partners are Organizations identified by [label / custom field]. Correct me.
3. Partner contacts are People linked to that Organization. Yes / no / correct me.
4. A deal is attributed to a partner through [field]. Correct me.
5. Forms can write to Organizations, People, Deals and Leads. Correct me with the list.
6. The duplicate check matches People on email and Organizations on name and/or website, as for HubSpot. Yes / no / correct me.
7. Sync runs [in real time / every n minutes]. Correct me.
8. EULER inherits the permissions of the Pipedrive user who connects. Yes / no / correct me.

### Related documentation

- [Salesforce Integration: Data Flow](https://support.eulerapp.com/en/c/integrations/salesforce/salesforce-integration-data-flow) and [HubSpot Integration: Data Flow](https://support.eulerapp.com/en/c/integrations/hubspot/hubspot-integration-data-flow) (the page template)
- [Forms 2.0](https://support.eulerapp.com/en/c/core-euler-features/customization-content/forms-2-0)
- [Potential Duplicate](https://support.eulerapp.com/en/c/integrations/potential-duplicate)
- [About the Pipedrive API](https://pipedrive.readme.io/docs/core-api-concepts-about-pipedrive-api) (Pipedrive docs)
- [Pipedrive OAuth reference](https://developers.pipedrive.com/docs/api/v1/Oauth) (Pipedrive docs)
- [EULER + Pipedrive on eulerhq.com](https://eulerhq.com/integrations/pipedrive)

### Sources for this page

- Forms 2.0: Pipedrive named as a supported CRM; API Value and Test rules.
- eulerhq.com/integrations: Pipedrive under CRMs. eulerhq.com FAQ: CRM integrations bidirectional, any object or field.
- Salesforce Integration: Data Flow and HubSpot Integration: Data Flow, used as the page template.
- Potential Duplicate: covers HubSpot and Salesforce, not Pipedrive.

### Next

- Gap 4: [Salesforce setup checks](05-salesforce.md). The finished version of this page type.
- Gap 12: [Style guide](13-styleguide.md). Why "Pipedrive", not "PipeDrive".

---

*Independent writing sample by Bachtiar Widyantoro (bachwidy.site), November 2026. Not published or endorsed by EULER. Free to reuse and edit. Customer names in examples are fictional. Anything marked [VALIDATE ...] or [CONFIRM ...] is not settled by a public source and needs checking before publishing.*