Pipedrive

Notes:

The Pipedrive connector is currently in feature preview and as such documentation for this feature is still work in progress

Contact us to get on the waitlist

The Pipedrive connector loads Deals, Activities, Organizations, Persons, Products, Leads, Projects, Pipelines, and Stages into xpna Lists through a read-only private OAuth app. This connector is a private pilot and is not a public Marketplace integration.

Prerequisites

• The Pipedrive connector must be enabled for the workspace.
• A Pipedrive global administrator must complete authorization. Other users cannot guarantee complete company visibility.
• Pop-up windows must be permitted while authorization is in progress.
• The private app must have read-only access to Deals, Activities, Contacts, Products, Leads, and Projects. Contacts access covers both Persons and Organizations. Deals access also covers Pipelines and Stages.
• Projects must be included in the Pipedrive plan or enabled as an add-on for the authorizing user.

Connect Pipedrive

• Open Connections, choose Add Connection, and select Pipedrive.
• Select Authorise and complete the Pipedrive consent flow.
• Confirm that the company and authorizing user shown in xpna are correct.
• Test the connection before saving it.
• Add a provider object and choose Deals, Activities, Organizations, Persons, Products, Leads, Projects, Pipelines, or Stages.
• Map the provider fields to a normal List. For Deals, use the provider id as the List key so later lifecycle records update the same row.

The application registration and credentials are managed by xpna. Client credentials and personal API tokens are not entered in the connector.

Loading behavior

• The connection test confirms the authorized company and global administrator through GET /api/v1/users/me. Users are not available as a List provider object.
• Activities, Products, and Projects are read from GET /api/v2/activities, GET /api/v2/products, and GET /api/v2/projects, with every cursor page followed to completion.
• Leads are read from GET /api/v1/leads, with every start offset followed to completion.
• Pipelines and Stages are read from GET /api/v2/pipelines and GET /api/v2/stages, with every cursor page followed to completion.
• Provider IDs, relationship IDs, timestamps, and field names are preserved.
• Pipeline fields and Stage-to-Pipeline relationships are preserved.
• custom_fields remains rich JSON so selected fields can be expanded with normal List configuration.
• When the List uses a compatible, noncomputed update_time discriminator, the connector sends an inclusive bounded update window for Deals, Activities, Organizations, and Persons.
• Products and Leads send the inclusive lower update_time bound supported by Pipedrive. Their endpoints do not accept an upper update bound.
• Projects, Pipelines, and Stages are always complete reads and do not send a provider watermark. Other or malformed watermarks also use a complete provider read.
• Deal loads include current, archived, and recently deleted Deals. If the same Deal appears more than once, the connector keeps its newest lifecycle record.
• Pipedrive retains deleted Deals for only 30 days. Run the connection frequently enough to observe tombstones during that window; the connector cannot recover deletions after that retention period.
• Lists use upserts for received rows. Filtering out a deleted or archived Deal does not remove an older row already in the List, and a Deal missing from a later provider response is not deleted from the List.
• A Project, Pipeline, or Stage missing from a later complete read is not removed from the List. The connector does not infer deletion from a missing provider row.
• A failed page, repeated cursor or offset, authentication error, or unrecovered rate limit fails the load and does not advance the List watermark.

Disconnect

Use Disconnect in the saved Pipedrive source to remove local access and request refresh-token revocation. Local access is removed even when Pipedrive cannot confirm the remote revocation; xpna displays a warning in that case.

Deleting a connection is not a substitute for Disconnect.

Troubleshooting

• If authorization is rejected, ask a Pipedrive global administrator to reconnect the company.
• If Test Data reports that an object returned no rows, the Pipedrive request succeeded but no records were visible to the authorized user. Add a record in Pipedrive or check the user's visibility permissions, then test again.
• If Pipedrive reports that billing attention is required, xpna shows a persistent business warning that must be dismissed. Confirm that the company account is active, its trial has not expired, and payment details are current. For Projects, also confirm that Projects is included in the plan or enabled as an add-on for the authorizing user.
• If Pipedrive denies access, confirm that the private app has the matching read-only scope and that the authorizing user can view the selected object.
• If Pipedrive reports that a feature is not enabled, enable that feature for the company and authorizing user before testing it again.
• Pipedrive does not provide one complete list of every endpoint enabled for an authorized company. xpna therefore validates the selected object when Test Data runs and reports the provider's reason when it is unavailable.
• If a daily API budget is exhausted, wait for the Pipedrive limit to reset before retrying.
• If authorization has expired or been revoked, disconnect and authorize the connector again.
• For further help, contact xpna support via email to support@xpna.com.