Pin integration for Atlas
The Pin integration connects Pin’s AI sourcing and outreach platform to the Atlas database. Candidates sourced in Pin arrive in Atlas as records, with the search and outreach context that produced them attached. Replies to outreach, screened CVs and booked interviews land against the same record, so nobody retypes a name. It sits alongside the rest of the Atlas integrations.
Live · Reviewed September 2026
What Pin does
Pin is an AI recruiting platform built around sourcing. Paste a job description and it searches more than 850 million profiles, then returns a ranked shortlist. The ranking is based on fit rather than keyword overlap, and Pin summarizes why each candidate made the list. It also runs automated outreach sequences across multiple channels from a single inbox. Interview scheduling and its own recruiter CRM sit inside the same product. Agencies, internal recruiting teams and founders all run desks on it.
What changes in your day
A researcher finishes a sourcing run on a live role and ends up with a longlist worth keeping. Those candidates go into Atlas as records, carrying the search and the outreach that produced them. There is no export and no pasting into a form. Nobody finds out weeks later that half the longlist only ever existed in another tab. The record also carries the reason a candidate was surfaced, which matters when someone else picks the search up.
Outreach sequences go out on Monday and the replies come back across the rest of the week. Candidates answer at whatever hour suits them. Each reply is tracked against the Atlas record. A consultant covering the desk sees the whole thread instead of a name with no history behind it. Candidate control is easier when the last four messages sit on the record.
Volume roles pull in applications faster than anyone on the desk can read them. Pin screens those inbound CVs before they reach a consultant. What arrives in Atlas is a filtered set rather than the whole postbag. A consultant on that desk opens Atlas to a screened shortlist rather than an inbox nobody has read. Time-to-send moves, because the first hour goes on the shortlist rather than the pile underneath it.
A client asks to see two of the shortlist this week. The interview is booked through Pin, without the email chain that takes longer to agree than the interview runs. The confirmed slot sits on the Atlas record with everything else about that candidate. Nobody has to remember to update the CRM afterwards.
Six months later a similar role opens and the record is still there. The sourcing context, the messages and the outcome sit with it. That is the difference between a database of names and a database a consultant can work. Someone inheriting the desk gets the history instead of a starting position.
How to turn it on
Turning the connection on takes an account with Pin and admin rights in your Atlas workspace. Those are the two requirements on either side. Once it is enabled, sourcing, outreach, CV screening and interview scheduling in Pin write through to the Atlas database. Teams already running Pin carry on working in Pin. What changes is where the output lands, and how much of it a consultant has to copy across by hand. Ask the Atlas support team to enable it for your account. They will confirm what is needed for your setup.
Anyone comparing more than one tool will find Recruitcha and Talin written up the same way.
Pin FAQ
Is the Pin integration available in Atlas now?
Yes. The connection between Pin and Atlas is live. Candidates sourced and contacted in Pin land in the Atlas database with their context attached. Ask support to enable it on your account.
Which parts of Pin connect to the Atlas database?
Sourcing, outreach, CV screening and interview scheduling all connect. Candidates found in Pin are created in Atlas and outreach activity is tracked against the record. Screened applicants arrive filtered, and booked interviews appear on the candidate record.
Do candidates sourced in Pin have to be added to Atlas by hand?
No. That is the point of the integration. Candidates move from Pin into Atlas without manual data entry. A researcher does not export a list or paste names into a second system. The record arrives with the context that produced it.
Where do replies to a Pin outreach sequence show up?
Replies are tracked against the Atlas record for that candidate. A consultant picking the desk up sees what was sent and what came back. There is no separate inbox to cross-reference before making a call.
Can Pin screen inbound CVs before a consultant sees them?
Yes. Inbound CVs are screened in Pin before they reach a consultant. The applications landing in Atlas have already been filtered against the role. On a high volume desk, that removes the first read through every application.
Do we still need a Pin account to use the integration?
Yes. The integration connects two products rather than replacing one of them, so a Pin subscription stays in place alongside Atlas. Sourcing and outreach still happen in Pin, and Atlas becomes the database that holds the result.
