Skip to main content
Audact
See the offer

Integration · HubSpot

Every call lands on the contact record.

Integration · HubSpot: In development

In development: Audact would read the contact and deal before the call so the agent knows who it is talking to, and would write back after it: outcome, transcript reference and the receipt for the Article 50 disclosure. A HubSpot workflow could go the other way and start an outbound campaign, with the evidence chain stitched across both directions.

What Audact writes back

PATCH /crm/v3/objects/contacts/{contactId}
{
  "properties": {
    "audact_last_outcome": "booking_requested",
    "outcome_source": "conversation",
    "confirmed_by": null,
    "audact_last_call_at": "2026-08-15T10:14:23Z",
    "audact_receipt_id": "rcpt_01HX7K9M3P4Q5R6S7T8U9V",
    "audact_article_50_disclosed": "true",
    "audact_transcript_ref": "sess_8h2k9d7"
  }
}

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

outcome is what was requested in the call; confirmed_by stays null until the system of record confirms it.

What it does

Would create or update the contact on every call and attach the transcript reference.
In development
Would write the outcome (booked, qualified, opted out, escalated) onto the deal.
In development
Inbound HubSpot workflows could start an outbound Audact campaign.
In development

Setup

Planned setup

In development

  1. Connect HubSpot from your Audact tenant: API token or the app authorisation flow.
  2. Map Audact outcome fields to HubSpot properties, or accept the five defaults.
  3. Choose which objects the agent may write to: contacts, deals, tickets.

Questions

Does the transcript itself go into HubSpot?
In development: a reference would. The transcript would stay in the Audact tenant under its retention policy, which keeps an erasure request answerable in one place instead of two.
What if the caller opts out?
In development: the outcome property would record it, and the eligibility check (In controlled testing) would block the next dial to that number.

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