Skip to main content
Use the @bijection/connectors/pipedrive entrypoint to declare Pipedrive resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Deals, persons, organizations and activities

pull: update_time cursor walk, soft-deletion withdrawal, Basic-authorized webhook hints

The following example matches configuration deals.
The function references identify application policy queries. Implement those policies in your application; the references alone grant no authority.

Configuration: deals

Case: pipedrive/records/pull/deals. Connection and resource configuration are declared by this exact case. Credential kind: pipedrive. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: deals
Commands
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Configuration: persons

Case: pipedrive/records/pull/persons. Connection and resource configuration are declared by this exact case. Credential kind: pipedrive. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: persons
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. The connection holds a pipedrive credential (pipedrive.credential) for https://<companyDomain>.pipedrive.com, with companyDomain as setup. An API token is a header API-key credential named x-api-token; an OAuth token is a bearer. Identity is the exact integer company_id of GET /api/v1/users/me. records.pull reads one of deals, persons, organizations or activities through API v2: updated_since (inclusive) sorted by update_time ascending, 500 rows a page by next_cursor. The first pass starts at 1970; each finished pass carries the latest update_time it read and the next pass starts five minutes before it, deduplicating re-read rows by update_time, the version. is_deleted: true withdraws a record. Deals list deleted rows only under status=deleted (for 30 days), so a deal pass ends with that listing from the same bound. Whether the other listings return soft-deleted rows is not documented. Fields are kept as provider text, so money never passes through a float. With updates: "webhooks", a webhooks v2 delivery identified by meta.id hints that the object type changed, and the next pass reads it. Pipedrive signs nothing; it sends the HTTP Basic credentials configured on the webhook, which the listener’s signing credential holds as the whole Authorization value, so a delivery proves the channel, not its body: it cannot name the record to refresh. update is an unconditional single-attempt PATCH. Nothing here has run against Pipedrive or been qualified.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.