Skip to main content

Custom SFTP integration

How to set up a custom SFTP send

Jared Ellis avatar
Written by Jared Ellis
Updated yesterday

Who can use this feature?

Available on:

  • All Culture Amp subscriptions.

Note: If your HRIS isn't listed in Culture Amp or if you're unsure about its compatibility with automatic SFTP transfers, we advise reaching out directly to your HRIS representative. They can confirm if your system supports generating files that align with our employee template guidelines and provide information regarding any potential associated costs.

You can save time and effort by configuring your HRIS to automatically extract and send your employee data to Culture Amp via Secure File Transfer Protocol (SFTP).

Employee data files sent to Culture Amp via SFTP will be processed using our partial import process, allowing you to safely decentralize employee data management across your organisation.


Once files are successfully imported via SFTP, youโ€™ll see added/updated employee details in the Users page of your Culture Amp account.

For any custom SFTP transfers, make sure to select Other Integration Options from the Integrations page to begin the set up process on the Culture Amp side:

Some key things to note:

  • Setting up the SFTP connection will require the assistance of an appropriate IT support person or another contact familiar with SFTP.

  • Make sure that your HRIS supports the creation of files that fit these data standards and requirements.

As an alternative, your Engineering or IT team may also be able to help you set up an automatic transfer via an external SFTP client such as Filezilla. For more information, check out the SFTP technical guide for IT support specialists.

๐Ÿ”‘ PGP File Encryption (Optional)

Culture Amp supports PGP encryption to more securely transfer sensitive user files via SFTP if required.

Requirements:

To ensure your files are processed successfully using PGP encryption, please adhere to the following technical requirements:

  • Encryption Type: We only accept files that are encrypted without signing. Signed files will result in a failed ingestion attempt.

  • Software Version: Use GnuPG version 2.2.8 or higher.

  • Accepted File Formats: Files must use one of these specific extensions

    • <filename>.csv.pgp

    • <filename>.xlsx.pgp

  • Encoding: .csv files must be UTF-8 encoded

Why isn't "signing" required?

While signing verifies the sender's identity, it is redundant for our system because we already require secure SSH Key authentication for all SFTP transfers.

How do I encrypt my files?

You will need the Culture Amp Public RSA key and the recipient email, both of which can be provided by your Customer Success or Technical Success representative. Just reply with "Ask a Person" in a Support Conversation to connect with the support team if you're unable to contact your CSM directly.

How can I tell if my file is encrypted correctly?

A correctly encrypted PGP file is "ASCII armored," meaning it is human-readable text that looks like a block of random characters (e.g., starting with -----BEGIN PGP MESSAGE-----). In contrast, a signed file is a binary file that will appear as "nonsense" characters or unreadable symbols when opened.

What happens to my files after upload?

  • Successful Files: Files that process successfully are deleted promptly after ingestion.

  • Failed Files: Files with incorrect extensions or encryption (like signed files) are moved to a failed_files folder and deleted after 5 days.

  • Retention Policy: All files are automatically removed from the SFTP server within five (5) days.

Need more info? Access some further PGP documentation, including visual examples, here.


โ€‹
โ€‹


๐Ÿ’ฌ Need help? Just reply with "Ask a Person" in a Support Conversation to speak with a Product Support Specialist.

Did this answer your question?