Pipedrive Connection Details¶

Introduction¶

Connector Version

This documentation is based on version 23.0.8936 of the connector.

Get Started¶

Pipedrive Version Support

The connector leverages the Pipedrive API to enable bidirectional access to Pipedrive.

Establish a Connection¶

Connect to Pipedrive¶

Pipedrive offers two ways to connect and authenticate: Basic and OAuth.

Basic Authentication¶

To authenticate via Basic authentication:

1. Obtain an API Token:
   1. Open the Pipedrive portal.
   2. At the top right corner of the page, click the account name. Pipedrive displays a drop-down list.
   3. Navigate to Company Settings > Personal Preferences > API > Generate Token.
   4. Record the value of the generated API token. Also, note the CompanyDomain,which is visible in the PipeDrive HomePage URL. (This is the company's developer sandbox URL.)
2. Set these connection properties:
   • APIToken: The value for the API token you just obtained.
   • CompanyDomain: The CompanyDomain from the developer sandbox URL.
   • AuthScheme: Basic.
3. Log in with the approved user name and password.

The API Token is stored in the Pipedrive portal. To retrieve it, click the company name, then use the drop-down list to navigate to Company Settings > Personal Preferences > API.

OAuth Authentication¶

If you do not have access to the user name and password or do not want to require them, use the OAuth user consent flow. To enable this authentication from all OAuth flows, you must set AuthScheme to OAuth and create a custom OAuth application.

The following subsections describe how to authenticate to Pipedrive from three common authentication flows. For information about how to create a custom OAuth application, see Creating a Custom OAuth Application. For a complete list of connection string properties available in Pipedrive, see Connection.

Desktop Applications¶

To authenticate with the credentials for a custom OAuth application, you must get and refresh the OAuth access token. After you do that, you are ready to connect.

Get and refresh the OAuth access token:

• InitiateOAuth: GETANDREFRESH. Used to automatically get and refresh the OAuthAccessToken.
• OAuthClientId: The client ID assigned when you registered your custom OAuth application.
• OAuthClientSecret: The client secret that was assigned when you registered your custom OAuth application.
• CallbackURL: The redirect URI that was defined when you registered your custom OAuth application.

When you connect, the connector opens Pipedrive's OAuth endpoint in your default browser. Log in and grant permissions to the application.

After you grant permissions to the application, the connector completes the OAuth process:

1. The connector obtains an access token from Pipedrive and uses it to request data.
2. The OAuth values are saved in the path specified in OAuthSettingsLocation. These values persist across connections.

When the access token expires, the connector refreshes it automatically.

Automatic refresh of the OAuth access token:

To have the connector automatically refresh the OAuth access token:

1. Before connecting to data for the first time, set these connection parameters:
   • InitiateOAuth: REFRESH.
   • OAuthClientId: The client ID in your custom OAuth application settings.
   • OAuthClientSecret: The client secret in your custom OAuth application settings.
   • OAuthAccessToken: The access token returned by GetOAuthAccessToken.
   • OAuthSettingsLocation: The path where you want the connector to save the OAuth values, which persist across connections.
2. On subsequent data connections, set:
   • InitiateOAuth
   • OAuthSettingsLocation

Manual refresh of the OAuth access token:

The only value needed to manually refresh the OAuth access token is the OAuth refresh token.

1. To manually refresh the OAuthAccessToken after the ExpiresIn period (returned by GetOAuthAccessToken) has elapsed, call the RefreshOAuthAccessToken stored procedure.
2. Set these connection properties:
   • OAuthClientId: The Client ID in your custom OAuth application settings.
   • OAuthClientSecret: The Client Secret in your custom OAuth application settings.
3. Call RefreshOAuthAccessToken with OAuthRefreshToken set to the OAuth refresh token returned by GetOAuthAccessToken.
4. After the new tokens have been retrieved, set the OAuthAccessToken property to the value returned by RefreshOAuthAccessToken. This opens a new connection.

Store the OAuth refresh token so that you can use it to manually refresh the OAuth access token after it has expired.

Create a Custom OAuth Application¶

Create a Custom OAuth Application¶

If you do not have access to the user name and password or do not wish to require them, you can use OAuth authentication. Pipedrive uses the OAuth authentication standard, which requires the authenticating user to interact with Pipedrive via the browser. Authenticating via OAuth requires the use of the OAuth client credentials, client Id, and client secret.

To register a custom OAuth application and obtain the OAuth client credentials, client id, and client secret:

1. Log into your Pipedrive account Login Page.
2. At the drop-down menu, click Tools and integrations. Pipedrive displays the Settings page.
3. In the menu at left, click Marketplace Manager.
4. Click Create new app.
5. Click the yes or no button.
6. Fill in all requested items.
7. Enter a value for the application's Redirect URI:
   • If you are making a desktop application, set the Callback URL to http://localhost:33333 or a different port number of your choice.
   • If you are making a web application, set the Callback URL to a page on your Web app that you want the user to be returned to after they have authorized your application.
8. When you have filled in all required fields, click Save. Pipedrive displays a confirmation screen that shows the data you have just filled in.
9. Check your entries on the confirmation screen. If everything looks correct, click Add a new.

Enabled applications are displayed in the list and the process completes.

The OAuthClientId and ClientSecret are displayed along with the information you specified when setting up the application. Record the OAuthClientID and ClientSecret for future use.

Important Notes¶

Configuration Files and Their Paths¶

• All references to adding configuration files and their paths refer to files and locations on the Harmony Agent where the connector is installed. These paths are to be adjusted as appropriate depending on the agent and the operating system. If multiple agents are used in an agent group, identical files will be required on each agent.

Data Model¶

Overview

This section shows the available API objects and provides more information on executing SQL to Pipedrive APIs.

Key Features

• The connector models Pipedrive entities like documents, folders, and groups as relational views, allowing you to write SQL to query Pipedrive data.
• Stored procedures allow you to execute operations to Pipedrive
• Live connectivity to these objects means any changes to your Pipedrive account are immediately reflected when using the connector.

Views

Views describes the available views. Views are statically defined to model Pipedrive entities such as Currencies, DealsPersons, and ProductsFiles.

Tables

Tables describes the available tables. Tables are statically defined to model Pipedrive entities such as Activities, Users, and Leads.

Stored Procedures

Stored Procedures are function-like interfaces to Pipedrive. Stored procedures allow you to execute operations to Pipedrive, including downloading documents and moving envelopes.

Tables¶

The connector models the data in Pipedrive as a list of tables in a relational database that can be queried using standard SQL statements.

Pipedrive Connector Tables¶

Activities¶

Get all Activities assigned to a particular User.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• Id supports the = operator.
• Done supports the = operator.
• Type supports the '=, IN' operators.
• UserId supports the = operator.
• FilterId supports the = operator.
• StartDate supports the = operator.
• EndDate supports the = operator.

For example, the following query is processed server side:

SELECT * FROM Activities WHERE Id = 246

SELECT * FROM Activities WHERE Done = 0

SELECT * FROM  Activities WHERE Type IN ('deadline', 'call')

SELECT * FROM  Activities WHERE EndDate = '2021-12-24'

SELECT * FROM  Activities WHERE UserId = 8230170

INSERT¶

The columns that are not read-only can be inserted. Following is an example of how to insert into this table.

INSERT INTO ActivitiesAttendees#TEMP (EmailAddress) VALUES ('blaineh@cdata.com')
INSERT INTO Activities (DueDate, DueTime, Duration, Dealid, Attendees) VALUES ('1994-10-12', '10:20', '02:00', 1, 'ActivitiesAttendees#TEMP')

UPDATE¶

UPDATE can be executed by specifying the ID in the WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE Activities SET DealId = 2 WHERE ID = 245

DELETE¶

DELETE can be executed by specifying the ID in the WHERE Clause. For example:

DELETE FROM Activities WHERE ID = 246

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

ActivityTypes¶

Get all ActivityTypes.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• Id supports the = operator.

For example, the following query is processed server side:

SELECT * FROM Activities WHERE ID = 9

INSERT¶

Insert can be executed by specifying the Name and IconKey columns. The columns that are not required can be inserted optionally. For example:

INSERT INTO ActivityTypes (Name, IconKey, color, IsCustomFlag, KeyString) VALUES ('test42', 'task', 'FFFFFF', 'true', 'call')

UPDATE¶

Update can be executed by specifying the ID in the WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE ActivityTypes SET IconKey = 'email' WHERE ID = 7

DELETE¶

Delete can be executed by specifying the ID in the WHERE Clause. For example:

DELETE FROM ActivityTypes WHERE ID = 2

Columns¶

CallLogs¶

Returns all call logs assigned to a particular user.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• Id supports the = operator.

For example, the following query is processed server side:

SELECT * FROM CallLogs WHERE ID = 'cf75de9e4cbcb4a33658ad40561e3230'

INSERT¶

Insert can be executed by specifying the Outcome, ToPhoneNumber, StartTime and EndTime columns. The columns that are not required can be inserted optionally.

INSERT INTO CallLogs (Outcome, StartTime, EndTime, Duration, FromPhoneNumber, ToPhoneNumber, UserId, OrgId) VALUES ('connected', '2021-12-15', '2021-12-16', '140', '984656646', '9846566456', '8230170', '6')

DELETE¶

Delete can be executed by specifying the ID in the WHERE Clause. For example:

DELETE FROM CallLogs WHERE ID = '8381cea5da671fa16a1eb63af15e5ec4'

Columns¶

DealFields¶

Returns data about all deal fields.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• Id supports the = operator.

For example, the following query is processed server side:

SELECT * FROM DealFields WHERE ID = 12478

INSERT¶

Insert can be executed by specifying the Name and IconKey columns. The columns that are not required can be inserted optionally. For example:

INSERT INTO DealFields (Name, AddVisibleFlag, FieldType) VALUES ('test43', 'false', 'address')

UPDATE¶

Update can be executed by specifying the ID in the WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE DealFields SET Name = 'test44' WHERE ID = '12500'

DELETE¶

Delete can be executed by specifying the ID in the WHERE Clause. For example:

DELETE FROM DealFields WHERE ID = 12500

Columns¶

Deals¶

Get all deals.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• Id supports the = operator.
• StageId supports the = operator.
• Status supports the = operator.
• FilterId supports the = operator.
• UserId supports the = operator.
• PersonId supports the = operator.
• OrgId supports the = operator.
• OwnedByYou supports the = operator.

For example, the following query is processed server side:

SELECT * FROM Deals WHERE Id = 14

SELECT * FROM Deals WHERE StageId = 1

SELECT * FROM Deals WHERE  Status = 'Open'

SELECT * FROM Deals WHERE FilterId = 1

SELECT * FROM Deals WHERE FilterId = 1

SELECT * FROM Deals WHERE OrgId = 1

SELECT * FROM Deals WHERE OwnedByYou = 1                

INSERT¶

Insert can be executed by specifying the Title columns.The columns that are not read-only can be inserted. Following is an example of how to insert into this table.

INSERT INTO Deals (title, PersonId) VALUES ('tetsptest', 6203)

UPDATE¶

Update can be executed by specifying the ID in the WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE Deals SET Title = 'test' WHERE ID = 15

DELETE¶

Delete can be executed by specifying the ID in the WHERE Clause. For example:

DELETE FROM Deals WHERE ID = 15

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

DealsFollowers¶

Get details of deals followers.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• Id supports the = operator.

For example, the following query is processed server side:

SELECT * FROM DealsFollowers WHERE ID = 2

INSERT¶

Insert can be executed by specifying the Name and IconKey columns. The columns that are not required can be inserted optionally. For example:

INSERT INTO DealsFollowers (userid, id) VALUES (8230170, 8)

DELETE¶

Delete can be executed by specifying the Id, DealId in the WHERE Clause. For example:

DELETE FROM DealsFollowers WHERE ID = 1 AND Dealid = 1

Columns¶

DealsParticipants¶

Get details of deals participants.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• Id supports the = operator.

For example, the following query is processed server side:

SELECT * FROM DealsParticipants WHERE ID = 9

INSERT¶

Insert can be executed by specifying the Content and PersonId columns. The columns that are not required can be inserted optionally. For example:

INSERT INTO DealsParticipants (Id, Personid) VALUES (4, 6)

DELETE¶

Delete can be executed by specifying the ID in the WHERE Clause. For example:

DELETE FROM DealsParticipants WHERE ID = 14 AND ItemDealId = 17

Columns¶

DealsProducts¶

Get details of deals products.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• Id supports the = operator.

For example, the following query is processed server side:

SELECT * FROM DealsProducts WHERE ID = 9

INSERT¶

Insert can be executed by specifying the Content and PersonId columns. The columns that are not required can be inserted optionally. For example:

INSERT INTO DealsProducts (DealId, ProductId, ItemPrice, quantity) VALUES (2, 2, 20000, 1)

UPDATE¶

Update can be executed by specifying the ID and Dealid in the WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE DealsProducts SET quantity = 20 WHERE ID = 15 AND Dealid = 2

DELETE¶

Delete can be executed by specifying the Id, DealId in the WHERE Clause. For example:

DELETE FROM DealsProducts WHERE ID = 15 AND Dealid = 2

Columns¶

Files¶

Returns data about all files.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• Id supports the = operator.

For example, the following query is processed server side:

SELECT * FROM Files WHERE ID = 400

UPDATE¶

Update can be executed by specifying the ID in the WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE Files SET Name = 'Updating PipeDrive Pipelines1' WHERE ID = 405

DELETE¶

Delete can be executed by specifying the ID in the WHERE Clause. For example:

DELETE FROM Files WHERE ID = 400

Columns¶

Filters¶

Returns data about all filters.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• Id supports the = operator.
• Type supports the = operator.

For example, the following query is processed server side:

SELECT * FROM Filters WHERE ID = 39

INSERT¶

Insert can be executed by specifying the Name, Conditions and Type columns. The columns that are not required can be inserted optionally. For example:

INSERT INTO Filters (Name, Conditions, Type) VALUES ('Indias Filter', '{"glue": "and","conditions": [{"glue": "and","conditions": [{"object": "organization","field_id": "4020"}]}]}', 'deals')

UPDATE¶

Update can be executed by specifying the ID in the WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE Filters SET Name = 'Updating Pipedrive filters', Conditions = '{"glue": "and","conditions": [{"glue": "or","conditions": [{"object": "organization123","field_id": "4021"}]}]}' WHERE ID = 39

DELETE¶

Delete can be executed by specifying the ID in the WHERE Clause. For example:

DELETE FROM Filters WHERE ID = 10

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Goals¶

Goals help your team meet your sales targets.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• Id supports the = operator.
• Title supports the = operator.
• Name supports the = operator.
• Type supports the = operator.
• Title supports the = operator.
• PipelineId supports the = operator.
• ActivityTypeId supports the = operator.

For example, the following query is processed server side:

SELECT * FROM Goals WHERE id = 'c924154b747f214228a906d3de079801' AND DurationEnd = '2022-02-03' AND DurationStart = '2022-01-01'

SELECT * FROM Goals WHERE Title = 'test'

SELECT * FROM Goals WHERE Type = 'test'

SELECT * FROM Goals WHERE TypeName = 'test'

INSERT¶

Insert can be executed by specifying the Content and PersonId columns. The columns that are not required can be inserted optionally. For example:

INSERT INTO Goals (Title, AssigneeId, AssigneeType, DurationStart, DurationEnd, Target, CurrencyId, TrackingMetric, Iterval, TypeName, PipelineId) VALUES ('test', 13815887, 'person', '2022-01-21', '2022-02-03', 50, 1, 'sum', 'monthly', 'deals_started', 'null')

UPDATE¶

Update can be executed by specifying the ID in the WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE Goals SET title = 'test' WHERE ID = 'c924154b747f214228a906d3de079801'

DELETE¶

Delete can be executed by specifying the ID in the WHERE Clause. For example:

DELETE FROM Goals WHERE ID = 'c924154b747f214228a906d3de079801'

Columns¶

LeadLabels¶

Returns details of all Lead Labels.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• Id supports the = operator.

For example, the following query is processed server side:

SELECT * FROM LeadLabels

INSERT¶

Insert can be executed by specifying the Name and Color columns. The columns that are not required can be inserted optionally. For example:

INSERT INTO LeadLabels (Name, Color) VALUES ('BangaloreCdataIndia123', 'blue')

UPDATE¶

Update can be executed by specifying the ID in the WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE LeadLabels SET Name = 'I am updating content' WHERE ID = '28093520-743a-11ec-96e6-031cfba07e9a'

DELETE¶

Delete can be executed by specifying the ID in the WHERE Clause. For example:

DELETE FROM LeadLabels WHERE ID = '28093520-743a-11ec-96e6-031cfba07e9a'

Columns¶

Leads¶

Returns lead data.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• Id supports the = operator.
• SearchByEmail supports the = operator.
• OwnerId supports the = operator.
• PersonId supports the = operator.
• OrganizationId supports the = operator.

For example, the following query is processed server side:

SELECT * FROM Leads

SELECT * FROM Leads WHERE Id = 'a300ea00-5d6c-11ec-9270-93cbb0be1eed'

SELECT * FROM Leads WHERE SearchByEmail = 'all'

INSERT¶

Insert can be executed by specifying the Title column. The columns that are not required can be inserted optionally. For example:

INSERT INTO Leads (Title, Personid, Visibleto, ExpectedCloseDate) VALUES ('123', 1, 1, '2022-01-01')

UPDATE¶

Update can be executed by specifying the ID in the WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE Leads SET Title = 'CdataIndia' WHERE ID = 'bf1bb1e0-6e13-11ec-b981-a127469657bd'

DELETE¶

Delete can be executed by specifying the ID in the WHERE Clause. For example:

DELETE FROM Leads WHERE ID = 'bf1bb1e0-6e13-11ec-b981-a127469657bd'

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

MailThreads¶

Get, Update and Delete mail threads in a specified folder ordered by the most recent message within.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• Id supports the = operator.
• Folder supports the = operator.

For example, the following query is processed server side:

SELECT * FROM MailThreads WHERE Folder = 'inbox'

UPDATE¶

Update can be executed by specifying the ID in the WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE MailThreads SET Subject = 'test' WHERE ID = 145

DELETE¶

Delete can be executed by specifying the ID in the WHERE Clause. For example:

DELETE FROM MailThreads WHERE ID = 145

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

NoteComments¶

Create, Update, Delete and Get the comments associated with a note.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• NoteId supports the = operator.
• UUID supports the = operator.

For example, the following query is processed server side:

SELECT * FROM NoteComments WHERE NoteId = 14

INSERT¶

Insert can be executed by specifying the NoteId and Content columns.The columns that are not read-only can be inserted. Following is an example of how to insert into this table.

INSERT INTO NoteComments (NoteId,Content) VALUES (2, 'Test comment')

UPDATE¶

Update can be executed by specifying the NoteId and UUID in the WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE NoteComments SET Content='Test' where NoteId=1 and UUID = '53e0c79fdacf083d9fe1f799fdc0a206'

DELETE¶

Delete can be executed by specifying the NoteId and UUID in the WHERE Clause. For example:

DELETE FROM NoteComments WHERE NoteId=1 and UUID = '53e0c79fdacf083d9fe1f799fdc0a206'

Columns¶

Notes¶

Returns all notes.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• Id supports the = operator.
• UserId supports the = operator.
• LeadId supports the = operator.
• DealId supports the = operator.
• PersonId supports the = operator.
• OrgId supports the = operator.
• PinnedToLeadFlag supports the = operator.
• PinnedToDealFlag supports the = operator.
• PinnedToOrganizationFlag supports the = operator.
• PinnedToPersonFlag supports the = operator.

For example, the following query is processed server side:

SELECT * FROM Notes WHERE ID = 9

INSERT¶

Insert can be executed by specifying the Content and PersonId columns. The columns that are not required can be inserted optionally. For example:

INSERT INTO Notes (ActiveFlag, Content, PersonId, AddTime) VALUES ('true', 'this is frist notes', '8', '2021-12-31')

UPDATE¶

Update can be executed by specifying the ID in the WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE Notes SET Content = 'I am updating content' WHERE ID = 7

DELETE¶

Delete can be executed by specifying the ID in the WHERE Clause. For example:

DELETE FROM Notes WHERE ID = 5

Columns¶

OrganizationFields¶

Returns data about all organization fields.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• Id supports the = operator.
• OrgId supports the = operator.

For example, the following query is processed server side:

SELECT * FROM OrganizationRelationships WHERE id = 2

INSERT¶

Insert can be executed by specifying the Type, RelOwnerOrgId and RelLinkedOrgId columns. The columns that are not required can be inserted optionally. For example:

INSERT INTO OrganizationRelationships (Type, RelOwnerOrgId, RelLinkedOrgId) VALUES ('parent', '8230170', '8230170')

UPDATE¶

Update can be executed by specifying the ID in the WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE OrganizationRelationships SET Type = 'related' WHERE ID = 2

DELETE¶

Delete can be executed by specifying the ID in the WHERE Clause. For example:

DELETE FROM OrganizationRelationships WHERE ID = 2

Columns¶

OrganizationRelationships¶

Gets all of the relationships.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• Id supports the = operator.

For example, the following query is processed server side:

SELECT * FROM OrganizationRelationships WHERE ID = 9

INSERT¶

Insert can be executed by specifying the Content and PersonId columns. The columns that are not required can be inserted optionally. For example:

INSERT INTO OrganizationRelationships (type, RelOwnerOrgId, RelLinkedOrgId) VALUES ('parent', 2, 3)

UPDATE¶

Update can be executed by specifying the ID and Dealid in the WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE OrganizationRelationships SET type = 'parent' WHERE ID = 10

DELETE¶

Delete can be executed by specifying the Id, DealId in the WHERE Clause. For example:

DELETE FROM OrganizationRelationships  WHERE ID = 10

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Organizations¶

Get details of organizations

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• Id supports the = operator.
• FirstChar supports the = operator.
• FilterId supports the = operator.
• UserId supports the = operator.

For example, the following query is processed server side:

SELECT * FROM Organizations WHERE Id = 14

SELECT * FROM Organizations WHERE FirstChar = 'c'

SELECT * FROM Organizations WHERE FilterId = 1

SELECT * FROM Organizations WHERE UserId = 1

INSERT¶

Insert can be executed by specifying the Name columns.The columns that are not read-only can be inserted. Following is an example of how to insert into this table.

INSERT INTO Organizations (name) VALUES ('testpankaj')

UPDATE¶

Update can be executed by specifying the ID in the WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE Organizations SET Name = 'test123' WHERE ID = 2495

DELETE¶

Delete can be executed by specifying the ID in the WHERE Clause. For example:

DELETE FROM Organizations WHERE ID = 15

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

OrganizationsFollowers¶

Get details of organizations followers.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• OrgId supports the = operator.

For example, the following query is processed server side:

SELECT * FROM OrganizationsFollowers WHERE OrgId = 6

INSERT¶

Insert can be executed by specifying the UserId, OrgId columns.The columns that are not read-only can be inserted. Following is an example of how to insert into this table.

INSERT INTO OrganizationsFollowers (UserId, OrgId) VALUES (8230170, 1)

DELETE¶

Delete can be executed by specifying the Id, OrgId in the WHERE Clause. For example:

DELETE FROM OrganizationsFollowers WHERE OrgId = 1 AND ID = 1

Columns¶

OrganizationsInternal¶

Get details of organizations.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

PersonFields¶

Returns data about all person fields.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• Id supports the = operator.

For example, the following query is processed server side:

SELECT * FROM PersonFields WHERE ID = 9039

INSERT¶

Insert can be executed by specifying the Name and FieldType columns. The columns that are not required can be inserted optionally. For example:

INSERT INTO PersonFields (Name, AddVisibleFlag, FieldType) VALUES ('NameCdataIndia', 'true', 'address')

UPDATE¶

Update can be executed by specifying the ID in the WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE PersonFields SET Name = 'My name just started here' WHERE ID = '9062'

DELETE¶

Delete can be executed by specifying the ID in the WHERE Clause. For example:

DELETE FROM PersonFields WHERE ID = 9040

Columns¶

PersonFollowers¶

Get details of persons followers.

Columns¶

Persons¶

Get all details of persons.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• Id supports the = operator.
• FirstChar supports the LIKE operator.
• FilterId supports the = operator.
• UserId supports the = operator.

For example, the following query is processed server side:

SELECT * FROM Persons WHERE Id = 14

SELECT * FROM Persons WHERE FirstChar = 'c'

SELECT * FROM Persons WHERE FilterId = 1

SELECT * FROM Persons WHERE UserId = 1                 

INSERT¶

Insert can be executed by specifying the Name columns.The columns that are not read-only can be inserted. Following is an example of how to insert into this table.

INSERT INTO Persons (name) VALUES ('testpankaj')

UPDATE¶

Update can be executed by specifying the ID in the WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE Persons SET Name = 'test123' WHERE ID = 2495

DELETE¶

Delete can be executed by specifying the ID in the WHERE Clause. For example:

DELETE FROM Persons WHERE ID = 15

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Pipelines¶

Get all Pipelines.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• Id supports the = operator.

For example, the following query is processed server side:

SELECT * FROM Pipelines WHERE ID = 4

INSERT¶

Insert can be executed by specifying the Name, Active, DealProbability, OrderNr and UrlTitle columns. The columns that are not required can be inserted optionally. For example:

INSERT INTO PipeLines (Name, Active, DealProbability, OrderNr, UrlTitle) VALUES ('Indias PipeLines for Pipedrive', 'true', '0', 1, 'indiapipedrivepipeline@com')

UPDATE¶

Update can be executed by specifying the ID in the WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE PipeLines SET Name = 'Updating Pipedrive Pipelines1' WHERE ID = 4

DELETE¶

Delete can be executed by specifying the ID in the WHERE Clause. For example:

DELETE FROM PipeLines WHERE ID = 5

Columns¶

ProductFields¶

Returns data about all product fields.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• Id supports the = operator.

For example, the following query is processed server side:

SELECT * FROM ProductFields WHERE ID = 28

INSERT¶

Insert can be executed by specifying the Name and FieldType columns. The columns that are not required can be inserted optionally. For example:

INSERT INTO ProductFields (Name, FieldType) VALUES ('BangaloreCdataIndia123', 'address')

UPDATE¶

Update can be executed by specifying the ID in the WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE ProductFields SET Name = 'My name just started here' WHERE ID = 28

DELETE¶

Delete can be executed by specifying the ID in the WHERE Clause. For example:

DELETE FROM ProductFields WHERE ID = 9040

Columns¶

Products¶

Get details of Products

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• Id supports the = operator.
• FirstChar supports the = operator.
• FilterId supports the = operator.
• UserId supports the = operator.
• GetSummary supports the = operator.
• Ids supports the '=,IN' operators.

For example, the following query is processed server side:

SELECT * FROM Products WHERE Id = 14

SELECT * FROM Products WHERE FirstChar = 'c'

SELECT * FROM Products WHERE FilterId = 1

SELECT * FROM Products WHERE UserId = 1

SELECT * FROM Products WHERE GetSummary = 1

SELECT * FROM Products WHERE Ids IN (1, 2)

INSERT¶

Insert can be executed by specifying the Name columns.The columns that are not read-only can be inserted. Following is an example of how to insert into this table.

INSERT INTO Products (name) VALUES ('tests')

UPDATE¶

Update can be executed by specifying the ID in the WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE Products SET Name = 'test123' WHERE ID = 2495

DELETE¶

Delete can be executed by specifying the ID in the WHERE Clause. For example:

DELETE FROM Products WHERE ID = 15

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

ProductsFollowers¶

Get details of products followers.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• ProductId supports the = operator.

For example, the following query is processed server side:

SELECT * FROM ProductsFollowers WHERE ProductId = 6

INSERT¶

Insert can be executed by specifying the UserId, ProductId columns.The columns that are not read-only can be inserted. Following is an example of how to insert into this table.

INSERT INTO ProductsFollowers (UserId, ProductId) VALUES (8230170, 1)

DELETE¶

Delete can be executed by specifying the Id, ProductId in the WHERE Clause. For example:

DELETE FROM ProductsFollowers WHERE ProductId = 1 AND ID = 1

Columns¶

Roles¶

Returns all the role.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• Id supports the = operator.

For example, the following query is processed server side:

SELECT * FROM Roles

SELECT * FROM Roles WHERE ID = 2

INSERT¶

Insert can be executed by specifying the Name and ParentRoleId columns. The columns that are not required can be inserted optionally. For example:

INSERT INTO Roles (Name, ParentRoleId) VALUES ('BangaloreCdataIndia123', '2')

UPDATE¶

Update can be executed by specifying the ID in the WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE Roles SET Name = 'My name just started here' WHERE ID = 1

DELETE¶

Delete can be executed by specifying the ID in the WHERE Clause. For example:

DELETE FROM Roles WHERE ID = 1

Columns¶

RolesAssignments¶

List assignments for a role.

Select¶

The connector will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• Id supports the = operator.

For example, the following query is processed server side:

SELECT * FROM RolesAssignments

SELECT * FROM RolesAssignments WHERE ID = 1

INSERT¶

Insert can be executed by specifying the ID and UserId columns. The columns that are not required can be inserted optionally. For example:

INSERT INTO RoleAssignments (Id, UserId, RoleId) VALUES (1, 'NameCdataIndia', '1')

DELETE¶

Delete can be executed by specifying the ID and UserId WHERE Clause. For example:

DELETE FROM RolesAssignments WHERE ID = 1 AND UserId = 1

Columns¶