Pipedrive

Connect Pipedrive with your own OAuth app so an agent can add notes and read a person's activity during a call.

What you will achieve

An agent will be able to add notes in Pipedrive and read a person's activity.

Overview and use cases

Add a note about the call to a person, deal or lead.
Review a person's past activities before replying.

Limitation. Pipedrive has no ticket object, so tickets are unavailable. Creating a lead from a call is not offered as an agent tool for Pipedrive, because a Pipedrive lead must hang off a person or organisation the caller cannot supply.

Prerequisites

A Pipedrive account, and a Pipedrive developer app (OAuth) in its Developer Hub.

External account setup (in Pipedrive)

Pipedrive controls these screens. Pipedrive's guide: Core API concepts.

Create an OAuth app in Pipedrive's developer area.
Set its callback URL to the redirect URL shown in Phynxa's Connect dialog.
Grant the scopes below, then copy the Client ID and Client secret.

Connect it in Phynxa

Integrations, Connect on Pipedrive.
Paste the Client ID and Client secret.
Continue to Pipedrive and approve. The card shows Connected.

Scopes requested: deals:full, contacts:full, activities:full, leads:full. Phynxa uses Pipedrive's API v2. The API address contains your company's own domain, which Pipedrive returns with the token.

Use it in a call

Action	What it does	Runs
Add note	Adds a note to a person, deal, lead or organisation (give it the id).	In the background
Fetch customer history	Lists a person's activities. It needs a person id.	Waits
Update contact	Changes a contact's name, email, phone or company; only what you give is changed. Needs the contact's id from a history lookup.	In the background
Create task	Creates a follow-up task for your team (subject, optional body and due_date like `2026-11-02`), linked to a contact when you give its id.	In the background

Test it

Test connection on the card. Then ask an agent in Chat to add a note and check the person in Pipedrive.

Expected result

The note appears on the Pipedrive record and the card counts a success.

Troubleshooting

Redirect or client error. The callback URL must match exactly.
"A person_id is needed." History needs an id the agent usually lacks.
403. The app lacks a scope; add it and Reconnect.

Security and credentials

Client secret stored encrypted. Remove forgets the connection; uninstall the app in Pipedrive to revoke it.

Something here does not match what you see in the dashboard? Let us know.