About the Pipedrive category

o.plokha · August 26, 2024, 7:33am

Put topics about this connector package here.

Always check the ‘How to use the Alumio connector packages’ topic.

Extra information

System documentation: Pipedrive API Reference

Connector package documentation

1. Setting up HTTP Client Pipedrive

1.1 Steps

In the Alumio Dashboard, go to Clients → HTTP Clients. Create a new HTTP Client.
Select Pipedrive HTTP Client as PlatForm and click next step
Fill in the Base URI and API Token.
(See the Pipedrive Authentication Documentation for more information)
You can optionally enable logging of request to get the log of the authentication.
Click next step, fill the name of the HTTP Client and finally you can save the HTTP Client for use.

2. Subscribing to Entities from Pipedrive

2.1 Steps

Go to Connections → Incoming and create a new incoming configuration and select “Pipedrive Subscriber” as the subscriber.
Select the entity you want to subscribe to from Pipedrive.
Add any request parameters needed to subscribe to the entity.
Select the Pipedrive HTTP Client to use.
You can optionally add a transformer to transform the request parameters into something you will request from Pipedrive.
You can also optionally enable pagination to allow Alumio fetches paginated entities.

2.2 General Concept

We follow Pipedrive documentation on building this connector, so you can easily use the connector based on Pipedrive API Reference.

Entity

The entity you want to subscribe to Pipedrive. Please refer to the entities from Pipedrive API Reference page.

Request Parameters

These are the parameters you can provide to get the needed entity based on the Pipedrive API Reference.

Please look at the example below on how to fill path field when we want get a user by subscribing “Users - Get one user” entity.

From the end point, we can see that we need to set the user id as parameters. That is why we set the “id” inside the path key in the Request Parameters.

Alumio will then make a request to Pipedrive with the URL /v1/users/22013967

Path is the path parameter of the url. For example the {id}.
Query is defined set of parameters attached to the end of a url.
Example: www.url.com?type=true&start=0

HTTP Client

The HTTP Client configuration you will use to access Pipedrive.

3. Publishing Entity to Pipedrive

3.1 Steps

Go to Connections → Outgoing, create a new outgoing configuration and select “Pipedrive Publisher” as the publisher.
Select the Method that you want the publisher to perform with the data.
Select the Pipedrive entity you want the data to be published to.
You can optionally add any query data to the request on the key query.
You can optionally add any payload data to the request on the key payload.
Select the HTTP Client to use.

3.2 General Concept

Like the subscriber, the publisher has similar methods on how to use it. The difference is the payload that will be submitted by the publisher originating from the data (from routes, from transformers in outgoing configuration), though you can also add or modify payload using the Request Transformer.

Method

Currently, we support HTTP Post method, HTTP Put method and HTTP Delete method on submitting data to Pipedrive.

Entity

We support publishing to most Pipedrive endpoints.
Please refer to Pipedrive API Reference page.

For example, we want to edit an user. Please select “Put” as the Method and “Users - Update user details”.

From the documentation, we can see that we need to set a path parameter and a body parameters. That is why we set the “id” inside the path key and body parameters inside the payload key in the data.

Alumio will send an API request to Pipedrive with URL /v1/users/22013967

Path is the path parameter of the url. For example the {id}.
Query is defined set of parameters attached to the end of a url.
Example: www.url.com?type=true&start=0
Payload is the data contained within a request.