Pipedrive
Connect Pipedrive to Ploy to see every user in your Pipedrive company, the role and permission sets they hold, when they last signed in, and which teams they belong to. Ploy can also invite users, deactivate and reactivate them, change a user's role, and add or remove users from teams.
This integration is in beta
The Pipedrive integration is in beta. It was built from Pipedrive's documented API and has not yet been run against a live Pipedrive company, so some behaviour may differ from what is described here until it has.
The first step of setup is a consent checkbox. Ticking it lets Ploy send redacted error data to its own monitoring when a call to Pipedrive fails. Redacted means secrets, tokens and personal details are removed before anything is stored. Ploy uses it only to fix problems with the integration. You need to tick it to continue.
What Ploy reads
Every user in the connected company, with their email address, name, role and permission sets for each Pipedrive app (for example Sales and Projects).
Users who have been invited but have not accepted yet, shown as pending.
Users who have been deactivated or deleted, shown as no longer having access.
When each user last signed in.
The company itself, so several Pipedrive companies connected to one Ploy organisation stay separate.
Every team, and which users belong to it. A team's manager is marked as Manager.
Ploy does not read deals, persons, organizations or any other CRM records.
What Ploy can change
Invite a user by email address. Pipedrive gives them its default access. Someone who is already a user is left as they are.
Deactivate and reactivate a user.
Remove a user. Pipedrive cannot delete users, so removing a user deactivates them.
Give or remove a role. A user holds one role, so giving another role swaps it. Removing a role moves the user to your company's default role.
Add or remove a user from a team, from the team's page in Ploy.
Permission sets are shown in Ploy but cannot be changed from Ploy, because Pipedrive's API does not allow changing them for an existing user.
Before you start
You need a Pipedrive user who is an admin of the company. Ploy acts with that user's permissions, and reading roles and permission sets, and changing users and teams, all need admin rights. Many companies use a dedicated admin user for integrations so access does not depend on one person.
Connect Pipedrive
In Ploy, open Integrations, find Pipedrive and start setup.
Tick the beta consent checkbox.
Enter your company's Pipedrive address, for example
acme.pipedrive.com. You can paste the whole address from your browser, or just the company domain (acme).In Pipedrive, signed in as the admin user, open your profile menu, then Personal preferences, then API, and copy your personal API token.
Paste the token into Ploy and select Test connection. Ploy checks it can read your company's roles, which also confirms the token belongs to an admin.
Finish setup. The first scan starts straight away and runs every hour after that.
Troubleshooting
"Pipedrive rejected that API token": the token was not copied in full, or it has been regenerated since. Copy it again from Personal preferences.
"That API token cannot read the company's roles": the token's user is not an admin. Use the token of an admin user.
"Pipedrive could not find that company": check the address matches the one you sign in at.
A role shows on nobody: roles are kept up to date each scan. A role nobody holds any more disappears from users after the next scans.
Pipedrive limits how many API calls a company can make each day, based on your plan and number of seats. Ploy's hourly scan uses a small share of that budget.