Claude Lattice connectorWhat Claude can do in your Lattice account.
The Claude Lattice connector exposes 20 tools. 13 read your Lattice data, 3 write (saving drafts and submitting a review), and 4 are documented by no official source. Below: what Claude can see, what it can submit, and the two admin switches that come first.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can reach Lattice
Reviews, updates, feedback and notes from 1:1s live in Lattice. With the connector, Claude pulls that context into the conversation for you, helps you write, then saves the draft in Lattice. It sees exactly what your Lattice role lets you see, as a manager or an employee, never the admin view.
Prepare a review with the facts in front of you. Claude can read the drafts you owe with get-draft-reviews, past reviews you are allowed to see with find-reviews, feedback with find-feedback and your 1:1 history with find-one-on-ones. It then saves answers with save-draft-review, checks what is missing with validate-draft-review, and submits with submit-review.
Write your update faster. get-current-update-draft loads this period's questions, and save-draft-update stores your answers and sentiment without publishing.
Find your way around the org. whoami, find-employees, find-reports, find-ancestors and list-departments answer who is who and who reports to whom.
What Claude cannot do here: anything from the admin side of Lattice, even if you are a Lattice admin. Lattice says the connector offers manager and employee capabilities only. Four tools on the sheet have no description anywhere, and nothing happens by itself when a cycle opens. The Integrations hub lists the other connectors covered so far.
Five words before you connect
The vocabulary Claude uses around this connector, in one minute.
- Connector
- A link you set up once between Claude and an account you already have, here Lattice, so Claude can work in it while answering.
- Tool
- One named action the connector hands Claude, such as saving a review draft. Claude picks the ones it needs as it replies.
- Authorization
- Lattice's own consent screen, where you grant the access Claude will use. It is given once per person and can be withdrawn.
- Approval
- The confirmation Claude waits for before an action that changes your account, such as submitting a review, shown in the chat.
- MCP
- The open standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Lattice.
Connect Lattice to Claude in three steps
- 01
Find Lattice in Claude
Open Claude's settings, go to Customize, then Connectors, and find Lattice. On a Team or Enterprise workspace, an Owner or Primary Owner has to add the connector before members can each authenticate.
- 02
Sign in to Lattice
Click Connect on the Lattice row. Lattice opens its own window, asks for your Lattice subdomain, then your login. If the link breaks later, Disconnect and connect again.
- 03
Review the permissions
Read the authorization screen before you accept. It is Lattice's screen, not Claude's, and it lists what the access covers, from employee data to reviews and updates. You can revoke it later.
The 20 Lattice tools, by what they do
Lattice gives Claude 20 tools: 13 that read your account, 3 that change something in it, and 4 no official source describes.
Three groups: what Claude reads, what it saves or submits, and what no official source describes. Names stay exactly as Claude shows them.
- 13 read
- 3 write
- 4 not documented
What Claude reads (13)
13 toolsThirteen tools that look at people, reviews, updates, feedback and 1:1s without changing them.
whoami
Identifies the person asking: your own profile (name, title, email, department) plus your manager's. It deliberately leaves out your reports, reviews and goals.
find-employees
Searches colleagues by name, work email or department and returns their profiles with the ID other tools require. Results match what you are allowed to see, and org-chart links are not included.
find-reports
Returns the team below an employee, either direct reports or the whole subtree down to a chosen depth of up to five levels. Only people beneath appear, never peers or managers.
find-ancestors
Traces the chain of managers above someone, from their direct manager up to the top of the org. It skips the person, their reports and their peers.
list-departments
Lists the active departments of the company with their IDs and names. It does not say who belongs to each one or how departments nest.
get-draft-reviews
Shows the open review drafts you are currently drafting, self-reviews and reviews of others, with the cycle, the questions, and any saved answers. Submitted reviews stay out.
find-reviews
Retrieves past reviews you are permitted to read, filtered by reviewee, author, cycle, direction (self, downward, upward, peer), status or dates. By default only reviews already shared with the reviewee come back.
get-review-cycles
Tells you which review cycles you are part of right now, your role in each (reviewer, reviewee or both) and how many drafts you owe. It returns counts, not the content of reviews.
validate-draft-review
Inspects an open draft and lists the required questions still unanswered. Optional or complete questions are left out. It only inspects, so it is a safe check to run right before submit-review.
list-updates-for-employee
Brings up the submitted status reports of one person, with their questions and answers, sentiment and period. Drafts never appear, and neither do status reports written by other people.
get-current-update-draft
Opens your status report for the current period: questions, saved answers, period dates, cadence and sentiment. If you have not started, you still get the questions so you can preview the template.
find-feedback
Retrieves feedback you can see, either about a given person or written by them. Reviews, answers to status reports and 1:1 notes are excluded. It sits next to find-reviews when you gather material for a review.
find-one-on-ones
Surfaces your 1:1 meetings with one person, past, upcoming and cancelled, with talking points, action items, shared notes, AI summary and your private notes. Meetings you did not attend stay out.
What Claude writes (3)
3 toolsThree tools that save drafts or submit a review. No source spells out their confirmation, so the general rule below applies.
submit-review
Approval: see the ruleMoves a finished draft from drafted to submitted. Lattice says every required question in the draft needs an answer, and once submitted it can no longer be edited as a draft.
save-draft-review
Approval: see the ruleStores answers on an open review draft: ratings, free text or multiple choice. New answers replace earlier ones for the same questions, and the review stays an editable draft, not submitted.
save-draft-update
Approval: see the ruleWrites answers, sentiment and the public flag into your current-period update draft. Partial saves leave untouched answers in place, and the draft is not published.
Not documented (4)
4 toolsThe directory lists these four names and nothing more. No official text says what they do, and this page will not infer it.
get-review-context-for-reviewee
This name is on the directory's tool list and nowhere else. Lattice's tool article does not include it and no Claude page mentions it, so this page has nothing to report about it.
get-review-packet-for-reviewee
Same situation as the previous name: listed in the directory, absent from every official text we could read, so no source documents it. Guessing its role from its wording would be fiction, so we leave it blank.
list-goals-for-employees
Lattice's tool article documents a tool with a nearly identical name in the singular, not this plural one. No source documents this exact plural name, and nothing official ties the two together.
list-grow-competencies-for-employees
The directory shows this plural name; the publisher's article only describes a singular one. With no text matching it exactly, we record it as undocumented rather than borrow the other's description.
What Claude asks before acting
By default, Claude pauses and asks for confirmation before each action it takes on an account for someone, in the conversation.
No source describes a specific prompt for the three Lattice write tools, so that default is what covers saving drafts and submitting a review. Lattice adds that Owners can restrict what the connector does across the organization, for example keep it read only. Claude also uses your Lattice rights and nothing more: a request you could not make in Lattice comes back as a permission error, and Claude cannot go around it.
Which plans can use it
No official source publishes plan availability connector by connector, and none of the 819 directory sheets shows it.
The general rule is what is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members connect. The publisher's setup guide describes that same Owner step from its side. For the live state, check the sheet in the official directory.
Where the Lattice connector stops
A connector is not an automation. Claude calls these tools while it answers you, so nothing starts by itself when a review cycle opens or an update is due.
Everything here comes from Lattice's help center: no Claude help page covers this connector. The partner badge is not a security audit, and Anthropic states it neither picks the tools a publisher exposes nor guarantees they behave as announced. Lattice also warns that its tool list changes over time, so a new tool may only appear after you refresh the list in the connector's menu or reconnect. Anthropic's advice on every sheet applies too: only connect a publisher you know.
Need help connecting Lattice to Claude?
A person reads every message.