Talin Crelate

Talin and Crelate

Seamlessly sync your Talin activity with Crelate.

What's inside

What flows between Talin and Crelate

Contacts create themselves

Candidates Talin sources land in Crelate with their verified email and phone number attached, matched to the record you already hold, never duplicated onto a new one.

Activity logs sync

Every email, InMail, connection request, and SMS Talin sends writes back as a note on the candidate, and so does every reply. The ATS timeline stays the whole story.

Campaign status in your ATS

Recruiters who live in Crelate can see which campaign a candidate is in and when they entered or left it, without opening Talin.

You choose every trigger

Push on upload or only once a contact is enriched, note on send or only on reply, include message bodies or keep notes to the headline. Each one is its own switch.

How to set up

Connect Crelate in four steps

1 –
Select integration
2 –
Connect your account
3 –
Map your fields
4 –
Start syncing

Pick Crelate from the list

Open Settings → Integrations in Talin and choose Crelate under ATS. One workspace can carry an ATS and a CRM at the same time, so this slot is only half the stack.

Paste your API token

Talin hands off to Crelate to authorize the connection. Paste your API token, authorize, and you land back in Talin connected.

Decide what syncs, and when

Choose which events push a candidate to the ATS and which write a note: on send, on reply, on entering a campaign, and on which channel. Nothing moves until you say so.

The first sync runs itself

Crelate shows as connected and Talin starts writing. Change any switch later, or disconnect, without touching the records and notes already in your ATS.

IT
Settings
Members
Rules
Integrations
Billing
Campaign mapping settings
ATS
Choose your ATS provider from the list below to connect it to Talin.
Bullhorn
Crelate
JobAdder
JobDiva
Lever
Loxo
Mercury ATS
PCRecruiter
RecruitCRM
Recruiterflow
TrackerRMS
Zoho Recruit
Top Echelon
CRM
Sync prospects with CRM as:
Leads
Choose your CRM provider from the list below to connect it to Talin.
Bullhorn
HubSpot
JobAdder
JobDiva
Loxo
Microsoft Dynamics 365 Sales
RecruitCRM
Recruiterflow
Salesforce
TrackerRMS
Top Echelon
Authorize Access
talin.ai is requesting access to your Crelate account
API token
Authorize
Cancel
EnglishFrançaisEspañolDeutschPortuguêsItaliano简体中文हिंदी
IT
Campaign mapping settings
ATS
Crelate CONNECTED
Hide settings
Sync settings
Push candidate to ATS when:
they are uploaded to Talin
their email or phone number is enriched
Add note to candidate when:
they receive a message from Talin via
any channel
they reply to a message sent from Talin via
any channel
Add notes and create candidates as individual users
Include message and reply content in notes
Pull candidate emails that already exist in your ATS into Talin
General settings
Add note to candidate when added to and removed from an active Talin campaign
Disconnect
IT
Settings
Members
Rules
Integrations
Billing
Campaign mapping settings
ATS
Crelate CONNECTED
Settings
CRM
Sync prospects with CRM as:
Leads
Choose your CRM provider from the list below to connect it to Talin.
Bullhorn
HubSpot
JobAdder
JobDiva
Loxo
Microsoft Dynamics 365 Sales
RecruitCRM
Recruiterflow
Salesforce
TrackerRMS
Top Echelon
Partner specifics

The Crelate details

Good to know

Crelate takes both sides of the desk: candidate campaigns sync as ATS records, prospect campaigns as Leads (the default) or Contacts, whichever your pipeline reports on.

Candidate campaigns link to a Crelate job at creation. Talin pulls your open positions into the campaign builder, and you can associate or re-associate later from Settings.

An "exclude contacts with activity in Crelate" rule can skip anyone your team already touched within a lookback window you set, so two recruiters never chase the same person.

FAQ

Crelate integration, answered

Yes. Talin pushes candidates and their enriched contact details into Crelate, 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 job they were sourced for, and prospect campaigns write as Leads or Contacts, your choice. Both run from one Talin workspace with their own sync switches.

Yes. Turn on the exclude rule and Talin skips anyone with Crelate activity inside a lookback window you configure, 30 days for example, so campaign imports never collide with live conversations.

About five minutes. You pick Crelate in Settings → Integrations, paste your API token, 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 Crelate 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 Crelate, and your Talin campaigns keep running. Reconnecting picks the sync back up with your previous settings.

Eliminate 90% of your ATS data entry.