Live today
- Bullhorn — SyncTalent.ai connects to Bullhorn through Merge.dev — reading requirements and candidates, writing submissions back. A connector, not a migration.
- Merge.dev — SyncTalent.ai uses Merge.dev as its unified ATS connector layer — one integration surface, normalised objects, and no ATS credentials stored on our side.
On the roadmap
No committed dates, because we do not have any. Connectors get built when a design-partner agency needs one and will test it against live requirements.
- JobDiva — A JobDiva connector is on the SyncTalent.ai roadmap and is not available today. Bullhorn via Merge.dev is the live ATS path. Here is what a JobDiva sync would cover.
- Ceipal — A Ceipal connector is on the SyncTalent.ai roadmap and is not available today. Bullhorn via Merge.dev is the live ATS path. Here is what a Ceipal sync would cover.
What needs no ATS at all
The ingestion agent takes requirements straight from email, Telegram, WhatsApp, Dice, Slack, and Teams. Vendor-blast dedup into canonical requirements, bench-first shortlisting, outreach, and AI voice screening all run without an ATS connector. What the connector adds is automatic submission write-back and a single source of candidate truth.
Where to go next
How it works covers the pipeline end to end. SyncTalent.ai vs Bullhorn automation answers the question most agencies running Bullhorn actually have. And if you run something not listed here, tell us.