Talin and Bullhorn

Yes. Talin pushes candidates and their enriched contact details into Bullhorn, and pulls records the other way so a candidate who already exists in your ATS is matched rather than duplicated. Every message Talin sends and every reply it receives writes back as a note on the candidate.

Yes. Bullhorn fills both halves of the stack: candidate campaigns sync to the ATS side and prospect campaigns to the CRM side, from one Talin workspace. BD activity never lands on candidate records, and each side keeps its own sync switches.

Your choice. Campaign Mapping Settings lets prospect campaigns write either record type, so match it to how your BD team reports in Bullhorn. Candidate campaigns are unaffected and always write to the ATS side.

About five minutes. You pick Bullhorn in Settings → Integrations, fill in your OAuth2 Client ID and OAuth2 Client Secret, choose which events push records and write notes, and the first sync starts on its own. No engineering, no data migration.

Candidates, with the contact details Talin verified. You choose the trigger: every candidate uploaded to Talin, or only the ones whose email or phone number Talin enriched, so your ATS stays free of records that were never reachable.

No. Talin matches on the identifiers Bullhorn already holds before it writes, so an existing candidate gets updated and noted instead of re-created. You can also have Talin pull candidate emails that already exist in your ATS so it never spends a credit re-finding them.

Every event is a switch. Push on upload or on enrichment; add a note when a candidate receives a message, when they reply, or when they enter and leave a campaign; include the full message body in notes or keep them to the headline. Change any of it later without reconnecting.

Syncing stops and nothing is deleted. Records and notes Talin already wrote stay in Bullhorn, and your Talin campaigns keep running. Reconnecting picks the sync back up with your previous settings.