Skip to content
All integrations
Coming soonPhone providersImports calls

PyAI x Dialpad

Dialpad hangups, recordings, and transcripts into PyAI.

The Dialpad importer is rolling out now. When it opens for you, completed calls (with Dialpad's own transcripts when they exist, our transcription when they do not) import into PyAI for summaries and QA, verified as really from Dialpad on every delivery.

Status
Rolling out
Direction
Calls into PyAI
Setup
Console, no code
Cost
Included

What will land in PyAI

The same per-call record as the other providers: transcript, Recap summary, Trace scorecard, stable call id. Dialpad's three event types coalesce into the single call they describe.

Planned import flow

Dialpad hangup / recording / call_transcription (HS256 JWT)
  -> recording fetched via the official Dialpad API
  -> transcript -> Recap summary -> Trace scorecard

Where it stands

  1. 1

    We are proving the importer with a real Dialpad account right now.

  2. 2

    When it opens, you will connect with a Dialpad API key (recordings export scope) and a webhook secret you choose.

  3. 3

    Watch the integrations page in the console; the card opens the day it is ready.

Built into every connection

Delivery you can prove

Verified, and never twice

Every delivery carries proof it is really from us (the X-PyAI-Signature header, an HMAC your tools can verify) and a unique receipt id (the Idempotency-Key), so a retry can never post the same call twice.

Retried, then shown to you

If your endpoint hiccups, we retry with backoff (eight attempts over about twenty minutes). Still failing? The exact error waits on the integration card in your console, not in a log you never read.

Your credentials stay yours

Tokens, secrets, and webhook URLs are encrypted at rest and masked everywhere. They never appear in the messages we send.

Included, no extra fees

Integrations come with your Recap or AMD usage. There is no per-connection or per-delivery charge.

FAQ

When does the Dialpad importer open?

Soon. We are proving it with a real Dialpad account first (signed deliveries, recording export, one clean record per call, and a disconnect test), then it opens for everyone.

Why does Dialpad need a webhook secret I choose?

Dialpad signs every delivery with the secret on the subscription, and PyAI verifies that signature on every event. The secret is what proves the delivery is really Dialpad's.

Can I get notified when it opens?

Yes. Contact us from the integrations page and mention Dialpad; we will flag your account for the rollout.

Dialpad is almost here.

It is rolling out now. Grab a sandbox key and the rest of the platform while you wait; the card opens in the console the day it is ready.

Agents is live in beta. Sandbox keys have daily limits and never touch billing.