Before you start
Most integrations require a Lattice admin or the Manage integrations, SSO, and API data company-wide permission. See the individual Integration setup linked below. Also see Configure Custom Role Integrations Permissions.
Many integrations also need an admin or owner in the other tool. Each setup guide lists what's required.
Connectors use Lattice AI. If Lattice AI is turned off, Connectors are hidden. See Manage Lattice AI Access.
Integration types at a glance
Type | What it does | Data direction | Where people see it |
Employee data import (HRIS, SFTP, SCIM) | Keeps employee records and the org chart current | Into Lattice. Workday and Rippling can also send some data back. | People directory, org chart, and anywhere employee fields appear |
Lets AI tools like Claude and ChatGPT read and act on Lattice data | Both. The AI tool reads from and writes to Lattice. | The AI tool, not Lattice | |
Gives Lattice AI context from tools like Jira, Notion, and Zoom | Into Lattice | Lattice AI features, such as Updates and Reviews | |
Calendar integrations (Google Calendar, Outlook) | Syncs 1:1 and meeting schedules | Into Lattice | 1:1s or Meetings |
Communication apps (Slack, Microsoft Teams) | Sends Lattice notifications and actions to chat | Out of Lattice, with actions back in | Slack or Teams |
Goals integrations (Jira, Salesforce) | Updates goal progress from Jira filters or Salesforce reports | Into Lattice (read-only) | A goal's progress |
Let's your engineers build custom integrations | Mostly out of Lattice (read-only). | Depends on what you build |
Employee data import integrations
Employee data integrations bring people records from your HR system into Lattice, so you don't have to update employees by hand. Choose one method as your main source of employee data.
Method | How it works | Data direction | Setup guide |
HRIS integration | A direct connection to a supported HRIS, such as BambooHR, Workday, Rippling, or ADP | Into Lattice | |
SFTP | Your HRIS sends a CSV file of employee data to Lattice's SFTP server on a schedule. Use this when Lattice doesn't have a direct integration with your HRIS. | Into Lattice | |
SCIM | An external system, usually an identity provider, provisions accounts and sends employee data to Lattice | Into Lattice |
Admins set up HRIS integrations and SCIM from Admin > Platform > Integrations. To start SFTP, contact Customer Care for credentials. Admin paths differ by integration type, so check each setup guide.
After a sync, you can check what changed in the Import Log. Employees see the synced data wherever their profile fields appear, such as the people directory and org chart.
Two-way HRIS integrations
Some HRIS integrations also send Lattice data back to your HRIS:
Workday: Sends review data and feedback from Lattice to Workday. See Configure the Workday Integration, Sync Lattice Review Data to Workday, and Sync Lattice Feedback Data to Workday.
Rippling: Sends the performance ratings and scores you choose from selected review cycles to Rippling, where they appear in Rippling's Data Catalog. See Integrate Rippling with Lattice and Sync Lattice Review Data to Rippling.
Lattice MCP
Lattice MCP lets AI tools like Claude, ChatGPT, Slack, and Glean use Lattice data, such as reviews, 1:1s, feedback, goals, and updates.
Data direction: Both. The AI tool reads Lattice data and can take some actions, like drafting updates or creating goals. See Lattice MCP Tools for more details.
Permissions: Each employee signs in with their own Lattice account. The AI tool can only see what that person can already see in Lattice.
Admins allow each AI tool from Admin > Platform > MCP Integrations. An admin in the AI tool usually needs to enable the Lattice app too.
Employees connect their Lattice account inside the AI tool.
Where people see it: In the AI tool, not in Lattice.
Setup guides:
Connectors
Connectors let employees connect their work accounts in productivity tools, so Lattice AI can use that work as context. For example, the Lattice AI Agent can draw on an employee's Jira issues or Notion pages created.
Data direction: Into Lattice.
Admins choose which connectors are available from Admin > Platform > Connectors. Some tools also need an admin there to install or approve the Lattice app.
Employees connect their own accounts from their profile > Manage settings > Connectors. Each person authorizes their own account.
Requirements: Lattice AI must be on. If it's off, Connectors are hidden for admins and employees.
Setup guides:
Calendar integrations
Calendar integrations keep 1:1s and meetings in Lattice in step with Google Calendar or Outlook. Your calendar is the source of truth: when you reschedule a recurring event, Lattice updates the 1:1 and schedules the next one.
Data direction: Into Lattice. For Google Calendar, Lattice also adds a link to the Lattice 1:1 in the event description. [Confirm: Google's technical details article lists read-only scopes. How does Lattice add the link?]
Who sets it up: Each employee connects their own calendar. No admin setup is needed in Lattice. For Outlook, a Microsoft admin may need to approve Lattice first.
Where people see it: In 1:1s and Meetings.
Calendar | Sync timing | Setup guide |
Google Calendar | Changes can take up to 1 hour | |
Outlook | About 5 minutes |
With a connected calendar, you can also invite the Lattice AI Agent to join meetings on Google Meet, Microsoft Teams, or Zoom. See Invite the Lattice AI Agent to Your 1:1s.
Communication apps
The Lattice apps for Slack and Microsoft Teams bring Lattice notifications into chat and let people take some actions there, such as giving feedback.
Data direction: Out of Lattice to chat, with some actions sent back into Lattice.
Who sets it up: An admin installs the app for the company. Someone with permission to install apps in Slack or Teams may also need to approve it.
Where people see it: In Slack or Teams.
Setup guides: Slack Integration articles, About the Lattice Slack App, and Company Integration with Microsoft Teams.
Slack appears in three integration types, and each one does something different:
Slack integration | What it does |
Lattice Slack app | Sends Lattice notifications and actions to Slack |
Slack connector | Gives Lattice AI context from an employee's Slack messages. Requires the Lattice Slack app. |
Lattice MCP with Slack | Lets Slack's AI use Lattice data |
Goals integrations
Goals integrations update a goal's progress automatically from Jira or Salesforce. The connection is read-only: Lattice reads the results of a Jira filter or Salesforce report and doesn't change data in either tool. Progress syncs at the start of each hour.
Admins create the connection from Admin > Platform > Integrations. You can limit which departments or employees can use a Jira connection.
Employees connect a goal or key result under How will you measure progress? when they create or edit it.
Tool | Notes | Setup guide |
Jira | Jira Cloud only. Each goal tracks up to 50 issues from its filter. | |
Salesforce | Connects to reports in Salesforce's standard Reports module |
For an overview, see Integrate with Lattice Goals.
The Jira goals integration is separate from the Jira connector. The goals integration tracks goal progress. The connector gives Lattice AI context about an employee's work. See Connectors.
Lattice Public API
The Lattice Public API lets your company build its own custom integrations with Lattice. Use it when none of the integration types above fit your needs.
Data direction: Mostly read-only. You can't use the Public API to update employee data. To send employee data into Lattice, use the SCIM API.
Who sets it up: Your own technical resource or engineer builds and maintains the integration. Lattice doesn't build custom integrations for you.
See Lattice's Public API.
