You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/actions-pipedrive/index.md
+27-16Lines changed: 27 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,13 +3,11 @@ title: Actions Pipedrive
3
3
hide-boilerplate: true
4
4
hide-dossier: true
5
5
id: 5f7dd8191ad74f868ab1fc48
6
-
private: true
7
-
hidden: true
8
6
---
9
7
10
8
{% include content/plan-grid.md name="actions" %}
11
9
12
-
The Actions Pipedrive destination is an integration that allows customers to share events from Segment directly to Pipedrive. When you use Pipedrive with Segment, you don’t need to manually export and upload data to Pipedrive. Your customer data will remain up to date in real time and across all enabled integrations. Every tool you use to interact with leads and customers will land in Pipedrive, so you can always have a clear picture in front of you.
10
+
The Actions Pipedrive destination allows customers to share Segment event data with Pipedrive. Segment events sent to Pipedrivewill either create new Entities or update existing Entities in Pipedrive.
13
11
14
12
## Benefits of Actions Pipedrive
15
13
@@ -20,21 +18,34 @@ Actions Pipedrive provides the following benefits:
20
18
21
19
## Getting started
22
20
23
-
1. From the Segment web app, click **Catalog**, then click **Destinations**.
24
-
2. Find the Destinations Actions item in the left navigation, and click it.
25
-
3. Click **Configure "Actions Pipedrive"**.
26
-
4. Select an existing Source to connect to "Actions Pipedrive".
27
-
5. When adding Pipedrive as a destination, you will be redirected to the basic settings page, where you need to enter the destination name as well as Pipedrive's domain and API token.
28
-
6. To complete the installation process, switch to advanced settings and enter your Pipedrive IDs.
21
+
1. Sign in to your Segment Workspace
22
+
2. Click to the **Catalog** tab.
23
+
3. Click on the **Destinations** tab.
24
+
2. Use the search field to find the 'Pipedrive' destination. Click on the **Actions Pipedrive** tile.
25
+
3. Click **Add Destination**.
26
+
4. Select a source to connect to and click the **Next** button.
27
+
5. Provide a name for your Pipedrive destination and click the **Create Destination** button.
28
+
6. On the Settings tab, provide values in the **Domain** and **API Token** settings fields, then click the **Save Changes** button.
29
+
7. Navigate to the **Mappings** tab to configure how Segment events will be mapped to Pipedrive Entities. By default, mappings to upsert to Pipedrive's Person, Organization and Activity Entities will already be enabled. You can configure new Mappings by clicking on the **New Mapping** button.
30
+
8. After you've configured and enabled your Mappings, click back to the **Settings** tab and enable the integration using the **Enable Destination** toggle. Segment should now start sending event data to Pipedrive.
29
31
30
-
To set up the Segment integration with your Pipedrive account:
31
-
1. Go to either your Marketplace menu within your settings or directly to Pipedrive's Marketplace.
32
-
2. Search for *Segment* and click on **Install now**.
33
-
3. A new window will pop up and prompt you to allow Segment to connect with Pipedrive.
34
-
4. Choose the Pipedrive account you wish to connect to, then, click **Allow and Install**.
32
+
## Inserting new Entities compared to updating existing Entities
35
33
36
-
Once the installation is successful, you'll be redirected to Segment to authenticate your account.
34
+
Segment uses the **Match value** field value as a key when creating or updating an Entity in Pipedrive. By default, the **Match value** will be mapped to the **id** field for the corresponding Entity. You can specify which Pipedrive field to use as a key using the **Match field** field.
37
35
38
-
{% include components/actions-fields.html %}
36
+
**Match field** fields are dynamic and will populate with data from your Pipedrive account.
37
+

38
+
39
+
In the following example, Segment is configured to create or update Person entities using the email field.
40
+

41
+
42
+
## Associating Entities with other Entities
39
43
44
+
Entities such as the **Deal** Entity can be configured to be associated with other Entities in Pipedrive. In the example **Deal** mapping below the following will happen:
45
+
1. A **Person** Entity with an email address matching **properties.email** will be associated with the **Deal** Entity being created or updated.
46
+
2. An **Organization** Entity with an ID matching **properties.org_id** will be assocated with the **Deal** Entity being created or updated.
47
+
48
+

0 commit comments