Skip to main content

Cascade API

Learn how to get setup with Cascade within Talos to onboard candidates

Adam Kavanagh avatar
Written by Adam Kavanagh
Updated over a month ago

Intermediate Setup โ€“ may require occasional guidance, but generally manageable to setup using the step-by-step guide.

Talos has several HR providers integrated within the system.

Learn how to setup Cascade within your ATS, so you can onboard candidates directly into your HR system.

Note: you will need access to the Integrations Management administration permission to setup the integration

Setup

Required Information

The below details will be required to integrate Cascade to Talos:

  • Client Key

  • Client Secret

  • Temp Hierarchy ID

  • Temp Job Title

These details will need to be provided by Cascade support.

Information: the Hierarchy ID will be a series of alphanumeric characters and will need to be entered in the below format in Talos:

xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

You will also need the data values for the below field, from your Cascade HR system, so these can be added to the relevant data capture forms in Talos:

  • Title

  • Cost Centre

  • Gender

  • Ethnic Origin

  • Nationality

  • Religion

  • Marital Status

  • Gender Identity

Once all the details have been provided by Cascade to you, you will be able to set this up in Talos Marketplace. Search for 'Cascade' within the Marketplace 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. Linking the integration to your workflows in Talos is mandatory and must be completed for Cascade to be an available option on job posts.

Creating a Temp Hierarchy & Job Title in Cascade

A Temp hierarchy is required for the transfer of candidates from Talos, as there is no direct integration between your Cascade hierarchy and your Talos hierarchy. You can manually move candidates from the Temp hierarchy to the relevant Cascade hierarchy once the candidates have been imported

Temp Hierarchy

To create a new hierarchy in Cascade to be used for the integration, please see this guide on Cascade's knowledge base, which has steps on how to set this up.

Cascade support will be able to assist in providing the Temp Hierarchy ID that has been created on your Cascade system, as the ID can only be found within the back-end data of Cascade's system.

Temp Job Title

To setup a temp job title, please refer to this guide on Cascade's knowledge base. The job title will need to be inputted in Talos once created.

Only one Temp Job Title is required to be setup in Cascade and added to Talos, and all candidates submitted to Cascade will be imported against this job title.

The candidate can then be manually assigned the relevant job title within your Cascade system.

Transferred Fields

Please see the below table which shows what fields are transferred to Cascade 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 to Cascade.

API Field

Length

Cascade Source

Talos Source

Talos Name

Title Honorific

50 characters

[Employee].[Title]

External Data Capture Form

Title

First Name

50 characters

[Employee].[Forename]

Core Data

First Name

Known As

50 characters

[Employee].[KnownAs]

External Data Capture Form

Known As

Other Name

50 characters

[Employee].[OtherName]

External Data Capture Form

Other Name(s)

LastName

50 characters

[Employee].[Surname]

Core Data

Surname

Cost Centre

50 characters

[Employee].[CostCentre]

Internal Data Capture From

Cost Centre

National Insurance Number

50 characters

[Employee].[NationalInsuranceNo]

External Data Capture Form

National Insurance Number

Include In Payroll

[Employee].[IncludeInPayroll]

Internal Data Capture From

Include in Payroll?

Employment Start Date

[Employee].[EmployeeStartDate]

Internal Data Capture From

Start Date

Continuous Service Date

[Employee].[ContServiceDate]

Internal Data Capture From

Continuous Service Date

Date Of Birth

[Employee].[DateOfBirth]

External Data Capture Form

Date of Birth

Gender

50 characters

[Employee].[Sex]

External Data Capture Form

Gender

Ethnicity

50 characters

[Employee].[EthnicOrigin]

External Data Capture Form

Ethnic Origin

Nationality

50 characters

[Employee].[Nationality]

External Data Capture Form

Nationality

Religion

50 characters

[Employee].[Religion]

External Data Capture Form

Religion

Marital Status

50 characters

[Employee].[MaritalStatus]

External Data Capture Form

Marital Status

Phones - Ownership

50 characters

[Employee].[WorkPhone]

Hard: Organization

Hard: Organization

Phones - Type

50 characters

[Employee].[WorkPhone]

Hard: Landline

Hard: Landline

Phones - Value

50 characters

[Employee].[WorkPhone]

