Pipedrive | Operate As Docs

Connect your client's Pipedrive with a key they paste, and call its API through Operate As.

Website: pipedrive.com
Connects by: Pasting a API token
Category: CRM and sales
Services: 1
Tools: 198

Service	Key	Base URL
Pipedrive	`pipedrive`	`https://api.pipedrive.com/v1`

Connecting

Your client makes a API token in their Pipedrive settings and pastes it on their link. Operate As tries it with Pipedrive before saving it, and stores it encrypted. See Services connected with an API key.

Check they're connected

curl https://api.operate.as/v1/me/clients \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

[
  {
    "id": "6f1c2a7e-...",
    "name": "Miller Dental",
    "services": [
      "pipedrive"
    ]
  }
]

[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "pipedrive"    ]  }]

Permissions

What the client reads	Permission it asks for
Use the Pipedrive key you paste, with only the access you gave that key	Chosen on the provider's screen

Tools

Install Pipedrive's typed package for your language:

pip install operate-as-pipedrive

pip install operate-as-pipedrive

Run pipedrive.add_activity_type

curl -X POST https://api.operate.as/v1/actions/pipedrive.add_activity_type \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "6f1c2a7e-...",
    "input": {}
  }'

curl -X POST https://api.operate.as/v1/actions/pipedrive.add_activity_type \  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "clientId": "6f1c2a7e-...",    "input": {}  }'

Every input, with its JSON Schema: GET /v1/actions/pipedrive.add_activity_type

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

Pass-through

Paths continue from https://api.pipedrive.com/v1. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../pipedrive/users/me" \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../pipedrive/users/me" \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

A key works until your client deletes it in Pipedrive. They can paste a new one on the same link at any time, and your workflows carry on without changes.

See Keeping access alive and Removing access.

Calls answer, once the key is deleted

{
  "status": 401,
  "data": {
    "…": "the service's own error"
  },
  "encoding": "json"
}

{  "status": 401,  "data": {    "…": "the service's own error"  },  "encoding": "json"}