Talin and Mercury ATS

Yes. Talin pushes candidates and their enriched contact details into Mercury ATS, 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. Both campaign types sync, each with its own toggles for when records push and which events write notes, so recruiting and BD activity stay organized the way your Mercury is.

Not if you enable the pull option: Talin reads emails Mercury already holds and enriches only the genuine gaps. Duplicate records are prevented by matching before writing, so existing records update instead of re-creating.

About five minutes. You pick Mercury ATS in Settings → Integrations, fill in your subscription-key, tenant-id and Domain URL, 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 Mercury ATS 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 Mercury ATS, and your Talin campaigns keep running. Reconnecting picks the sync back up with your previous settings.