Contacts, deals, outcome write-back.
Integrations
The integration plan, and where each system stands.
In development: HubSpot, Pipedrive, Slack, Zapier · Cal.com: In controlled testing
This page is a build plan, not a catalogue of what runs today: every system below carries a status. An integration here does one of two things: it gives an agent something real to act on (availability, a deal stage, an invoice status), or it takes what the agent produced and files it where your team already looks. None of the five is connected today. The DACH sector systems are the wedge. No dates are set.
The event every integration consumes
POST https://your-endpoint.example/audact
X-Audact-Signature: t=1755264863,v1=hmac-sha256:9f86d081...
{
"event": "call.completed",
"tenant": "acme-dental",
"session_id": "sess_8h2k9d7",
"outcome": "booking_requested",
"outcome_source": "conversation",
"confirmed_by": null,
"receipt_id": "rcpt_01HX7K9M3P4Q5R6S7T8U9V",
"article_50": { "disclosed": true, "clause": "1", "at_turn": 1 },
"fields": { "starts_at": "2026-09-03T09:30:00+02:00", "provider": "dr_meier" }
}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. The authentication code is HMAC-SHA256 over the raw body with your tenant key; verify it before you trust the payload.
How an integration is delivered
- Native integrations: to be configured in the tenant, no code on your side.
- In development: HubSpot, Pipedrive, Slack, Zapier · Cal.com: In controlled testing
- Outbound webhooks with an HMAC-SHA256 authentication code and a 72-hour replay window.
- In development
- Sector systems in DACH: practice management, legal, finance, KYC, e-signature.
- Planned
- Aggregators for the long tail rather than one integration per tool.
- Planned
The list
What connects, and when.
- System
- HubSpot
- What it carries
- Contacts, deals, tickets · outcome write-back
- Status
- In development
- System
- Pipedrive
- What it carries
- Pipeline stages and activities
- Status
- In development
- System
- Cal.com
- What it carries
- Live availability and booking
- Status
- In controlled testing
- System
- Slack
- What it carries
- Compliance alerts per sub-account
- Status
- In development
- System
- Zapier
- What it carries
- Webhook triggers and actions to the long tail
- Status
- In development
- System
- CGM Z1
- What it carries
- Dental practice management, write-back
- Status
- Planned
- System
- DATEV
- What it carries
- Bookkeeping and client records
- Status
- Planned
- System
- lexoffice
- What it carries
- SMB invoicing and receivables
- Status
- Planned
- System
- finAPI
- What it carries
- PSD2 account data across DACH banks
- Status
- Planned
- System
- Medatixx
- What it carries
- German physician practice management
- Status
- Planned
- System
- RA-MICRO
- What it carries
- Law-firm matters and time entries
- Status
- Planned
- System
- Doctolib
- What it carries
- Patient booking and rescheduling
- Status
- Planned
- System
- Skribble
- What it carries
- Qualified electronic signature requests
- Status
- Planned
- System
- IDnow
- What it carries
- Identity verification in-call
- Status
- Planned
Two lists, and they are not the same one
An integration is not an enterprise connector.
This page carries integrations: they give an agent something real to act on (availability, a deal stage, an invoice status) or file what the agent produced where your team already looks. The five named at the top are those, and each has its own page and its own row in the table above.
The enterprise connectors on /connectors are a different thing: they surface Audact governance inside a platform an organisation has already standardised on, so a DPO, a risk team or an Azure administrator does not have to learn a second console. There are four, all planned. Reading one list as the other is how a procurement conversation goes wrong.
Aggregators
Three connections instead of three hundred.
Beyond the sector systems, the plan is to reach the long tail through aggregators rather than one integration per tool: lower total cost of integration, faster coverage, fewer fragile endpoints. All three are planned; no date is set.
- finAPI: PSD2 account data across DACH banks, plus the bridge into DATEV-canonical bookkeeping.
- Codat: one API into Xero, QuickBooks, Sage, NetSuite and the rest of the accounting world outside DACH.
- Merge.dev: unified access to CRM, ticketing, HR and file storage for Enterprise accounts that run something we do not connect to natively.
Also on the list
Evidence into the programme you already run.
Vanta and Drata integrations push Audact evidence into the compliance programme your team already operates, and a knowledge-base sync grounds agent answers in Notion, Confluence or SharePoint. Both are in development; no date is set.
Questions
- What does Planned mean here?
- That we are building towards it and no date is set. It does not mean a signed partnership, a listing, or a pilot with a customer.
- My tool is not on the list.
- Zapier (In development) is the route for most of the long tail. Write to integrations@audact.ai.
- Does an integration cost extra?
- Nothing to order. A connection is scoped inside an applicable paid agreement; integrations are not priced separately.
Or skip the integration entirely
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.
Related
HubSpot Pipedrive Pipeline stages and activities.
Cal.com Live availability and booking.
Slack Compliance alerts per sub-account.
Zapier The general-purpose escape hatch.
CGM Z1 Dental practice management.
DATEV Bookkeeping and client records.
lexoffice SMB invoicing and receivables.
finAPI PSD2 account data across DACH.
Medatixx German physician practices.
RA-MICRO Law-firm matters and time.
Doctolib Patient booking.
Skribble Qualified electronic signatures.
IDnow Identity verification in-call.
Enterprise connectors OneTrust, ServiceNow, Azure (Planned) · MCP (In development).