Get started

CRM, sales & support · wired today

Drive Pipedrive with governed agents

Pipeline truth lives here, and agents are only as honest as their source. The Pipedrive connector is one of 205 executable connectors and gives agents 5 read-only tools, with the credential held in the vault and every call receipted.

What agents can run against Pipedrive

ToolWhat it does
list_dealsList Pipedrive deals, optionally filtered by status
get_dealGet one Pipedrive deal by its numeric ID
list_personsList Pipedrive persons (contacts)
list_organizationsList Pipedrive organizations (companies)
search_dealsSearch Pipedrive deals by term across title, notes and custom fields

Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.

What the Pipedrive connector needs

You provide API token from your Pipedrive account; Quox sends it as an API key sent as a query parameter. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.

Where to get it: Pipedrive's own API documentation ↗ covers creating and scoping the credential.

How proven is this?

Pipedrive answers every unauthenticated request identically, so its endpoint paths rest on Pipedrive's own published API reference (cited in the connector spec). The credential wire format was verified against the real host. Like every factory connector, it is Beta: it has not yet been run with a real credential.

Pipedrive integration FAQ

What can Quox agents do with Pipedrive?

Agents can run 5 read-only tools against Pipedrive: list deals, get deal, list persons, list organizations, search deals. Every call is receipted in the evidence trail.

What does the Pipedrive integration need?

You provide API token from your Pipedrive account; Quox sends it as an API key sent as a query parameter. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.

Do agents see my Pipedrive credentials?

No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.

How proven is the Pipedrive connector?

Pipedrive answers every unauthenticated request identically, so its endpoint paths rest on Pipedrive's own published API reference (cited in the connector spec). The credential wire format was verified against the real host. Like every factory connector, it is Beta: it has not yet been run with a real credential.