Outbound sales
Apollo finds them, PyAI calls them, HubSpot remembers everything.
Keep Apollo for sequencing; that is what it is good at. PyAI places the calls with answering-machine detection, so your agent only speaks when a human answers, and when the call ends the recap lands as a note on the HubSpot contact. List in Apollo, calls by PyAI, record in HubSpot: three tools each doing the job they are best at, with no one retyping outcomes.
The loop
- 1
Apollo runs the sequence and queues the call task, as it does today.
- 2
PyAI places the call. AMD listens first: voicemail, IVR, or a human, with a confidence score, before your agent says a word.
- 3
The conversation runs with the recap building in the background.
- 4
On call end, Recap completes and PyAI posts the TL;DR, summary, and next steps as a note on the HubSpot contact (matched by CRM field or phone).
- 5
The Apollo integration creates a follow-up task with the full recap on the same contact natively; AMD retries can still flow through Zapier for sequence-level automation.
What it looks like running
One call through the stack
Apollo: sequence "Q3 installers", call task due
PyAI: AMD -> human (97%) -> agent speaks
Recap completes 41s after hangup
HubSpot: note on contact Jane Doe
"Customer asked to reschedule Friday's installation
to next week... Next steps: Confirm by SMS."
Apollo: follow-up task (high priority, due tomorrow)
with the full recap in the noteWhat each tool does here
PyAI
Places the calls, detects humans, writes the recap
Setup order
- 1
Connect HubSpot in the PyAI console (Integrations, HubSpot card) and press Test.
- 2
Connect Apollo (Apollo card) with your API key and task owner user id, and press Test.
- 3
Optional: subscribe AMD decisions to Zapier and point a Zap at Apollo for sequence-level updates (voicemail retries, list moves).
- 4
Load your Apollo call list into the PyAI campaign the same way you dial today, place one test call, and check the three surfaces.
FAQ
Does PyAI replace Apollo?
No. Apollo stays your sequencer and list source. PyAI places the calls, detects who answered, and writes the follow-up task back onto the contact. Each tool keeps the job it is best at.
How do outcomes get back into Apollo?
Two ways. The Apollo integration creates a follow-up call task with the full recap natively, due the next day. For sequence-level automation (retry voicemail, mark contacted, move lists), subscribe AMD decisions to the Zapier integration and drive those steps from a Zap.
What if the HubSpot contact does not exist?
The recap note still posts with the full summary and the call reference, unattached. Nothing is silently dropped, and you can associate it later in HubSpot.
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. Apollo and HubSpot bill you as they do today, unchanged.
Run the outbound sales 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.