Skip to main content
Audact
See the offer

Integration · Pipedrive

Deals move because the call moved them.

Integration · Pipedrive: In development

In development: Audact would create a Pipedrive activity for every call and advance the deal on the outcome: qualified, booked, lost, opted out. The Article 50 receipt and the transcript reference would land on the person record. A deal entering a stage could fire an outbound campaign the other way, so the CRM stays the source of truth and the chain stays intact.

The activity Audact logs

POST /v1/activities
{
  "subject": "Audact call — booked",
  "type": "call",
  "done": 1,
  "deal_id": 4711,
  "person_id": 8123,
  "note": "outcome=booked · receipt=rcpt_01HX7K9M3P4Q5R6S7T8U9V · art50=disclosed@turn1"
}

Worked example. Acme GmbH and Nova Industries are fictional; no customer data appears here.

The receipt id in the note is enough to pull the whole chain back out of the Evidence Vault later.

What it does

Would log one activity per call, with the outcome and the receipt id.
In development
Stage transitions would be driven by agent outcomes rather than by hand.
In development
A deal entering a stage could trigger an outbound campaign.
In development

Setup

Planned setup

In development

  1. Generate a Pipedrive API token and paste it into the Audact integration.
  2. Map Audact outcomes to your pipeline stages.
  3. Choose which activity types and custom fields the agent may write.

Questions

Can the agent move a deal backwards?
In development: only if you map an outcome to an earlier stage. The mapping would be yours; the integration would not invent transitions.
What is written on a call that never connected?
In development: the planned write-back is an activity with the reason (no answer, blocked by eligibility, voicemail) and a receipt for the eligibility decision where there was one.

The same write-back, without an integration

Every integration will be built on the same six endpoints. They run inside the managed platform; no public API is served on api.audact.ai yet, apart from the published Merkle roots.

See the API

Related