PipelineCRM
Connect PipelineCRM to Ploy to see every user in your PipelineCRM account, their level, who is an account administrator and which team each person is in. Ploy can also add users, change their level, move them between teams and deactivate them.
This integration is in beta
PipelineCRM is a beta integration. It was built from PipelineCRM's API documentation and has not yet been run against a live PipelineCRM account. Everything works as described here, but some details may change once it has.
The first step of setup asks you to agree to beta terms. Ticking the box lets Ploy send redacted error details to our engineering team when a PipelineCRM request fails, so we can fix problems quickly. Redacted means names, email addresses, keys and other personal or secret values are removed before anything is stored.
Before you start
You need:
A PipelineCRM user who is an account administrator and whose level is Executive. Only Executives can see every user in the account, and only administrators can add or change users.
That user's API key.
An app key for Ploy, which an account administrator registers in PipelineCRM.
Ploy acts as the user whose API key you use. Changes Ploy makes are recorded in PipelineCRM as that person, and resetting their API key stops the connection. Consider using a dedicated administrator for Ploy.
Get your keys from PipelineCRM
Sign in to PipelineCRM as the Executive account administrator.
Open your account's API settings page.
Copy your API key.
On the same page, register a new integration named Ploy and copy the app key PipelineCRM gives it.
Connect PipelineCRM in Ploy
In Ploy, go to Integrations and choose PipelineCRM.
Tick the beta consent box.
Paste the API key and the app key.
Optionally, choose the level that people Ploy adds will receive. Basic is used if you leave it empty.
Continue to the next page and, optionally, choose the team that people Ploy adds will join. PipelineCRM puts every Basic and Manager user in a team, so Ploy can only add Basic or Manager users once a team is chosen.
Save. Ploy tests the keys by reading your user list and tells you if anything is wrong.
What Ploy reads
Every user, including deactivated users, with their email address, name, level, whether they are an account administrator, whether two-factor sign-in is on, and when they last signed in.
Every team, and which team each user is in.
Ploy reads PipelineCRM every hour. A user deactivated in PipelineCRM loses their access in Ploy on the next read.
Ploy does not read your deals, companies, people or other CRM records.
What Ploy can change
Add a user at the level and in the team chosen during setup. PipelineCRM sends no invitation, so the new user signs in however your administrators normally arrange it. Someone who already has a user is left as they are.
Change a user's level between Basic, Manager and Executive, and make them an account administrator or take that away. Moving someone down from Executive puts them in the team chosen during setup.
Move a user into a team, from the team's page in Ploy. This takes them out of the team they were in.
Deactivate a user. PipelineCRM keeps their history and gives the records they own to the administrator whose API key Ploy uses.
Ploy will never deactivate or change the level of the administrator whose API key the connection uses, because the connection would stop working. PipelineCRM's API cannot reactivate a deactivated user, so do that in PipelineCRM itself.
Troubleshooting
PipelineCRM refused those keys. Check both keys were copied in full and that neither has been reset.
PipelineCRM refused to list users. Use the API key of an account administrator at Executive level.
Ploy shows fewer users than PipelineCRM. The API key probably belongs to a user below Executive level. Ploy will not remove anyone's access while that is the case; reconnect with an Executive administrator's key.