Connect Pipedrive

≈ 1 min Extension Bearer Token

Before you start

• A Pipedrive account.
• The AWFlow browser extension. These steps run in the extension (the web app hands them to it).

Used by

• Pipedrive

Set it up

This is the only method. The token can do anything your Pipedrive user can.

1. Copy the token. In Pipedrive, open Settings › Personal preferences › API and copy Your personal API token.

2. Save it in AWFlow. Open Credentials and click Add Credential (or + Add Credential in a node’s Credential field), then fill the New Credential form. In the browser side panel the form comes in two steps: tap Pipedrive in the list, then fill the rest.

   12345

   1. 1 Step 1:Pick Pipedrive Under Integration App / Service, pick Pipedrive. There is no Auth Type menu: Pipedrive uses a Bearer Token.
   2. 2 Step 2:Name it For example Pipedrive – sales. A Description is optional.
   3. 3 Step 3:Paste the token Paste the token into Bearer Token.
   4. 4 Step 4:Check where it is saved Signed in, choose Local (this browser only) or Cloud (synced to your account) under Storage location. Without an account it is saved locally in this browser, as here.
   5. 5 Step 5:Click Create Credential Check: the credential is listed on the Credentials page, ready to pick in nodes.

   Numbered areas in the screenshot: 1. Integration App / Service: Pipedrive; 2. Name; 3. Bearer Token; 4. Where the secret is stored (here, locally in this browser); 5. Create Credential.

Check it's connected — 

Run Person › Search with a name you know: the person comes back.

Where your token lives

Where your token lives — 

The credential is stored where you choose when you create it:

• Local (this browser only): encrypted in this browser. The encryption key is kept on the same device, so turn on the local secret vault to lock it with a passphrase only you know.
• Cloud (synced to your account): sent over an encrypted connection and stored encrypted on AWFlow’s server, so it works on your other devices.

When a step runs, your browser sends it only to api.pipedrive.com. AWFlow’s servers never relay the call.

Privacy & your data →

Common issues

• “401 … the API token is missing or invalid”. Copy the token again. Regenerating it makes the old one stop working.
• The run is blocked in the web app. Pipedrive runs through the browser extension. Install the extension and allow Pipedrive for this workflow when asked, or run the workflow from the extension. See Extension-only integrations in the web app.

Related

Pipedrive node

All connections

Create and manage credentials

Privacy & your data