Pipedrive workflow automation with AI agents
We build AI agents on top of Pipedrive that route leads, enrich people and organizations, keep deals clean and draft follow-ups. Pipedrive's own automations keep the fixed rules. The agents handle steps that need reading, through the Pipedrive API with OAuth 2.0, and write custom fields that explain each change.
For small sales teams on Pipedrive, where one person runs the pipeline and the follow-up work lives in notes and memory.
What we automate in Pipedrive
The record work around the pipeline, from the first form fill to the closed deal, with your reps deciding what changes.
- 1
Lead handling
New leads and form fills are read, matched to existing people and organizations, scored against your profile and assigned. A lead that fits no rule goes to the owner with the reason.
- 2
Enrichment
Organization and person fields are filled from sources you approve, with the source and date stored in a custom field. Conflicting values are flagged.
- 3
Deal hygiene
Deals with no next activity, a stale stage or no linked person are listed for the owner each week. Fixes apply once the owner agrees.
- 4
Follow-up drafts
After a call or demo, the agent drafts a follow-up from the notes and the deal. The rep edits and sends.
- 5
Duplicate review
Likely duplicate people and organizations are grouped with a score. A person decides which to merge.
- 6
Won-deal handoff
When a deal is won, the agent checks the fields finance needs and hands over a clean packet, or a draft invoice in your accounting system. Finance approves before billing.
How one Pipedrive run works
Each step is fixed logic, a model doing the reading, a call to the system, or a person on your team. You decide which steps wait for approval.
Read · intake agent
Reads the inquiry and the company website
Match · rules engine
Finds the existing person and organization
Enrich · enrichment agent
Fills approved fields with their source
Route · pipedrive integration
Creates the deal and assigns the owner
Review · your team
Owner confirms any unclear match
Pipedrive lead, one run
Illustrative- ReadReads the inquiry and the company websiteIntake agent
- MatchFinds the existing person and organizationRules engine
- EnrichFills approved fields with their sourceEnrichment agent
- RouteCreates the deal and assigns the ownerPipedrive integration
- ReviewOwner confirms any unclear matchHuman in the loop
How the Pipedrive integration works
We build on the interfaces the vendor documents, and we link the documentation so you can check it.
Pipedrive's strength is a simple pipeline, and we keep it that way. The agent writes a few well-named custom fields, such as score, source and routing reason. A rep opens a deal and sees why it landed with them.
Because v1 and v2 coexist, we pin which version each call uses and review it on a schedule. A change in Pipedrive's docs then shows up in our tests first.
Pipedrive REST API
A JSON API with OpenAPI 3 specifications published for v1 and v2. Deals have list, add, update and search endpoints on v2, while many related endpoints still sit on v1, so we call both where needed.
OAuth 2.0 and API tokens
Pipedrive's docs describe a stateless API checked against a token, and an OAuth 2.0 flow for apps. We prefer OAuth. Access tokens last 60 minutes, and a refresh token expires if unused for 60 days.
Custom fields
Custom field keys are 40-character hashes, and values go in a custom_fields object. Pipedrive says to clear a multi-option field with null, not an empty array. We map keys to labels once and store the map.
Request costs
Pipedrive's reference gives each call a cost, such as 5 for adding a deal and 20 for a search. We budget calls so the integration leaves room for your other tools.
Vendor documentation we build against
- Pipedrive API reference (v1)
- Deals endpoints (Pipedrive API)
- OAuth authorization for apps (Pipedrive Developers)
Links open the vendor's own site. Interfaces change, so we confirm current behavior in a sandbox before we build.
What we read and write in Pipedrive
Reading is the default. Each write has a named gate, so you can see who has to agree before anything changes.
Leads and deals
Created and updated with score, owner and stage hygiene.
Gate: Rules; owner for stage changes
Persons
Matched, enriched and linked. Conflicts are flagged.
Gate: Rules; owner for conflicts
Organizations
Enriched and associated with people and deals.
Gate: Rules; flagged conflicts reviewed
Activities
Created for follow-ups and next steps.
Gate: Rules
Notes
Read to draft follow-ups. Routing reasons added as notes.
Gate: Rules
Custom fields
Written to store score, source and routing reason.
Gate: Defined with you first
Controls and testing
People stay in charge of money and records. The system keeps the evidence.
Scoped access
The app asks for the scopes the workflow needs and you can uninstall it at any time. Nothing outside those scopes is reachable.
Test pipeline first
We run on a test pipeline with test records, check the routing against your rules, and only then switch to the live pipeline.
Every change explained
Each write carries its source, rule and time. Overwriting what a rep entered is off by default.
No surprise emails
Agents draft messages. Sending stays with the rep unless you approve a narrow automated case.
Where we stop, and what to expect
- Pipedrive plans differ in what they allow, including automation and API access. We check your plan before scoping.
- We usually don't auto-merge records, and we don't change deal values. A person decides both.
- Enrichment is only as good as its sources, and low-confidence values never replace good ones.
Questions about Pipedrive automation
When should I use Pipedrive's own automations and when an AI agent?
Use Pipedrive's automations for rules that are the same every time. Use an agent when the step needs reading, like a free-text inquiry or a call note. The agent writes fields your automations can then use.
Can AI route and enrich leads in Pipedrive?
Yes. It reads the lead, matches existing people and organizations, fills approved fields and assigns an owner by your rules. Unclear matches go to the owner with the reason.
Does it overwrite what our reps entered?
No, not by default. Human-entered values stay, conflicts are flagged, and each automated change records its source and rule.
How do you connect, with an API token or OAuth?
OAuth 2.0 where we can. Pipedrive documents both, and OAuth gives scoped, revocable access. Access tokens last 60 minutes and we refresh them.
Can it send the won deal to our accounting system?
Yes. When a deal is won, the agent checks the required fields and hands over a packet, or a draft invoice in a system like QuickBooks or Xero. Finance approves before billing.
Other CRM integrations
All integrationsNetSuite, QuickBooks, Xero, Sage Intacct, Sage 100, Sage 300, SAP S/4HANA, SAP Concur, SAP Ariba, Microsoft Dynamics 365 Business Central, Workday, Oracle Fusion Cloud ERP, Coupa, Infor, Acumatica, Zoho Books, Zoho CRM, Pipedrive, HubSpot and Salesforce are trademarks of their respective owners. Scenox Studios is an independent company. Product names appear here only to describe the systems we integrate with, and no affiliation, partnership or endorsement is implied.
Tell us where deals get stuck in your Pipedrive pipeline.
A 30-minute call with an engineer. You will leave knowing what a system could do for that workflow and what it would take to build.
What happens next
- 1
Strategy call
We learn how the workflow runs today and what a good outcome would be.
- 2
Workflow audit
We map the process and measure where a system would save the most time.
- 3
Proposal
A written scope, timeline and fixed price for your first system. No obligation to build.