Connector · CRM and email lists

Pipedrive, in every client’s workflows.

List people, create a person, or start when a deal moves to a stage, with the client’s own Pipedrive account.

Triggers: 5start a workflow
Actions: 4steps in a workflow

Start a workflow when something happens in PipedriveBeta

By webhook where Pipedrive sends one, by checking where it does not. A webhook is checked once a day to see it is still on, and if Pipedrive turns it off the alert carries a Reconnect button.

A deal moves to a stageWebhookA deal enters the stage you choose, within seconds.
A deal is wonWebhookA deal is marked won, within seconds.
A new deal is createdWebhookA deal added in Pipedrive, within seconds.
A new contact is addedWebhookA person added in Pipedrive, within seconds.
An activity is scheduledWebhookA call, meeting or task added in Pipedrive, within seconds.

Do it in Pipedrive

A step with its own fields: values from the run go in by name, and what Pipedrive answers is there for the next step.

List peopleEvery person, up to 1,000 (ten pages of 100), with their emails, phones and organisation. Past that, the step says it stopped.
Create a personA new person (contact).
Update a personChange a person’s name, email or phone, found by id. Fields left empty keep their value.
Create a dealA deal, linked to a person, in the stage you choose: the lead is in the pipeline.

Connect the client’s Pipedrive

On the client’s page in Thrum: Add credential, type Pipedrive API token.

In the client’s Pipedrive: your avatar → Personal preferences → API → copy the token.

The key is stored encrypted and bound to that client: another client’s workflow cannot use it, and no template or pack copies it.

Pipedrive’s API documentation

Via HTTP

Or by web request: add a person

Sales-led clients see the enquiry as a person in their pipeline, ready for a deal. The web request step, filled in: paste it, swap in the client’s ids, add their key.

01
Add the client’s credential
On the client’s page in Thrum: Add credential, type API key. In the client’s Pipedrive: your avatar → Personal preferences → API → copy the token.
```
{
  "api_key": "…"
}
```

Add a web request step

Name it “Add to Pipedrive”, set it as here, and pick the credential. Values in double braces are read from the run: here, the lead the form brought in.

{
  "method": "POST",
  "url": "https://api.pipedrive.com/v1/persons",
  "headers": {
    "x-api-token": "{{ credential.api_key }}"
  },
  "body": {
    "name": "{{ lead.name }}",
    "email": "{{ lead.email }}",
    "phone": "{{ lead.phone }}"
  }
}

What goes out, and what comes back

Pipedrive does not merge duplicates on add: the same email twice is two people. Clean up in Pipedrive, or look the person up first with a GET to /v1/persons/search.

POST https://api.pipedrive.com/v1/persons
content-type: application/json
x-api-token: ••••••••

{
  "name": "Nadia Karim",
  "email": "nadia@example.com",
  "phone": "+447700900222"
}

201
{
  "success": true,
  "data": {
    "id": 1001,
    "name": "Nadia Karim",
    "email": [
      {
        "value": "nadia@example.com",
        "primary": true
      }
    ],
    "phone": [
      {
        "value": "+447700900222",
        "primary": true
      }
    ]
  }
}

Watched like everything else

When Pipedrive stops answering or refuses the client’s key, you hear about it, and your client does not.

A failing request: Tried 3 times, 5 seconds apart and doubling, only for errors a retry can fix
A service that asks for a pause: Given it, up to an hour
Requests at once, per account: 2, per worker; the rest wait their turn
Timeout: 15 seconds, unless the step sets its own
Private and internal addresses: Refused, on every redirect too
The client’s key: Encrypted, bound to the client, and kept out of every run record
A step that keeps failing: Marks the workflow Degraded and alerts you, not the client

Pipedrive and its logo are trademarks of their owner, used here only to say what Thrum works with; no endorsement is implied.

Thrum is cooking.

Get early access and you’ll be among the first in. Early members get a launch perk.

Get early access See pricing