Appearance
Pipedrive
Sales CRM for managing deals, contacts, and activities via the Pipedrive API.
| Detail | Value |
|---|---|
| Category | CRM |
| Base URL | https://api.pipedrive.com/v1 |
| Authentication | API Key (Query) |
| Endpoints | 6 |
| Connector key | pipedrive |
Using Pipedrive in a workflow
- Go to Connections and click New Connection.
- Pick Pipedrive from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /persons | List all persons |
POST /persons | Create a person |
GET /deals | List all deals |
POST /deals | Create a deal |
GET /organizations | List all organizations |
GET /activities | List all activities |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /persons
List all persons
| Detail | Value |
|---|---|
| Operation ID | crm.listPersons |
| Method | GET |
| Path | /persons |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
start | query | integer | No |
limit | query | integer | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Pipedrive connection from the Connection dropdown.
- In the Operation dropdown, select
crm.listPersons. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Pipedrive API reference.
POST /persons
Create a person
| Detail | Value |
|---|---|
| Operation ID | crm.createPerson |
| Method | POST |
| Path | /persons |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
name | string |
email | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Pipedrive connection from the Connection dropdown.
- In the Operation dropdown, select
crm.createPerson. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Pipedrive API reference.
GET /deals
List all deals
| Detail | Value |
|---|---|
| Operation ID | crm.listDeals |
| Method | GET |
| Path | /deals |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
start | query | integer | No |
limit | query | integer | No |
status | query | string | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Pipedrive connection from the Connection dropdown.
- In the Operation dropdown, select
crm.listDeals. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Pipedrive API reference.
POST /deals
Create a deal
| Detail | Value |
|---|---|
| Operation ID | crm.createDeal |
| Method | POST |
| Path | /deals |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
title | string |
value | number |
currency | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Pipedrive connection from the Connection dropdown.
- In the Operation dropdown, select
crm.createDeal. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Pipedrive API reference.
GET /organizations
List all organizations
| Detail | Value |
|---|---|
| Operation ID | crm.listOrganizations |
| Method | GET |
| Path | /organizations |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Pipedrive connection from the Connection dropdown.
- In the Operation dropdown, select
crm.listOrganizations. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Pipedrive API reference.
GET /activities
List all activities
| Detail | Value |
|---|---|
| Operation ID | crm.listActivities |
| Method | GET |
| Path | /activities |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
start | query | integer | No |
limit | query | integer | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Pipedrive connection from the Connection dropdown.
- In the Operation dropdown, select
crm.listActivities. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Pipedrive API reference.