CRM
Connect Pipedrive to Chatsy
Review the configured deal, person, and organization tools. The connection can be set up, but an agent cannot run these actions yet.
Route these requests to your team
Until agent execution passes end-to-end testing, set up human handoff so a person handles the requests these tools would cover.
Connects with an API token
Chatsy verifies the credential with Pipedrive before saving it, then stores it encrypted with AES-256-GCM.
Scope
What is configured
Action templates
- DealsSearchCreateSearch or create Pipedrive deals.
- ContactsSearchCreateSearch or create Pipedrive contacts.
- OrganizationsSearchCreateSearch Pipedrive organizations by name.
The configured provider routes need an API update before these actions can be tested.
Setup guide
Connect and review Pipedrive
Connect the service and review the configured tools.
- 01
Connect the service
In Integrations, choose Pipedrive and enter the API token from your Pipedrive account.
- 02
Review the configured tools
The connection creates provider tool records for existing agents. Review their methods, fields, and enabled state.
Limits and fit
Where this setup can fail, and when another path fits better.
Common failure modes
- The credential is invalid, expired, or later revoked.
- An enabled tool is asked to perform an action outside the fields and methods it supports.
- The agent runtime calls a provider route without the required session and the request is rejected.
Not a fit for
- Workflows that need actions not listed on this page.
- Requests that should always be reviewed by a person before an external action runs.
- Agent workflows that depend on these configured tools before the runtime authentication boundary is fixed and tested end to end.
FAQ
Common questions
Ready to connect Pipedrive?
Create an agent, connect the service, and review its configured tools.