A Pipedrive connection lets the Pipedrive steps work with deals, people, organisations, activities, leads, notes and products in your Pipedrive company, and lets the Pipedrive triggers start a run the moment something changes there. It connects with your personal API token. Bizomate reads your company's Pipedrive address from the token, so you do not type it. Everything the steps do is done as you, with what you can see and change in Pipedrive.

Who can do this

  • In Bizomate: workspace Admins and Editors. Viewers see the connection but cannot add or change it.
  • In Pipedrive: any user can copy their own API token. The connection sees and changes what that user can, so use a user who can reach every pipeline and record your workflows need.
  • Plan: Pipedrive is a premium connection, marked ◇. You can add it and test its steps and triggers on any plan; publishing a workflow that uses it needs Starter, Pro or Enterprise.

Steps

In Pipedrive, copy the token:

  1. Sign in to Pipedrive.
  2. Open Settings, then Personal preferences.
  3. Open the API tab.
  4. Copy your personal API token. If there is none yet, generate one first.

In Bizomate, add the connection:

  1. Select Connections in the bar at the top, then + Add connection.
  2. Under CRM/Sales, select Pipedrive — marked ◇, and on the Free plan "Stored credential · Paid plans".
  3. In Connection name, type a name — for example Consulace Pipedrive.
  4. Paste the token in API token — In Pipedrive: Settings › Personal preferences › API — copy your personal API token. Steps act as you, and see what you can see.
  5. Optional: in This token expires on · optional, the date your company's policy gives the token — If the service gave the key an end date. The workspace’s admins are reminded 30, 7 and 1 days before.
  6. Leave Test the connection before saving ticked. Bizomate asks Pipedrive who the token belongs to before keeping it.
  7. Select Save connection. The button reads Testing while Pipedrive is asked.

The toast "Connection added" says what Pipedrive answered — for example "“Consulace Pipedrive” is ready. Reached Rohan Mehta · Consulace (consulace.pipedrive.com)."

What happens next

  • The connection appears under CRM/Sales. Its panel shows Test, Replace token and Revoke — never the token.
  • Test answers with your name, your company and its address — Reached Rohan Mehta · Consulace (consulace.pipedrive.com). Every record's url uses that address.
  • Pipedrive steps and triggers list it under Connection, and read each kind of record's fields — custom fields included — from your Pipedrive company.

Good to know

  • On the Free plan the window notes: "Pipedrive is on paid plans. You can add it and test the steps that use it now; publishing a workflow that uses it asks for a paid plan."
  • The token belongs to one Pipedrive user. Records the steps create are made by that user. If that user is deactivated, the connection stops working — replace the token with another user's.
  • Regenerating the token in Pipedrive ends the old one at once. Open the connection's panel, select Replace token, paste the new token and select Replace token. The toast "Token replaced" says "Workflows that use “Consulace Pipedrive” use the new key from their next run."
  • Signing in with Pipedrive instead of a token is not offered yet.

If something goes wrong

What you see Why What to do
Pipedrive refused it — "Pipedrive refused: … Check the connection's details on Connections. Nothing was saved." The token was mistyped, regenerated, or belongs to a deactivated user. Copy the token again from Personal preferences › API and paste it.
"Could not reach Pipedrive: …" Pipedrive did not answer. Try again in a few minutes.
"Pipedrive did not answer within 30 seconds." Pipedrive was slow. Try again.
"Fill in API token." API token is empty. Paste the token.
A step fails with "Pipedrive did not say the company's address. Test the connection on Connections." Pipedrive's answer about the token's user had no company address. Select Test on the connection; if it fails, replace the token.