Skip to main content
Audact
See the offer

Integration · Zapier

The escape hatch for everything not on the roadmap.

Integration · Zapier: In development

In development: if your end-client runs something we do not connect to natively, Zapier would be the route for that case. Audact would expose triggers (call completed, compliance event, dial refused) and actions (start outbound, post a message, create a receipt).

The trigger payload

{
  "event": "call.completed",
  "session_id": "sess_8h2k9d7",
  "outcome": "opted_out",
  "receipt_id": "rcpt_01HX7K9M3P4Q5R6S7T8U9V",
  "article_50": { "disclosed": true, "clause": "1", "at_turn": 1 },
  "sub_account": "acme-dental"
}

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

The same payload the native integrations consume. Map it onto whatever the target app expects.

What it exposes

Would expose triggers: call completed, compliance event, dial refused.
In development
Would add the evidence-exported trigger.
In development
Would expose actions: start an outbound campaign, post a message, create a receipt.
In development
Sub-account scoping, so one Zap would not leak across end-clients.
In development

Setup

Planned setup

In development

  1. Connect using the Audact triggers and actions with your tenant API token.
  2. Paste the API key from your tenant settings.
  3. Build the Zap with Audact on one side and your target app on the other.
  4. Test, turn it on, ship.

Where it fits

A bridge, not a destination.

Zapier is the right answer for the long tail and the wrong answer for anything on the hot path: it adds a hop and it does not run inside the call. Availability lookups, eligibility checks and the governance gate belong on the API. Everything after the call (filing, notifying, reporting) is where a Zap earns its keep.

Questions

Can a Zap start a call?
In development: it would start an outbound campaign, and that campaign would run the eligibility check before a number is dialled.
Is the receipt available in the Zap?
In development: the receipt id would be in the payload. The receipt itself would stay in the Evidence Vault, where its retention rules apply.

Or go direct

Every trigger here is an endpoint underneath. If the hop matters, the API removes it.

See the API

Related