Note: This article contains technical instructions for setting up an SFTP integration and is intended for your IT department or HRIS representative.
We recommend starting your SFTP setup here
A Secure File Transfer Protocol (SFTP) integration allows you to securely sync employee data from your HRIS into Nectar.
This is a one-way import — files are sent (or pulled) from your HRIS to Nectar’s SFTP server and automatically processed to keep your user list up to date.
1. Where do I set up the SFTP integration in Nectar?
Log in to Nectar as an Admin.
Navigate to Workspace Settings → Integrations → HRIS SFTP Sync.
Click Connect SFTP.
Enter:
Your Public SSH Key (details below)
A valid email address for notifications
Click Save to generate your unique Hostname and Username.
Both are case-sensitive — copy them exactly into your SFTP client or HRIS configuration.
2. How do I create SSH Key Pairs for the connection?
An SSH key pair secures your connection to Nectar’s SFTP server.
This replaces traditional username/password authentication with a stronger, encrypted key-based method.
What is an SSH Key Pair?
The Private Key stays securely on your HRIS system or SFTP client.
The Public Key is pasted into the SFTP setup page in Nectar.
Important: Only OpenSSH key pairs are supported. If your HRIS generates SSH2 keys, they must be converted before use.
👈 Steps to Create an SSH Key Pair
👈 Steps to Create an SSH Key Pair
Mac:
Open Terminal (Command + Space → “Terminal”).
Run the command:
ssh-keygen -t rsaWhen prompted, choose a file path and name
(Optional) Add a passphrase for added security.
Copy the contents of the generated .pub file (your public key).
Paste it into the Public Key field in Nectar.
Upload the private key to your HRIS or SFTP client.
Windows:
Open Command Prompt (Start → type cmd).
Or download PuTTYgen (a free SSH key generator).
In Command Prompt, run:
ssh-keygen -t rsaWhen prompted, choose a file path and name
(Optional) Add a passphrase for added security.
Copy the contents of the generated .pub file (your public key).
Paste it into the Public Key field in Nectar.
Upload the private key to your HRIS or SFTP client.
👈 Converting SSH2 Keys to OpenSSH
👈 Converting SSH2 Keys to OpenSSH
If your HRIS or SFTP client outputs keys in SSH2 format, convert them using:
ssh-keygen -i -f ssh2.pub > openssh.pub
This creates a compatible OpenSSH public key (openssh.pub).
PLEASE NOTE: Never share your private key via email or unsecured channels. You can generate multiple key pairs if needed.
3. HRIS/SFTP Client Configuration
Use your preferred SFTP client or HRIS system to establish the connection.
Field | Description |
Protocol | SFTP |
Authentication Level | Public key |
Password for Connection | Private key matched to the public key provided and inputted in Nectar |
Host / Hostname | Provided in Nectar on the Integrations page |
Username | Provided in Nectar on the Integrations page |
Port | 22 |
Destination Directory | Use Root |
Delivery Directory | /csvs-to-be-processed/username (see above for your username information) |
Outbound File Name | Whatever you’d like, but must have the file extension of .csv or .xlsx |
We recommend some variation of “CompanyNameNectarUsers.csv” |
|
Export File Type | CSV (preferred) or XLSX |
Delivery Frequency | We recommend a daily schedule in the early morning M-F. You can check with your CSM to make sure this schedule is best for your team. |
Nectar Technical Contact | Your CSM will be the technical contact for Nectar. In some scenarios they may include our Integrations Specialist as well. |
File Encryption | None. SFTP already encrypts by default. |
4. Uploading Employee Data Files
Once connected, your HRIS or SFTP client should automatically upload your employee data files to Nectar.
File Requirements:
Accepted formats: .csv (preferred) or .xlsx
Encoding: UTF-8
Delimiter: Comma (,)
File name: Must include file extension
✅ Example: CompanyNameUsers.csv
❌ Not accepted: CompanyNameUsers
.txt files can be sent for connection testing purposes only.
Common Errors
Error Message | Cause | Solution |
Connection refused | Firewall blocking port 22 | Allow outbound access on TCP Port 22 to the Nectar hostname |
SSH2 key not supported | SSH key not in OpenSSH format | Convert using ssh-keygen -i -f ssh2.pub > openssh.pub |
No email key found. Failed formatting users. | Missing “email” column in uploaded file | Update the HRIS report to include an email field |
File not processing | Incorrect file format or naming | Ensure the file has a valid extension and matches the required template |
New Path for Existing Integration
If your SFTP integration fails after previously working, it may be due to an updated hostname or directory path.
To reset:
Log in to Nectar → Workspace Settings → Integrations → HRIS SFTP Sync
Copy your Public Key to a text editor (temporarily)
Disable the integration
Re-enable it and re-enter your Public Key and email
Update your SFTP client settings with the new hostname and directory
Test the connection to confirm successful upload
Additional Tips
Test your connection using your SFTP client before scheduling automated transfers.
Limit SFTP access to necessary systems only.
If switching HRIS systems, review the below page and contact your Customer Success Manager before making any changes.
