Skip to main content
Human guide: work with your agent → Inspect one Pipedrive action before starting provider-backed work. Your first result is a verified input and output contract.

​
Provider-specific requirements

Use Pipedrive only with the workspace’s own API token. Start with read operations such as listing users, pipelines, stages, or searching records to discover identifiers before writes. Create, update, archive, convert, and delete operations modify customer CRM data. Inspect the generated tool description and required identifiers before executing them. List endpoints use cursor pagination. pass the returned cursor to continue. Pipedrive also applies an account token budget whose per-operation cost is documented as x-token-cost in the upstream API specification.

​
Find an applicable action

Confirm your effective workspace, then search the live catalog:
Search returns candidates. Check the returned provider and operation rather than selecting a similar title automatically.

​
Inspect the selected contract

Replace <returned-tool-id> with the identifier returned by discovery:
These commands do not execute the selected provider action. Read its required inputs, supported access mode, pricing unit, outputs, and limits. A connection does not establish that every action supports BYOK. Follow the provider-specific requirements above and the live action contract.

​
Prepare one reviewed input

Use one authorized record that matches the inspected schema. Preserve its source identity and define the result you will accept. Open the action reference for its payload and response shape. Provider-backed execution can incur usage or external effects. For reusable logic, follow Write Plays. For direct-call recovery, use Tool execution recovery.
Continue only when the workspace, provider, required fields, acceptance rule, and applicable price are understood. Keep unavailable access separate from no-result evidence.