Claude isolved People Cloud connectorWhat Claude can do in your isolved People Cloud account.
The Claude isolved People Cloud connector exposes 4 tools. 0 are documented as reading, 2 change your time off requests, and 2 are described nowhere. Below: what Claude confirms before it submits, the clash over cancelling, and what your organization must switch on first.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can reach isolved
Asking for a day off usually means logging into the HR portal, finding the right form and filling in leave type, hours and dates. With the connector, an employee tells Claude what they need, and Claude prepares the time off request, checks every detail back with them, and only then sends it to isolved.
A leave request in one message. Say you want next Friday off as vacation: Claude uses submit_time_off_request, but first confirms the leave type, hours and dates with you. Nothing goes out before you say yes.
A change of plans. The sheet also lists cancel_time_off_request. isolved's own page, dated August 2026, says cancelling through Claude is not available yet; the limits section sets both sources side by side.
Payroll, described but not listed. isolved presents The Guardian, a payroll add-on enabled through its sales process, yet none of its tools appears on the directory sheet we read.
What the connector does not do matters too. Two tools, get_time_off_requests and get_time_off_summary, have no description in any source. isolved says The Guardian, its payroll part, does not reach Benefits, Time, HR or other HCM areas in this release, and does not write SSN, EIN or ITIN fields. Nothing runs by itself: no request goes out on a schedule. That is an automation tool's job, a different one; the Integrations hub covers that side.
Five words before you connect
The Claude vocabulary this page relies on, in under a minute.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action the connector hands to Claude. Claude picks the ones it needs by itself; the directory sheet lists them by name.
- Authorization
- The service's own sign-in screen, where you grant the access Claude will use afterwards. Given once per person, and revocable.
- Approval
- The confirmation Claude waits for in the chat before it goes ahead with something that would change your account.
- MCP
- The open standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as isolved.
Connect isolved to Claude in three steps
- 01
Find isolved in Claude
Open Claude's settings, go to Customize then Connectors, and look up isolved in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector before members can each sign in.
- 02
Start the connection
Click Connect on its row, then sign in to isolved in the window the service opens itself. If the link breaks later, use Disconnect and connect again from the same row.
- 03
Read the authorization screen
Check the screen isolved shows before you accept it. It belongs to the service, not to Claude, and it is what sets what the access covers. Access granted there can also be withdrawn later from the isolved side.
The 4 tools, split by what is known
isolved People Cloud gives Claude 4 tools: 0 that read your account, 2 that change something in it, and 2 no official source describes.
Two tools change your time off requests, two are names with no description. Tool names stay exactly as Claude shows them.
- 2 write
- 2 not documented
What Claude changes (2)
2 toolsTwo tools that act on time off requests in isolved. One has a documented confirmation; the other is contested by isolved's own page.
cancel_time_off_request
Approval: see the ruleThe directory sheet lists this tool by name and nothing more. isolved's own page, written earlier, says cancelling a request through Claude is not in this release and must be done in isolved directly.
submit_time_off_request
Asks you firstSends a new time off request to isolved on your behalf, once you and Claude have agreed on what it says.
Undocumented (2)
2 toolsThe directory publishes these two names and nothing more. No official text says what they do, so this page does not guess.
get_time_off_requests
No official source documents this tool. The directory sheet carries its name, isolved's page about the connector never mentions it, and no Claude help page covers it.
get_time_off_summary
Listed on the sheet, explained nowhere: no official source documents it. The sheet's general description talks about checking time off balances, but no source ties that sentence to this name, so this page leaves its effect undescribed.
What Claude checks with you first
By default, Claude stops and asks before each action it takes on an account in your name. For time off, isolved is specific: Claude confirms leave type, hours and dates before it submits anything.
On Team and Enterprise workspaces, owners decide whether members may let some actions through without a prompt, and they can restrict what a connector does for the whole organization; nobody overrides that from a personal account. Claude works with the rights of the person who signed in: isolved says the same of The Guardian, its payroll add-on, which stays inside your own isolved permissions. Disconnecting removes Claude's access at once.
Which plans include it
None of the 819 sheets in the official directory shows plan availability. The answer, connector by connector, is published nowhere.
What is published is the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members can each connect. For the live state, the isolved People Cloud sheet in the official directory is the place to look.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you, so nothing is filed when a holiday approaches or a balance changes.
Everything here comes from the directory sheet and isolved's own page: no Claude help page covers this connector. The tool list is an observed floor, not a promise. The partner badge is not a security audit, and Anthropic states on every sheet that it neither picks a publisher's tools nor guarantees how they behave. The sheet adds that capabilities vary with your organization's isolved setup and enabled services.
Can Claude cancel a time off request through the isolved connector?
- isolved page about the connector, FAQ ↗August 2026Not in this release: cancel a submitted request by signing in to isolved directly; cancelling through Claude is planned for later.
- Claude directory sheet ↗October 2026The sheet lists cancel_time_off_request among the connector's four tools.
What this page followsThe directory sheet is the more recent of the two and lists the tool; isolved's earlier page says the feature is not there and does not describe the tool. Neither says whether it works for every organization, so try it on your own account and fall back to isolved if in doubt.
Need help connecting isolved People Cloud to Claude?
A person reads every message.