Internal Data Capture From

Work Phone Number

Phones - Ownership

50 characters

[Employee].[WorkMobilePhoneNumber]

Hard: Organization

Hard: Organization

Phones - Type

50 characters

[Employee].[WorkMobilePhoneNumber]

Hard: Mobile

Hard: Mobile

Phones - Value

50 characters

[Employee].[WorkMobilePhoneNumber]

Internal Data Capture From

Work Mobile Number

Phones - Ownership

50 characters

[EmployeeHomeAddress].[Phone]

Hard: Personal

Hard: Personal

Phones - Type

50 characters

[EmployeeHomeAddress].[Phone]

Hard: Landline

Hard: Landline

Phones - Value

50 characters

[EmployeeHomeAddress].[Phone]

Core Data

Telephone Number

Phones - Ownership

50 characters

[EmployeeHomeAddress].[MobilePhone]

Hard: Personal

Hard: Personal

Phones - Type

50 characters

[EmployeeHomeAddress].[MobilePhone]

Hard: Mobile

Hard: Mobile

Phones - Value

50 characters

[EmployeeHomeAddress].[MobilePhone]

Core Data

Mobile Number

Emails - Ownership

320 characters

[Employee].[WorkEmail]

Hard: Organization

Hard: Organization

Emails - Value

320 characters

[Employee].[WorkEmail]

Internal Data Capture From

Work Email Address

Emails - Ownership

50 characters

[EmployeeHomeAddress].[HomeEmail]

Hard: Personal

Hard: Personal

Emails - Value

50 characters

[EmployeeHomeAddress].[HomeEmail]

Core Data

Email Address

Address - Ownership

50 characters

[EmployeeHomeAddress].[HomeEmail]

Hard: Personal

Hard: Personal

Address - Address1

50 characters

[EmployeeHomeAddress].[Address1]

External Data Capture Form

Address Line 1

Address - Address2

50 characters

[EmployeeHomeAddress].[Address2]

External Data Capture Form

Address Line 2

Address - Address3

50 characters

[EmployeeHomeAddress].[Address3]

External Data Capture Form

Address Line 3

Address - Address4

50 characters

[EmployeeHomeAddress].[Address4]

External Data Capture Form

Address Line 4

Address - Address5

50 characters

[EmployeeHomeAddress].[Address5]

External Data Capture Form

Address Line 5

Address - Postcode

50 characters

[EmployeeHomeAddress].[Postcode]

External Data Capture Form

Postcode

Gender Identity

50 characters

[Employee].[GenderIdentity]

External Data Capture Form

Gender Identity

Employee Id

50 characters

Success Message

Employees Payload

Bank Name

50 characters

[EmployeeBank].[BankName]

External Data Capture Form

Bank Name

Account Name

50 characters

[EmployeeBank].[AccountName]

External Data Capture Form

Bank Account Name

Account Number

50 characters

[EmployeeBank].[AccountNumber]

External Data Capture Form

Bank Account Number

Sort Code

50 characters

[EmployeeBank].[SortCode]

External Data Capture Form

Sort Code

Employee Id

50 characters

Cascade Source: [EmployeeJobs].[JobTitle]

Success Message

Employees Payload

Job Title

100 characters

Marketplace

Temp Job Title

Start Date

Cascade Source: [EmployeeJobs].[SYS_EffectiveDate]

Internal Data Capture From

Start Date

Hierarchy Node Id

36 characters

Marketplace

Temp Hierarchy ID

FAQ

Can I add additional fields into the form?

Yes, you can add additional fields into the data capture form however this information will not be transferred to Cascade. The integration will only transfer information for the fields indicated above.

Can I remove fields from the form that I don't want to transfer?

Yes, you can remove any optional fields from the forms that you don't wish to include in the transfer. However, some fields are mandatory, these mandatory fields cannot be removed and must be completed.

Can bank details be sent to Cascade from Talos?

Yes, bank details can be sent. You will need to contact Cascade's support team to enable this functionality on your system. Once this has been enabled, if you select 'Send Employee Bank Details' within the Cascade setup in Talos Marketplace, this will transfer bank details to Cascade.

Are documents transferred to Cascade?

Any documents which are linked to a candidates application in Talos are not transferred to Cascade.

Did this answer your question?