Talin and Loxo

Yes. Talin pushes candidates and their enriched contact details into Loxo, 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. Candidate campaigns write to the ATS side against the Loxo job they were sourced for, and prospect campaigns write BD contacts to the CRM side. Both sync in real time with their own switches.

Pick the job when you build the campaign: Talin pulls your open Loxo jobs into a dropdown, and every synced candidate lands associated with it. Forgot at creation? Associate the job afterwards from Settings and sync.

About five minutes. You pick Loxo in Settings → Integrations, fill in your Agency slug, API Key and Agency ID, 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 Loxo 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 Loxo, and your Talin campaigns keep running. Reconnecting picks the sync back up with your previous settings.