Pipedrive agents that follow up on every deal
Paste one Pipedrive API token. Qoren registers the webhooks, wakes an agent when a deal, person or activity changes, and gives it CRM tools that cannot touch more than you allow.
Integrations is in early access: Qoren is turning it on account by account. Already have access? Open Integrations
How do I connect Pipedrive to an AI agent?
In Qoren, open Integrations, choose Pipedrive and paste an API token from Personal preferences > API. Qoren checks the token, then sets up the Pipedrive webhooks itself when you pick an event such as Deal added. Give an agent read only or read and write access, and it can look up deals, add notes and schedule activities. Closing or reopening a deal always waits for your approval.
What agents do with Pipedrive
Example jobs, each built only from the events and tools listed further down. Write the agent's rules in plain words; these are starting points, not presets.
For agencies running it for clients
A next step on every new deal, for each client
When a deal lands in a client's Pipedrive, the agent reads it, looks up the contact, writes a note with what it found and schedules the follow-up call, so no lead sits untouched over a weekend.
- Wakes on
- Deal added
- Uses
- Read a deal
- Find a person
- Add a note
- Schedule an activity
Keep stalled deals moving
When a deal changes stage, the agent checks its activities and schedules the next one if nothing is planned. Delivered as a digest, a busy pipeline wakes it once per window instead of on every edit.
- Wakes on
- Deal updated
- Uses
- List a deal's activities
- Schedule an activity
A short debrief on every lost deal
When a deal is marked lost, the agent reads the deal and its activities and adds a note on what happened, which feeds the client's monthly report.
- Wakes on
- Deal lost
- Uses
- Read a deal
- List a deal's activities
- Add a note
For founders running it for themselves
Never lose a lead from your inbox
When a prospect emails the agent's mailbox, it searches Pipedrive for the person, adds them if they are new, and creates the deal, searching first so it does not add a duplicate.
- Uses
- Find a person
- Add a person
- Create a deal
A handoff note when a deal is won
When you win a deal, the agent reads it and writes the onboarding note your team starts from.
- Wakes on
- Deal won
- Uses
- Read a deal
- Add a note
The path one event takes
9 Pipedrive events that can wake an agent
Pick one on an agent's Triggers tab. Each event can arrive on its own, as a digest, or as the latest state of a record, and events that do not match your conditions are logged as Filtered, with no turn and no charge.
| Event | When it fires |
|---|---|
| Deal added | A new deal is created. |
| Deal updated | Any field of a deal changes: stage, value, owner, a custom field. |
| Deal won | A deal is marked as won. |
| Deal lost | A deal is marked as lost. |
| Person added | A new contact person is created. |
| Person updated | Any field of a contact person changes. |
| Organization added | A new organization is created. |
| Activity added | A call, meeting, task or other activity is scheduled. |
| Note added | A note is added to a deal, person or organization. |
11 tools agents can use
Curated Pipedrive tools, not a raw API: each returns only the fields the job needs. A read only grant never gets a write tool, and tools marked Always asks wait for a person's approval whatever the agent's autonomy setting.
| Tool | What it does | Access | Approval |
|---|---|---|---|
| Find a person | Search Pipedrive contacts by name, email or phone. Returns id, name, emails, phones and organization. | Read | None |
| Find an organization | Search Pipedrive organizations by name or address. Returns id, name and address. | Read | None |
| Find a deal | Search Pipedrive deals by title, optionally for one person or organization or by status. Returns id, title, value, status, stage, person and organization. | Read | None |
| Read a deal | Read one Pipedrive deal: title, value, status, stage, pipeline, owner, person, organization, dates and custom fields. | Read | None |
| List a deal's activities | List one deal's activities (calls, meetings, tasks), newest due date first, at most 50. | Read | None |
| Add a note | Add a note to a Pipedrive deal, person or organization (give at least one id). | Write | Per autonomy setting |
| Schedule an activity | Schedule a Pipedrive activity (call, meeting, task) on a deal, person or organization. | Write | Per autonomy setting |
| Add a person | Add a contact person to Pipedrive. Search first so you do not add a duplicate. | Write | Per autonomy setting |
| Create a deal | Create an open Pipedrive deal. Search first so you do not add a duplicate. | Write | Per autonomy setting |
| Move a deal to a stage | Move a Pipedrive deal to another stage (optionally in another pipeline). | Write | Per autonomy setting |
| Close or reopen a deal | Mark a Pipedrive deal won, lost or open again. Always asks a person to approve first. | Write | Always asks |
How connecting Pipedrive works
- 01Make a Pipedrive key with the least access it needs, following the guide below. Only the account owner can connect a tool.
- 02Paste it in Qoren. Qoren checks it before saving: which account it belongs to, what it can do and, where Pipedrive says, when it expires.
- 03Give an agent access, read only or read and write. An agent cannot use a tool it was not given.
- 04Pick the events that should wake the agent. Qoren registers the Pipedrive webhook itself, so there is no URL or signing secret to copy.
Making the Pipedrive key
- 1
Pick the right Pipedrive user
A Pipedrive API token can do everything its user can, and triggers only see what that user can see. Use an admin, or create a dedicated user for Qoren with access to all the deals, people and activities your agents should know about.
- 2
Open Personal preferences, then API
Signed in as that user, open your profile menu in Pipedrive, choose Personal preferences and then the API tab.
Qoren's connect dialog links straight to this page in Pipedrive.
- 3
Copy the token and paste it here
Copy your personal API token and paste it here. Never send it by email or chat.
Connecting a client's account? Send a link
An agency does not need its client's key. Send a connect link instead: it shows your agency's name and the exact permissions to tick, works once, expires after 7 days and can be revoked. The client pastes the key on that page, Qoren encrypts it on arrival, and you only ever see its last four characters. A client's connection is used only by that client's agents. Connect links come with Clients, on the Ultimate, Business and Enterprise plans.
Client connect linksSecurity in plain words
Keys never reach the agent's machine
The Pipedrive key is encrypted at rest with AES-256-GCM and used only inside Qoren's own calls to Pipedrive. It is never written to the agent's environment, and after you connect only its last four characters are shown.
Read only until you say otherwise
Each agent gets read only or read and write access, granted one agent at a time. Pipedrive keys cannot be limited, so Qoren's own tools are what keep a read only agent read only.
Risky actions always ask
In Pipedrive, these always wait for a person's approval, whatever the agent's autonomy setting: close or reopen a deal.
Capped reads and a full audit log
By default an agent reads at most 500 records an hour from one connection. Every call, read or write, lands in the audit log with the agent, the tool and the record ids.
Event data is treated as data
Events reach the agent fenced off as data, with a warning not to follow instructions inside them. For 30 minutes after an agent reads connected data, a Qoren tool that would send it outside your account waits for your approval.
Stored events expire
Qoren keeps event bodies for 7 days on Starter, 30 on Pro, 90 on Ultimate and 180 on Business, then removes them and keeps only the metadata.
Pipedrive limits worth knowing
When you disconnect, Qoren cannot revoke the key at Pipedrive, so it tells you where to delete it. In Pipedrive, open Personal preferences > API and generate a new token. The old token stops working at once.
- A Pipedrive API token can do everything its user can, and webhooks only see what that user can see. Use an admin, or a dedicated user who can see every deal your agents should know about.
- Pipedrive allows 40 webhooks per user. Qoren checks there is room before it adds one and never replaces a webhook you already have.
- Pipedrive deletes a webhook after 3 days of failed deliveries. Qoren's daily check notices and registers it again.
Frequently asked questions
Which Pipedrive user should create the token?
An admin, or a dedicated user created for Qoren with access to all the deals, people and activities your agents should know about. A token carries its user's full rights, and triggers only see what that user can see, so a token from a user with limited visibility misses events.
Can a read-only agent change my Pipedrive data?
No. Pipedrive tokens cannot be limited, so Qoren enforces the level itself: an agent with read only access is never given a write tool, whatever the token could do.
Does my agent ever see the Pipedrive key?
No. Qoren encrypts the key as soon as it arrives and uses it only inside its own calls to Pipedrive. The key never reaches the agent's machine, is never shown again after you connect, and the agent only gets the results of the tools you allowed.
Can an agent close or reopen a deal without asking?
No. In Pipedrive, these tools always wait for a person's approval, whatever the agent's autonomy setting: close or reopen a deal. The approval shows the exact details the agent wants to send.
ApprovalsWhat happens when I disconnect Pipedrive?
Qoren deletes the webhooks it registered, deletes the stored key, pauses the triggers that used it and removes stored event bodies. It cannot revoke a key at Pipedrive, so it shows you where to delete it: In Pipedrive, open Personal preferences > API and generate a new token. The old token stops working at once.
What does the Pipedrive integration cost?
Connecting tools comes with every Qoren plan, with no limit on connections, once Integrations is on for your account. It is in early access for now, turned on account by account. An event that wakes an agent uses credits like any other agent turn, and each trigger has an hourly cap.
Qoren pricingConnect Pipedrive once. Let agents handle the rest.
Integrations is in early access, turned on account by account. Request it and tell us how your agents should use Pipedrive.