AiOneChat
Pipedrive

One token. Wired both ways.

Paste a Pipedrive API token into AiOneChat and the connection builds itself: we verify it, register the webhooks on your account from this side, and then deals start messaging customers while conversations file themselves on the person.

Connect PipedriveWhat you actually do
  • No OAuth app
  • Webhooks installed for you
  • Both directions
Your side of it

Three minutes, and none of it in Pipedrive.

Everything except copying the token happens on our side. You never open Pipedrive’s webhook settings.

  1. 1in Pipedrive

    Copy your token

    In Pipedrive: your avatar → Personal preferences → API. One value, and it is the only thing you fetch from over there.

    452d8c••••••••a1
  2. 2in AiOneChat

    Paste it and connect

    Open the Pipedrive card in your dashboard and paste it. We check it against your account before saving anything.

    Connected+ 2 webhooks installed
  3. 3in AiOneChat

    Pick what fires

    Switch on the events that should message a customer and the mirroring that should write notes back. Each half is separate.

    deal wonchats → notes
Both ways

The deal messages the customer. The conversation joins the deal.

Three things leave Pipedrive and become a WhatsApp message. What they write back becomes a note on the person. Both lanes are open at once.

PPipedrive
Festive order · Desai TradersDeal wonpipedrive/deal/wonStage movedpipedrive/deal/stagePerson addedpipedrive/person/created On the person“Perfect, I’ll take it.”
Pipedrive → WhatsAppDeal wonStage movedPerson added
WhatsApp → Pipedrivetheir reply
APAnjali Patel
Your order Festive order is confirmed. Total ₹24,000.name · deal · valueHi Anjali, your order is now at Proposal.name · deal · stage · valueHi Anjali, thanks for your interest in Desai Traders.name · organisationPerfect, I’ll take it.

Each direction has its own switch. Turn the outbound events off and the notes keep arriving; turn the notes off and the events keep firing.

Three layers

The guard Pipedrive does not give you.

HubSpot has an upsert you can key on a property. Pipedrive has none, so the protection has to live on our side - and one layer is not enough when messages arrive together.

1

The id we already hold

The first time we create a person for a number, its id is written onto that contact. Every message after that goes straight to it - Pipedrive is not asked at all.

2

A short memory

The same id is kept in memory for a few minutes, so a burst of messages does not even hit the database, let alone Pipedrive.

3

One at a time, per number

Messages for the same number queue behind the first. Three arriving together make one lookup and one create, not three.

The loop

Filing a contact should not message them.

And it does not message people for its own filing.

Writing a person into Pipedrive makes Pipedrive announce that a person was created - back to us. Left alone, every contact we filed would send that customer a template, because we wrote their name down. We recognise our own handiwork and drop it.

We file the contactPipedrive tells us about it

skipped · this person was created by our own contact sync

Ready when you are

Let the pipeline do the talking.

Paste one API token. We register the webhooks on your account, and you pick which events message a customer.

Start freeRead the guide