PyAI x Slack
The call summary, in the channel where your team lives.
No more “did anyone listen to that call?” in the channel. The answer posts itself: a formatted Slack message with the TL;DR up top, the summary, next steps, and call metadata, the moment a Recap completes. AMD decisions post their own card with the verdict and confidence. Different channels can subscribe to different events.
- Status
- Live
- Direction
- PyAI to Slack
- Setup
- Console, no code
- Cost
- Included
What lands in Slack
A formatted message, readable at a glance: the TL;DR leads, then the summary, next steps, and the call reference. AMD posts a compact card with the verdict, confidence, and reason.
The message after a rescheduling call
:clipboard: Call recap ready
*Customer asked to reschedule Friday's installation to next week.*
Call: call_8fK2mQ9xR4 Status: completed
Pack: support_v1 Customer: +1 (555) 123-4567
The customer called to move their appointment. The agent offered
Tuesday or Wednesday morning; the customer chose Wednesday 9-11am.
*Next steps*
Confirm the new slot by SMS and update the calendar invite.Setup, end to end
- 1
In Slack, create an incoming webhook for the channel you want (or reuse one).
- 2
In the PyAI console, open Integrations and choose Slack, then paste the webhook URL and pick your events.
- 3
Press Test and watch the sample message land in the channel.
- 4
From the next completed call, summaries post automatically. Add another connection for a second channel.
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
Can different channels get different events?
Yes. Create one connection per channel, each with its own incoming webhook URL and its own event subscription. A common split: recaps to the team channel, AMD outcomes to the outbound-ops channel.
What exactly does the message include?
The TL;DR, the full summary, next steps, the call id, status, pack, and customer number when present. AMD messages carry the verdict, confidence, decision time, and reason instead.
Is the Slack webhook URL safe with PyAI?
The URL is the credential, and it is treated like one: encrypted at rest, masked on every read, and only ever posted to Slack's own hooks.slack.com host.
What does the Slack integration cost?
It is included with your Recap or AMD usage. There is no per-message or per-channel fee from PyAI.
Connect Slack to PyAI today.
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.