- Outbound destinations. When a call completes (a Recap summary finishes, or AMD classifies the call), PyAI delivers it to your tools: Slack messages, Zapier triggers, CRM notes and activities, Zendesk tickets, or a Google Sheets row.
- Inbound call imports. Completed calls from your phone provider flow into PyAI for transcription, Recap summaries, and Trace scorecards. JustCall is live; Aircall, Dialpad, Twilio, and RingCentral are in live certification.
What every integration gives you
- Signed delivery. Outbound deliveries carry an HMAC signature
(
X-PyAI-Signature) and a deterministicIdempotency-Key, so a retried delivery can never post twice downstream. - Retries with visible errors. A failing endpoint is retried with backoff (eight attempts over about twenty minutes). If it still fails, the exact error sits on the integration card in the console — never silently lost.
- Encrypted credentials. Tokens, secrets, and webhook URLs are encrypted at rest and masked on every read. They never appear in delivery payloads.
- A Test button. Every connection can deliver a sample before the first real call, so format and credentials are proven up front.
- No per-integration fees. Integrations are included; you pay only for the Recap or AMD usage you already run.
Pick your guide
Outbound destinations
Inbound call imports
Debugging a delivery? Each guide ends with a troubleshooting section
covering the exact errors you can hit (rejected signatures, unshared
sheets, unmatched contacts, revoked tokens) and how to fix them.