Skip to main content

Talos360 Core Data via SFTP/FTP

Information on setting and processes of Talos360 Core Data within Talos to export candidate details, including documents

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

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

To send documents to Core Documents Via SFTP/FTP, you will need to provide some basic information depending on whether you are connecting via SFTP or FTP. If using a pem file, this must be provided to our support team so they can upload it to our server.

Required Information

  • Connection Type: SFTP or FTP

  • FTP/SFTP URL: The web address of your storage server

  • File Location: This is the folder structure to where the files should be stored. Please make sure there is no leading or trailing forward slashes.

  • FTP/SFTP Port: Used to connect to the server. Normally 22

  • Username: Your login for the server

  • Password: Required if using FTP

  • Pem File Location: Required if using SFTP – this will be given to use from our support team.

  • Passphrase: Optional for SFTP if your Pem file has one

Document Processing

Once your connection is set up, the system handles files automatically using the following steps:

Step 1: Receiving Documents

  • The system collects incoming documents from the queue.

  • Each document’s connection information is formatted for upload.

Step 2: Checking the Connection Type

  • The system determines whether to use SFTP or FTP for the transfer.

Step 3: Uploading via SFTP

  • If needed, authentication details are added.

  • A folder is created on the server (or verified if it already exists).

  • Each document is:

    • Retrieved

    • Checked for the correct file type

    • Prepared for transfer

    • Uploaded to the folder

    • Logged as success or error

Step 4: Uploading via FTP

  • A folder is created on the server (or verified if it already exists).

  • Each document is:

    • Retrieved

    • Checked for the correct file type

    • Prepared for transfer

    • Uploaded to the folder

    • Logged as success or error

Step 5: Final Status

  • Once all files are processed, a final report shows whether the upload was successful or if there were any errors.

System Responses

Message Title

Description

Type

Importance

Notes

Couldn’t Create Folder

The system couldn’t create a folder. Check your permissions and try again. Contact support if needed.

Error

Major

True

Upload Failed: Document - ##documentname##

This document could not be uploaded. Check connection and permissions.

Error

Minor

True, per document

Upload Partially Failed

Some or all documents failed to upload. Check your connection and permissions.

Error

Major

True, final outcome

Upload Successful: All Documents

All documents have been uploaded successfully. You can access them in your storage.

Success

Major

True, final outcome

Upload Successful: Document - ##documentname##

This document was uploaded successfully.

Success

Minor

True, per document

Important Notes

File Types

  • Only .pem files are supported for SFTP.

  • A developer must upload these files into the system and provide the location for the Pem File Location field.

  • Pem files can be set up with or without a passphrase depending on your preference.

Folder Creation

  • The system automatically creates a folder named with the application ID.

  • Ensure the login used for the connection has permission to create and write to this folder.

Common Issues

  • IP Whitelisting: Make sure your network allows access to the following IP addresses (attached) to avoid connection problems.

Did this answer your question?