Skip to main content
connic

Pipedrive

Run connic agents when deals, leads, people or organizations change in Pipedrive. Agents add their results as notes to the record.

Modes
Inbound, Outbound
Set up in
Dashboard or connectors/*.yaml
Documentation
Pipedrive docs
Publisher
By connic

React to changes in your pipeline

When a record of the connector's type is created, updated or deleted, every agent linked to it starts. An outbound connector on the same Connection adds the result as a note.

Pick records and an event
Deals, leads, people, organizations, activities or notes, each when created, updated, deleted, or all three.
Several connectors per company
Each connector has its own webhook, so you can watch new deals with one and new leads with another, or use one per environment.
No loops, no double runs
Changes made through the API, like the agents' own notes, are skipped, and an event that Pipedrive delivers again doesn't start a second run.
  1. Something changes in Pipedrive

    Someone adds a deal, moves it to another stage, or creates a lead.

    deal.create
  2. connic checks and confirms the event

    It checks the webhook's password and answers Pipedrive well within its 10 seconds.

    Basic auth
  3. Linked agents start

    The run gets the record type, the action, the record's ID, title and link, and the full record.

    lead.change
  4. The result lands on the record

    An outbound connector on the same Connection adds a note to the deal, lead, person or organization.

One API token, the webhook is registered for you

You enter the company domain and an API token once. Saving an inbound connector registers its webhook in Pipedrive, and deleting the connector removes it.

Your token, your company
The token belongs to a user in your Pipedrive company. Creating a new token in Pipedrive replaces the old one.
Only what the user can see
Pipedrive sends the records the token's user can see, so the user's visibility settings also limit what agents get.
Nothing to copy back
connic generates the webhook's password and checks every delivery with it. You find the webhook in Pipedrive's settings under Tools and apps.
pipedrive-webhook.json
{
  "subscription_url": "https://connect.connic.co/pipedrive/<connector-id>",
  "event_object": "deal",
  "event_action": "create",
  "version": "2.0",
  "http_auth_user": "connic",
  "http_auth_password": "<generated by connic>"
}

Add notes to deals, leads, people and organizations

An outbound Pipedrive connector adds the agent's output as a note, whether the run starts from Pipedrive or from another connector or a schedule.

Routing
A deal_id, lead_id, person_id or org_id in the output wins. Without one, a run started from Pipedrive on the same Connection adds the note to that record.
Three ways to send
Send after every completed run, give the model a tool to call, or call send_connector from middleware when your code decides.
Rate limits handled
When Pipedrive rate-limits a note, connic waits and sends it again.
output.json
{
  "body": "Acme runs 40 seats today and asked about SSO. Next step: send the security overview."
}
connector-payload.json
{
  "body": "Follow-up call booked for Thursday.",
  "deal_id": 128
}

Where Pipedrive fits

Pick a setup to see what reaches the agent and what it adds to Pipedrive.

Someone adds a deal, and the agent notes what it knows about the company.

New deal
Inbound Pipedrive
account-research
Note on the deal
pipedrive-payload.json
{
  "event": "deal.create",
  "record_id": "128",
  "title": "Acme rollout",
  "url": "https://acme.pipedrive.com/deal/128",
  "change_source": "app"
}
output.json
{
  "body": "Acme: 1,200 employees, EU only. Buys through procurement, budget cycle in Q1."
}

A new lead comes in, and the agent notes whether it fits and what to do next.

New lead
Inbound Pipedrive
lead-qualifier
Note on the lead
pipedrive-payload.json
{
  "event": "lead.create",
  "record_id": "b1810230-6c0d-11ed-9826-a53d0eb706a5",
  "title": "Northwind, 200 seats",
  "url": "https://acme.pipedrive.com/leads/inbox/b1810230-6c0d-11ed-9826-a53d0eb706a5",
  "change_source": "app"
}
output.json
{
  "body": "Fits: 200 seats, EU, asked for a trial. Suggest a demo with the sales team."
}

A deal changes, for example its stage, and the agent notes what is still open.

Updated deal
Inbound Pipedrive
deal-coach
Note on the deal
pipedrive-payload.json
{
  "event": "deal.change",
  "record_id": "131",
  "title": "Globex renewal",
  "url": "https://acme.pipedrive.com/deal/131",
  "change_source": "app"
}
output.json
{
  "body": "Moved to Negotiation. Open points: price per seat and the SLA."
}

Your contact form sends an inquiry, and the agent sums it up on the person in Pipedrive.

Contact form
Inbound webhook
inquiry-summary
Note on the person
form.json
{
  "person_id": 2207,
  "name": "Dana Weber",
  "company": "Initech",
  "message": "We need SSO and an EU data location. Can we talk this week?"
}
output.json
{
  "body": "Asked for SSO and EU hosting, wants a call this week.",
  "person_id": 2207
}

Pipedrive FAQ

Your Pipedrive company domain and a user's API token, which you find under Personal preferences, API. Connectors act as that user and see the records that user can see.

From the user the API token belongs to. A Pipedrive user just for your agents keeps their notes apart from your team's.

No. Saving an inbound connector registers a webhook for its records and event, with a password connic generates, and deleting the connector removes it.

Yes, with type: pipedrive, the records and event, and the name of a Pipedrive Connection that holds the company domain and API token.