Pipedrive Data Targets

Overview

DataBlend supports the following data targets for creating records in Pipedrive:

  • Add Deal

  • Add Follower To Deal

  • Add Participant To Deal

  • Add Product To Deal

  • Delete Follower From Deal

  • Delete Participant From Deal

  • Delete Deal

  • Delete Product From Deal

  • Duplicate Deal

  • Merge Deals

  • Update Product On Deal

  • Update Deal

  • Add Follower To Organization

  • Add Organization

  • Delete Follower From Organization

  • Delete Organization

  • Merge Organizations

  • Update Organization

Configuration 

Setting

Required/ Optional 

Description

Type

Required

Pipedrive

Name

Required

Enter descriptive free text to name your Data Target.

Query

Required

Select the query that will generate the data for this target.
See the relevant target type documentation for additional details on what query columns are required for your target.

Credential

Required

Select the Pipedrive credential from the populated drop-down menu

Query Mode

Required

Choose New unless you have a reason for choosing Latest or Specific.

 To learn more about Pipedrive API requirements, please visit Pipedrive API v1 Reference.

Advanced

History Retention

History Retention (Days) allows users to decide how long they want the information from their data targets to be stored. This field is optional.

Timeout (seconds)

The Timeout section allows users to determine if they would like to timeout collections taking longer than a set number of seconds to collect data.

Skip If No Records Found

The “Skip if No Records Found” button is used to eliminate sending information to Data Targets unnecessarily. Simply enable the “Skip if No Records Found” toggle. The use of this toggle is optional.

Agent

The Agent drop-down for users to select any agent they have established. This is optional.

Run As

Run As allows users to select from a drop-down list of users to run the Workflow. This is optional. Please note that Run As is only available to Admin users. If a user is set as the Run As and then demoted to a Member, the user which demoted the Run As user will instead be set as the Run As.