> ## Documentation Index
> Fetch the complete documentation index at: https://docs.1eye.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Pipedrive

> Connect Pipedrive to 1eye, map buyer and company fields, choose when to push records, then run your workflow and verify delivery in the Console.

Push buyers and companies from your 1eye target lists into Pipedrive. Buyers become People, companies become Organizations, and the person is linked to the matching organization.

### Before you begin

* Admin or Marketer access to your 1eye workspace.
* A Pipedrive account with permission to install the app and create or update People and Organizations.
* At least one [Target List](https://docs.1eye.ai/target-lists/overview.md). Use a list with eligible buyers to verify your first push.
* Valid work emails and usable names for buyers, plus company names and website domains for organization matching.

You connect through Pipedrive's sign-in and authorization flow. You do not need an API key, code, or a CSV export. The screenshots use Snowbricks as an example workspace.

### Connect Pipedrive

**Step 1: Create the destination workflow**

1. Open **Destinations** in your 1eye workspace.
2. Select **Add Destination**.
3. Enter a name, such as **Push to Pipedrive**, select **Pipedrive**, and select **Add**.

The workflow follows **Start → Target Lists → Destination → End**.

**Step 2: Open the Pipedrive node**

Select the **Pipedrive** destination node. If it shows **Not Connected**, select **Connect**.

![Pipedrive destination node showing Not Connected and the Connect button](https://mintcdn.com/1eye/TXP_Kmyuy6narUjA/images/pipedrive-connect.png?fit=max\&auto=format\&n=TXP_Kmyuy6narUjA\&q=85\&s=49c80e3d961ffddc4fcae00b51bf2fab)

**Step 3: Authorize your Pipedrive account**

1. In the 1eye confirmation, select **Yes, continue**.
2. Sign in on Pipedrive's authorization screen.
3. Choose the correct Pipedrive company, review the permissions, and select **Allow and Install**.
4. Return to 1eye and confirm that the destination shows **Connected**.

Connecting the account does not start sending records. Finish the target list and field mapping settings, then run the workflow.

### Target Lists node

Select the **Target Lists** node, then:

1. Choose one or more 1eye target lists.
2. Choose **Delivery behavior**:

| Option | What it pushes |
| - | - |
| **Going forward** | New buyers as they are identified. |
| **Push retroactively** | Existing buyers in the selected lists, then new buyers going forward. |

3. Select **Save Target Lists**.

![Target Lists node with selected lists, delivery behavior options, and Save Target Lists](https://mintcdn.com/1eye/TXP_Kmyuy6narUjA/images/pipedrive-target-lists.png?fit=max\&auto=format\&n=TXP_Kmyuy6narUjA\&q=85\&s=81b57895a3f98a1401ef316cd07f4010)

Return to the **Pipedrive** destination node to configure the fields sent for those buyers and companies.

![Selected Target Lists feeding the connected Pipedrive destination](https://mintcdn.com/1eye/TXP_Kmyuy6narUjA/images/pipedrive-select-buyers.png?fit=max\&auto=format\&n=TXP_Kmyuy6narUjA\&q=85\&s=37efd80acf183acb7d871a857fcb05fb)

### Field mapping

Mapping is organized into four sections: **Standard Buyer Fields**, **Custom Buyer Fields**, **Standard Company Fields**, and **Custom Company Fields**.

Keep **Push** checked for each standard field you want to send. Uncheck optional fields you want to exclude.

**Standard Buyer Fields**

| 1eye field | Pipedrive field |
| - | - |
| Work Email | Email |
| First Name | Name |
| Last Name | Name |
| Phone | Phone |
| Company Name | Organization |

First and last names combine into Pipedrive's Name field. Company Name links the person to their organization.

A valid work email is used to match a buyer to an existing Pipedrive Person. Keep that email available in the buyer's 1eye record even if you turn off updates to the Email field.

**Custom Buyer Fields**

1. Select a **1eye Field**.
2. Select an existing, compatible **Pipedrive Custom Property**.
3. Select **+ Add more** for additional mappings.

For example, map Persona Name to a text field or Target Page Visit Count to a number field. For buyer title, LinkedIn, or location data, use a compatible custom field when a standard mapping is unavailable.

> [!NOTE]
>
> Create custom fields in Pipedrive before mapping them in 1eye. 1eye does not create them automatically. Person fields and Organization fields are separate, so choose a field on the correct record type.

**Standard Company Fields**

| 1eye field | Pipedrive field |
| - | - |
| Company Name | Name |
| Company Website | Website |
| Company LinkedIn | LinkedIn profile |
| Employee Count | Number of employees |
| Annual Revenue | Annual revenue |
| Address, City, State, Zip, Country | Address |

Company names and website domains help identify the correct Organization. Address components populate Pipedrive's Address field. Send employee count and revenue only when the values are valid for the mapped field.

**Custom Company Fields**

Choose a 1eye company field and an existing, compatible Pipedrive organization custom property. Select **+ Add more** to add another mapping.

For example, map Company Description to a text field you have created in Pipedrive.

![Pipedrive standard buyer and company mappings, custom mapping controls, and Save Destination](https://mintcdn.com/1eye/TXP_Kmyuy6narUjA/images/pipedrive-map-fields.png?fit=max\&auto=format\&n=TXP_Kmyuy6narUjA\&q=85\&s=a9f4d8ace0df834c83fef2039a42fc1a)

Under **Push behavior** below the mappings, choose **Once per Target Buyer**, **New Signal**, or **Every Signal**. Use **Once per Target Buyer** to push when the buyer is first identified, or a signal-based option to push again as new signals arrive.

Select **Save Destination** once your mappings and push behavior are set.

### Run the workflow

1. Open the **Start** node.
2. Choose **Runs continuously**, **Runs until the selected date**, or **Runs once only**.
3. Select **Save Workflow Settings**.
4. Confirm that your target lists and destination settings are saved, then select **Run**.

For a first test with buyers already in your list, choose **Push retroactively** in the Target Lists node and **Runs once only** in the Start node.

1eye reuses matching Pipedrive records and updates only the fields you configure. People are matched by work email; Organizations are matched using company identity and website domain. If more than one record matches, review the conflict in the Console before retrying.

### Monitor pushed records

Select **View console** in the workflow. Review **All**, **Pushed**, **Pending**, or **Failed** records.

| Status | What to check |
| - | - |
| **Pushed** | The configured delivery completed. Open the record to review the result. |
| **Pending** | The record is queued, waiting for a retry, or needs a data or configuration fix. |
| **Failed** | Delivery could not complete. Open the record for the error and attempt details. |

Select a buyer to inspect the fields sent or attempted, the Pipedrive Person and Organization IDs, and any response or error.

Use the Pipedrive record links when available to verify the Person, linked Organization, and mapped values. If the Organization was created but the Person failed, inspect the Person error; the successful Organization is retained.

### Disconnect Pipedrive

1. Open the workflow and select the **Pipedrive** node.
2. Open the **⋮** menu next to **Connected**.
3. Select **Disconnect**.

Disconnecting stops workflows that depend on the connection. People and Organizations already pushed remain in Pipedrive. To restore access, reconnect to the intended Pipedrive account.

### Best practices

* **Start with one small target list.** Check a few Pushed records in Pipedrive before adding more.
* **Review names and identifiers.** Buyers need a usable name and valid email; companies need a name and website domain for reliable matching.
* **Map only the fields you need.** Use compatible custom fields for account-specific information.
* **Check the Console after the first run.** Resolve missing data, invalid mappings, or matching conflicts before expanding the workflow.

### Troubleshooting

| Issue | What to check |
| - | - |
| Connect does not open an authorization window | Allow pop-ups for 1eye, then select Connect again. |
| Wrong Pipedrive company connected | Disconnect and reconnect, choosing the intended company on the authorization screen. |
| Connection shows Reconnect Required | Select Reconnect from the destination menu and authorize Pipedrive again. |
| No buyers appear in the Console | Confirm the selected lists contain eligible buyers. Choose Push retroactively to include existing buyers, save, and run the workflow. |
| Buyer cannot be pushed | Check for a valid work email and usable name, then inspect the Console error. |
| Multiple records match | Resolve the duplicate or conflicting records in Pipedrive, then retry. 1eye does not merge CRM records for you. |
| A mapped field is missing or rejected | Check Push, the source value, and the field's type and availability. Replace deleted or incompatible custom mappings, then save. |
| Pipedrive API limit reached | Review the Console message. Synchronization waits and resumes automatically when the limit allows. |

### FAQ

> [accordion] Does 1eye see my Pipedrive password?
>
> No. You sign in and authorize access on Pipedrive's own screen.

> [accordion] Can I change mappings after the workflow starts?
>
> Yes. Open the Pipedrive node, update the mapping, and select Save Destination. New jobs use the latest saved mapping; changing it does not automatically rewrite every historical record.

> [accordion] Does this create Leads or Deals?
>
> No. This destination syncs buyers as People and companies as Organizations.

> [accordion] Does Pipedrive sync back to 1eye?
>
> No. This destination sends data from 1eye to Pipedrive.

> [accordion] What happens when a buyer leaves a target list?
>
> People and Organizations already pushed remain in Pipedrive. Removing a buyer from a target list does not delete CRM records.

### Next step

See [Managing Destinations](https://docs.1eye.ai/destinations/managing-destinations.md) for more workflow guidance.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.