Basic Setup – can be completed independently by following the step-by-step guide.
Talos360 Core Data has been setup as an integration within Talos so you are able to export the core data of candidates, as well as any documents associated with a candidates application if needed.
Learn how to setup Talos360 Core Data within your ATS, so you can export candidates directly into your system.
Note: you will need access to the Integrations Management administration permission to setup the integration
Setup
Required Information
API URL
Username
Password
Information: this guide can be used to setup Talos360 Core Data or Talos360 Core Data with Documents.
For the purpose of this guide, 'Talos360 Core Data' was used.
Setting Up Talos360 Core Data
Go to the Talos Marketplace and find the 'Talos360 Core Data' or 'Talos360 Core Data with Documents' integration and click on 'Connect':
Click on 'Enable this Integration' and complete the required fields and click on 'Save' to link the integration with your ATS:
Once the details have been saved, the integration tile will be updated on the home page of the Integrations to show this is connected:
Additional Setup
Please see our 'HR Connect - Additional Setup' guide for further information on additional configuration options and linking your HR Provider to your ATS workflows.
Further Information
The Core Data integration has been created within Talos so candidates information, such as Personal Details, Job Post Information and Offer Details can be transferred to a location external to Talos.
Additional information can also be transferred from Talos, if these are being utilised within the system, including:
ATR
DocuSign
Data Capture answers
Right to Work (completed via Trust ID via Talos)
The exported data can be used to transfer candidate information so this can be held on file external to the ATS as part of any GDPR requirements, or to transfer information into a 3rd party system (such as HR platforms).
Data Structure
Please see the file 'Core Data with Documents - Example Payload Data' for all of the data that is included with Core Data and the format the data is submitted in.
Transferred Fields
Please see the below table which shows what fields are transferred as part of the Core Data export and where this information is populated from in Talos.
Any fields which have been highlighted in the table below are mandatory and must be included for a submission to be successful.
Field Name | Talos Location | Description |
ApplicantId | Applicant | Automatic ID that is allocated to the applicant when they apply for a vacancy |
Applicant | Email address of the applicant | |
Date Received | Applicant | Date the applicant applies to the vacancy |
FirstName | Applicant | First Name of the applicant |
Surname | Applicant | Surname of the applicant |
Source Value | Applicant | Source the applicant has applied from - Automatically allocated on application |
Phone | Applicant | Home telephone number of the applicant |
Street | Applicant | Address line 1 of the applicant - House Name/Number & Street |
Municipality | Applicant | Address line 2 of the applicant - Town/City |
Region | Applicant | Address line 3 of the applicant - County |
Country | Applicant | Address line 4 of the applicant - Country |
Postcode | Applicant | Postcode of the applicant |
Current Company | Applicant | Current company of the applicant |
MobileNumber | Applicant | Mobile telephone number of the applicant |
JobPostId | Job | Automatic ID that is allocated to the job when it is posted |
JobReference | Job | Job reference used when the job is posted |
InternalReference | Job | Internal job reference that is used when the job if posted - If used |
JobTitle | Job | Job title set when the role is posted |
Location | Job | Location used when role is posted - Town/City |
Country | Job | Location used when role is posted - Country |
County | Job | Location used when role is posted - County |
CurrencyCode | Job | Currency code used when role is posted |
PostCode | Job | Location used when role is posted - Postcode |
SalaryFrom | Job | Salary from used when the role is posted |
SalaryTo | Job | Salary to used when the role is posted |
SalaryType | Job | Salary type code used when role is posted |
SalaryReplacement | Job | Salary text replacement used when role is posted |
SalaryPlus | Job | Any Salary extras used when role is posted |
ATRProcessId | Job | ID of the ATR process linked to role when posted |
OfferDate | Offer Details | Offer date entered in the offer details accordion |
StartDate | Offer Details | Start date entered in the offer details accordion |
Salary | Offer Details | Salary as entered in the offer details accordion - May be different than Salary From/Salary To |
AgencyFee | Offer Details | Any Agency fee entered in the offer details accordion |
OfferJobTitle | Offer Details | Job Title as entered in the offer details accordion - May be different than Job Title from Job Table |
SalaryType | Offer Details | Salary type entered in the offer details accordion - May be different than Salary Type from Job Table |
SalaryPlus | Offer Details | Salary extras as entered in the offer details accordion - May be different than Salary Plus from Job Table |
CurrencyCode | Offer Details | Currency code as entered in the offer details accordion - May be different than Currency Code from Job Table |
PlaceOfWorkAddress | Offer Details | Office address as entered in the offer details accordion |
PlaceOfWorkPostcode | Offer Details | Office postcode as entered in the offer details accordion |
WorkingHours | Offer Details | Working hours as entered in the offer details accordion |
ContractedHours | Offer Details | Contracted hours as entered in the offer details accordion |
ProbationPeriod | Offer Details | Probation period as entered in the offer details accordion |
NoticePeriod | Offer Details | Notice Period as entered in the offer details accordion |
AnnualLeaveEntitlement | Offer Details | Annual leave entitlement as entered in the offer details accordion |
LineManagerName | Offer Details | Line manager name as entered in the offer details accordion |
LineManagerJobTitle | Offer Details | Line manager job title as entered in the offer details accordion |
LineManagerContactNumber | Offer Details | Line manager contact number as entered in the offer details accordion |
LineManagerContactEmail | Offer Details | Line manager email address as entered in the offer details accordion |
RecruitmentCost | Offer Details | Recruitment cost as entered in the offer details accordion |
AdminNotes | Offer Details | Admin notes as entered in the offer details accordion |
PlaceOfWorkType | Offer Details | Place of work type as selected in the offer details accordion (Remote/Hybrid/Workplace) |
PlaceOfWorkNotes | Offer Details | Place of work notes as entered in the offer details accordion |
Name | Hierarchy Team | Name of the team the role is posted in |
DisplayName | Hierarchy Team | Display name of the team the role is posted in |
Address1 | Hierarchy Team | Address line 1 set against the hierarchy team |
Address2 | Hierarchy Team | Address line 2 set against the hierarchy team |
City | Hierarchy Team | City set against the hierarchy team |
County | Hierarchy Team | County set against the hierarchy team |
PostCode | Hierarchy Team | Postcode set against the hierarchy team |
Description | Hierarchy Team | Description set against the hierarchy team |
WebsiteAddress | Hierarchy Team | Website address set against the hierarchy team |
Hierarchy Team | Email address set against the hierarchy team | |
TeamLogoFileName | Hierarchy Team | Filename of the logo stored against the hierarchy team |
TeamLogoBlobName | Hierarchy Team | Blob storage name of the logo stored against the hierarchy team |
TeamLogoBlobContainerName | Hierarchy Team | Blob storage container of the logo stored against the hierarchy team |
RightToWorkStatus | TrustID | Trust ID RTW Result Status |
FollowUpDate | TrustID | Follow up Date (Expiry Date) of RTW Check |
Notes | TrustID | Any Notes passed with the RTW check result |
Custom Values | ATR Extra Details | Custom fields and values depending on set up |
Custom Values | DocuSign Answers | Custom fields and values depending on set up |
Custom Values | Data Capture Form Answers | Custom fields and values depending on set up |
Transferred Documents
Please see the below table which shows what documents are transferred via the Core Data Export and and what file types are exported:
Note: please note that documents are only transferred if the 'Core Data Documents' integration has been setup.
If the standard 'Core Data' integration has been setup, this will only transfer the field data as listed above.
Document Name | Document Type | Detail |
Trust ID RTW Reports |
| |
Applicants CV | Multiple | Type depends on what document file type has been used when uploaded to TalosATS |
Applicants Application Form | HTML |
|
Completed DocuSign Documents |
| |
Data Capture Forms | HTML |
|
Credence Reports(DBS) |
| |
Any Documents stored in Manage Files | Multiple | Type depends on what document file type has been used when uploaded to TalosATS |
Completed Reference Reports |
|
Are documents transferred to Sona?
Yes, documents are transferred from Talos via the 'Core Data Documents' integration. If the 'Core Data' integration has been setup, this will not transfer documents.