Lattice HRIS + Nectar Integration

Connect Lattice HRIS to Nectar with a scheduled SFTP export so your people data powers recognition and engagement in Nectar.

Overview

Lattice HRIS keeps employee records alongside performance and engagement data. Nectar connects to it through a scheduled SFTP export: Lattice sends an employee file on the schedule you choose, and Nectar creates, updates, and deactivates users based on that file. Your Lattice records stay the source of truth, and Nectar recognition, rewards, and communications stay aligned with them.

Ideal for:

• Companies using Lattice HRIS as their employee system of record
• People teams who want recognition data to sit alongside their performance program
• Admins comfortable configuring a scheduled export
• Growing companies that want automated onboarding and offboarding in Nectar

How It Works

Nectar reads employee data from Lattice HRIS and uses it to create, update, and deactivate Nectar accounts. Data flows one way, from Lattice HRIS into Nectar, so Lattice HRIS stays your single source of truth.

What data syncs

• First name, last name, and work email (required)
• Preferred name
• Employee ID (recommended as the unique identifier)
• Manager email
• Department and office location
• Hire date and birthday (month and day only; birth year is never processed)
• Phone number, country, and preferred language
• Active status
• Custom fields you add to the report, which become Custom Properties in Nectar

Every field has a job inside Nectar. Manager relationships assign manager roles and Team Insights automatically. Hire dates and birthdays drive work anniversary and birthday celebrations in Nectar Recognition. Departments and locations power analytics filters, Group Give, and audience targeting in Nectar Comms, Nectar Engage, and Nectar Flows. Hire dates and work anniversaries can also trigger Nectar Flows, and manager relationships assign reviewers in Nectar Perform and build the org view in Nectar Signals. Country keeps the rewards catalog relevant for each employee, and phone numbers enable SMS delivery in Nectar Comms.

Sync behavior

• Runs each time Lattice HRIS delivers a new file; most teams schedule a daily delivery early on weekday mornings
• New rows create users, changes update existing profiles, and employees who no longer appear in the file are deactivated. If your report includes an active column, Nectar follows that status instead
• Matching on employee ID means an email change updates the existing account instead of creating a duplicate
• Fields you leave out of the report are never overwritten in Nectar

New users are created quietly by default. When you are ready to launch, turn on "Send Nectar platform email invitations to new users" so every future hire gets an invite automatically.

Authentication method

Files are delivered over SFTP to a destination unique to your Nectar account and authenticated with an SSH key pair. Lattice HRIS keeps the private key, and you share only the public key with Nectar. Every file is encrypted in transit over SSH.

Where users interact

Admins connect, monitor, and pause the integration in Nectar under Workspace Settings, then Integrations. Employees never touch it: they just find an accurate profile, the right manager, and their teammates already in Nectar when they log in.

Key Features + Benefits

• Automatic provisioning: new hires in Lattice HRIS get Nectar accounts without a manual upload
• Always-current profiles: title, department, manager, and location changes flow into Nectar
• Automated offboarding: terminated employees are deactivated, not deleted, so access ends and records stay intact
• You control the data: only the columns you include in the report are shared, and custom fields become Custom Properties in Nectar
• Celebrations on autopilot: birthdays and work anniversaries are recognized automatically from synced dates
• Controlled launch: accounts are created quietly, and invitations go out only when you turn them on
• Import monitoring: the Activity Console shows every import, and email alerts flag any file that fails

Setup and Implementation

Setting up the Lattice HRIS integration follows four steps: Connect, Authorize, Map, and Enable. Your Nectar Customer Success Manager guides you through each one.

High-level setup steps

1. Connect: In Nectar, go to Workspace Settings, then Integrations, then HRIS SFTP Sync, and click Connect SFTP.
2. Authorize: Add your public SSH key and a notification email, then save to generate your unique hostname and username.
3. Map: Build the Lattice SFTP Center, which a Lattice super admin can configure, using Nectar's template columns. First name, last name, and email are required; employee ID and manager email are strongly recommended.
4. Enable: Schedule the export to run daily, confirm the first import in Nectar's Activity Console, and turn on invitations when you are ready to launch.

Requirements

• Lattice super admin access to configure an export in the Lattice SFTP Center
• Nectar admin access

Estimated setup time

Connecting in Nectar takes minutes. Configuring and testing the Lattice export usually takes a few days to a few weeks.

Your integration should never delay your launch. If the connection is not live yet, Nectar's Bulk Upload loads your employees from a spreadsheet so you can launch on schedule and switch to the automated sync when it is ready.

Detailed, step-by-step instructions are available in the Nectar Help Center.

Use Cases

• Add new hires to Nectar from your Lattice HRIS export
• Keep reporting lines in Nectar matched to Lattice
• Celebrate milestones using Lattice hire dates and birthdays
• Deactivate employees who leave on the next scheduled file
• Bring custom Lattice fields into Nectar as Custom Properties

Security & Compliance

Nectar protects employee data at every step of the Lattice HRIS connection.

• SFTP over SSH encrypts every file and credential in transit
• Each account has its own delivery destination, and files cannot be read by other customers
• OpenSSH key-pair authentication; your private key is never shared with Nectar
• Data is encrypted in transit
• Nectar only uses the profile fields listed above and never syncs compensation, bank details, or benefits elections
• Only Nectar admins can connect, pause, or remove the integration
• Birth year is never processed; Nectar uses month and day only
• Nectar maintains a SOC 2 Type II report, audited annually, with security documentation available in the Nectar Trust Center

Learn more on the Nectar Security page and in the Nectar Trust Center.

Support & Resources

• Nectar Help Center
• How to sync employee data with Nectar using SFTP
• How to monitor and manage your HRIS SFTP sync
• Bulk upload users (to launch before your sync is live)
• Nectar Trust Center
• Email Nectar Support at [email protected], or contact your Customer Success Manager