Integrations
Your calls already end with an outcome. Now the outcome lands where your team works.
Summaries as CRM notes, support tickets with the write-up done, Slack posts the moment a call ends, a trigger for your whole Zapier account, and full call imports from your phone provider. Every delivery is signed, retried, and visible, so the Friday CSV export and the copy-paste recap both die here.
Find your integration
15 of 15 integrations
HubSpot
Every completed call becomes a note on the right contact.
See how it worksSalesforce
Recap writes back to the record your team actually works in.
See how it worksPipedrive
A done call activity on the right person, every time.
See how it worksZoho CRM
Call notes on the contact, in any Zoho data center.
See how it worksApollo
Every completed call becomes a follow-up task on the Apollo contact.
See how it worksClay
Every completed call becomes a row in your Clay table.
See how it worksZendesk
Every call opens a ticket with the summary already written.
See how it worksSlack
The call summary, in the channel where your team lives.
See how it worksZapier
Every completed call, a trigger for your whole Zapier account.
See how it worksGoogle Sheets
Every completed call becomes a row. No CRM required.
See how it worksTwilio Voice
Your Twilio calls, transcribed, summarized, and scored.
See how it worksRingCentral
RingCentral calls into Recap and Trace, with the webhook set up for you.
See how it worksJustCall
Your JustCall calls, transcribed, summarized, and scored.
See how it worksAircall
Aircall recordings and transcripts into Recap and Trace.
See how it worksDialpad
Dialpad hangups, recordings, and transcripts into PyAI.
See how it worksStack playbooks
Two or three tools each, wired together by the integrations above. Pick the shape of your team, follow the playbook, and the loop closes itself.
Outbound sales
Apollo finds them, PyAI calls them, HubSpot remembers everything.
Growth ops
Clay builds the list, PyAI works it, Slack watches it happen.
Support desk
Every JustCall call, scored and written up in Zendesk.
Ops without a CRM
No CRM? Every completed call becomes a row.
AI voice agent for your platform
Keep your CPaaS or phone system and add AI-answered calls on top: forward chosen numbers to PyAI, or integrate via API. Pick your platform for the two-path playbook.
CPaaS
Contact center
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.
What every connection gives you
- Console setup in minutes, no code
- Test delivery before the first real call
- Per-event subscriptions per connection
- Verified deliveries that can't post twice
- Retries with visible errors, never silent loss
- Credentials encrypted and masked
- No per-integration fees
FAQ
What do PyAI integrations cost?
They are included. Outbound deliveries (Slack, Zapier, CRM notes, Zendesk tickets) carry no per-destination or per-delivery fee, and phone-provider imports bill like any other Recap or Trace usage. You pay for the call intelligence you already run, never for the plumbing.
What happens when my endpoint is down?
PyAI retries the delivery with backoff, eight attempts over about twenty minutes. If it still cannot deliver, the error and the payload are preserved and visible on the integration card in the console, so you can fix the endpoint and replay instead of losing the event.
Is this a two-way sync with my CRM?
No, and that is deliberate. PyAI writes one-way, per-call records (notes, activities, tickets, messages) into your tools after each call. It does not read or modify your pipelines, stages, or contact properties.
How do I know a delivery really came from PyAI?
Every outbound delivery carries proof it is really from us (the X-PyAI-Signature header, verifiable with your org webhook signing secret) and a unique receipt id, so a retry can never post the same call twice.
Which phone systems can I import calls from?
JustCall is live today: completed calls import with recordings for transcription, Recap summaries, and Trace scorecards. Aircall, Dialpad, Twilio, and RingCentral are rolling out and open on the integrations page as each is ready.
Do I need to write code to connect an integration?
No. Every connection is configured in the console with a token, webhook URL, or OAuth credentials from the tool you are connecting. A Test button on each card proves the delivery before the first real call fires it.
Connect your first integration in minutes.
An instant sandbox key lets you test every delivery without billing. Create an account when you want saved projects, and fund a live key for production traffic.
Agents is live in beta. Sandbox keys have daily limits and never touch billing.