Growth ops
Clay builds the list, PyAI works it, Slack watches it happen.
Clay does what Clay does: enrich targets and score them. PyAI runs the calls against the result and posts every outcome (recap cards for conversations, AMD cards for verdicts) into a Slack channel, so the whole team watches the campaign without opening a dashboard. Outcomes flow back into the Clay table through the Zapier integration, closing the loop on the list that started it.
The loop
- 1
Clay enriches and scores the target list, as it does today.
- 2
PyAI runs the calls with AMD, so voicemail never burns agent time.
- 3
Every completed call posts a recap card to Slack: TL;DR, summary, next steps.
- 4
Every AMD verdict posts a compact card: answered by, confidence, reason.
- 5
The Clay integration appends the outcome row to the table directly (webhook source) for the next enrichment pass; Zapier stays for fancier multi-step flows.
What it looks like running
What the channel sees during a campaign
:clipboard: Call recap ready
*Customer asked to reschedule Friday's installation.*
Next steps: Confirm the new slot by SMS.
:telephone_receiver: AMD decision
Answered by: voicemail (92%) - Reason: carrier greeting
Session: q3-installers - Zapier: logged to Clay, retry FridayWhat each tool does here
PyAI
Runs the calls and the recaps
Setup order
- 1
Connect Slack in the PyAI console and subscribe it to both events (recaps and AMD decisions).
- 2
Connect Clay (Clay card) with your table's webhook source URL and press Test; the row columns are the table's own fields.
- 3
Export or sync the Clay list into your PyAI campaign.
- 4
Run a small batch and watch the channel and the table: recap cards, verdict cards, and rows should tell the whole story without opening a dashboard.
FAQ
Is there a native Clay integration?
Yes, delivered through Clay's webhook table source (their public API is read-only for tables). Rows append directly from PyAI with one column per field. Zapier remains for multi-step flows that fan one call out to several tools.
Can different campaigns post to different channels?
Yes. Create one Slack connection per channel, each with its own event subscription, and route campaigns by their session label through Zapier filters.
What does the Slack card actually show?
Recap cards carry the TL;DR, summary, next steps, and call reference. AMD cards carry the verdict, confidence, decision time, and reason. Both are formatted for scanning, not for clicking through.
What does this stack cost on the PyAI side?
The integrations are included; you pay for the calling and the Recap or AMD usage you run. Clay and Slack bill you as they do today.
Run the growth ops stack on PyAI.
An instant sandbox key lets you test every leg 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.