HR Cloud

Live 64 Actions

HR Cloud Integration for AI Agents

Connect your AI agent to 64 HR Cloud actions via MCP, A2A, or SDK, with agent authentication, tool-calling execution, and security built-in.

Start Free Book Demo HR Cloud MCP Server

HR Cloud AI Agent Actions

64 production-ready actions for your agent to do more on HR Cloud.

Read the HR Cloud docs Watch AI Onboarding Demo

64 Actions

List Employees - List Employees via HR Cloud CoreHR REST API.

Get Employee - Get Employee via HR Cloud CoreHR REST API.

Create Employee - Create Employee via HR Cloud CoreHR REST API.

Create Employee Using Mapping - Create one or more employees, where nested Lookup objects can reference parent entities (Department, Location, Position, etc.) by a "code" field instead of the primary Id.

Update Employee - Update Employee via HR Cloud CoreHR REST API.

Update Employee Using Mapping - Update one or more employees, identifying each by an alternative field (xEmail, xEmployeeNumber, etc.) instead of the primary Id. Supports nested Lookup objects keyed by code instead of Id. NOTE; the mapping feature requires the Service Account to hold field-level "Set" permission on every lookup field referenced in the mapping query (xDepartmentLookup, xManagerLookup, xLocationLookup, xPositionLookup, etc.). Without it the provider returns HTTP 400 "Validation failed. No set permission on field <lookup>." regardless of body shape. Same Set-permission gate also blocks UPDATEs that include xRecordStatus / xStartDate / xEmail in the body. Per HR Cloud's security-and-permissions docs, customers' HR Admins cannot grant this — only HR Cloud's Account Manager / Support team can flip the backend permission. Until granted, this action stays preview because its core feature (mapping) cannot be exercised.

Upsert Employee - Update or create one or more Employees via HR Cloud CoreHR REST API. Records with a matching Id are updated; records whose Id does not yet exist are created.

List Employment Statuses - List xEmploymentStatus records. Required for resolving xEmploymentStatusLookup on create/update/upsert_employee.

List Employment Types - List xEmploymentType records. Required for resolving xEmploymentTypeLookup on create/update/upsert_employee. Note xEmploymentType is a DIFFERENT catalog from xEmploymentStatus — do not reuse Status Ids for Type fields. NOTE; endpoint is not listed in HR Cloud's public Core HR API v5.4 docs but is functional (verified — returns Intern / Contractor / Freelance / Full-Time / Part-Time / Internship records). Same precedent as list_employee_groups; if the provider removes the endpoint in a future release, xEmploymentTypeLookup falls back to admin-UI out-of-band discovery.

List Departments - List Departments via HR Cloud CoreHR REST API.

Get Department - Get Department via HR Cloud CoreHR REST API.

Create Department - Create Department via HR Cloud CoreHR REST API.

Update Department - Update Department via HR Cloud CoreHR REST API.

Upsert Department - Update or create a Department via HR Cloud CoreHR REST API. If a record matching the Id (or Identifier query field) exists it is updated, otherwise a new department is created.

List Divisions - List Divisions via HR Cloud CoreHR REST API.

Get Division - Get Division via HR Cloud CoreHR REST API.

Create Division - Create Division via HR Cloud CoreHR REST API.

Update Division - Update Division via HR Cloud CoreHR REST API.

Upsert Division - Update or create a Division via HR Cloud CoreHR REST API. If a record matching the Id (or Identifier query field) exists it is updated, otherwise a new division is created.

List Locations - List Locations via HR Cloud CoreHR REST API.

Get Location - Get Location via HR Cloud CoreHR REST API.

Create Location - Create Location via HR Cloud CoreHR REST API.

Update Location - Update Location via HR Cloud CoreHR REST API.

Upsert Location - Update or create a Location via HR Cloud CoreHR REST API. If a record matching the Id (or Identifier query field) exists it is updated, otherwise a new location is created.

List Positions - List Positions via HR Cloud CoreHR REST API.

Get Position - Get Position via HR Cloud CoreHR REST API.

Create Position - Create Position via HR Cloud CoreHR REST API.

Update Position - Update Position via HR Cloud CoreHR REST API.

Upsert Position - Update or create a Position via HR Cloud CoreHR REST API. If a record matching the Id (or Identifier query field) exists it is updated, otherwise a new position is created.

List Position History - List Position History via HR Cloud CoreHR REST API.

List Applicants - List Applicants via HR Cloud CoreHR REST API.

Get Applicant - Get a single Applicant by Id. Provider-quirk — when the Id is not found the API returns HTTP 200 with data null instead of 404. Agents must check for null in the response, not just the status code.

Create Applicant - Create Applicant via HR Cloud CoreHR REST API. NOTE: REQUIRES the HR Cloud Recruit app to be installed on the tenant (currently not installed by default — request via Settings → Explore Apps → Recruit → 'I'M INTERESTED'). Without it the xApplicantStatus catalog stays empty so xApplicantStatusLookup cannot be supplied.

Upload Applicant Resource (Resume / Cover Letter) - Upload a resource file (resume, cover letter) to HR Cloud. The endpoint returns a resourceId that is then attached to an applicant via xResumeLookup / xCoverLetterLookup on create or update. NOTE: REQUIRES the HR Cloud Recruit app to be installed on the tenant (currently not installed by default — request via Settings → Explore Apps → Recruit → 'I'M INTERESTED'). Without it the endpoint returns 403 or empty results.

Update Applicant - Update Applicant via HR Cloud CoreHR REST API. NOTE: REQUIRES the HR Cloud Recruit app to be installed on the tenant (currently not installed by default — request via Settings → Explore Apps → Recruit → 'I'M INTERESTED'). Without it no xApplicant records exist to update.

Upsert Applicant - Update or create an Applicant via HR Cloud CoreHR REST API. If the Id is found the record is updated, otherwise a new applicant is created. NOTE: REQUIRES the HR Cloud Recruit app to be installed on the tenant (currently not installed by default — request via Settings → Explore Apps → Recruit → 'I'M INTERESTED'). Without it the xApplicantStatus catalog stays empty so new records cannot be created.

List Applicant Statuses - List xApplicantStatus records. Required for resolving xApplicantStatusLookup on create/update/upsert_applicant.

List Tasks - List Tasks via HR Cloud CoreHR REST API.

Get Task - Get Task via HR Cloud CoreHR REST API.

Create Task - Create a workflow task in the HR Cloud Portal, assigned to a group of employees, optionally tied to a specific HR application (coreHr, onboard, offboard, benefits).

List Employee Groups - List xEmployeeGroup records. Required for resolving `assignedEmployeeGroupId` on create_task.

Get Employee Group - Get a single xEmployeeGroup by Id.

List Bonus History - List Bonus History via HR Cloud CoreHR REST API.

Get Bonus History - Get Bonus History via HR Cloud CoreHR REST API.

List Salary History - List Salary History via HR Cloud CoreHR REST API.

List Rehire History - List Rehire History via HR Cloud CoreHR REST API.

Create Rehire History - Create a rehire history record (initiate a rehire workflow for an employee). NOTE; provider returns 400 "This action is not available for employment status 'Active'." when the target employee is currently Active. The action only succeeds when xEmployeeLookup points to an employee whose employment status is Terminated (or similar inactive status). Sandbox tenants typically lack pre-Terminated employees, so this action stays preview until tenant has seeded a rehire-eligible employee. Departmentaly some departments are blocked too — provider rejects with "Department can't be <name>" for certain default departments; use a real assignable department (e.g. "HR" with code Id 0d10e0b94428508eff2ba85b7de12569).

List Employment Status History - List Employment Status History via HR Cloud CoreHR REST API.

Create Employment Status History - Create a new employment status history entry (changes an employee's employment status). NOTE; provider returns 400 "There is already a pending change and new changes are disabled." for any employee with an in-flight (un-applied) status change. Once an employee has a pending change, the only way to clear it is to wait for the effective date and process the change in the HR Cloud UI. Test tenants quickly run out of employees in a "no pending change" state, so this action stays preview until callers can supply a fresh employee or wait out the pending state.

List Time Off Requests - List Time Off Requests via HR Cloud CoreHR REST API.

Get Time Off Request - Get Time Off Request via HR Cloud CoreHR REST API.

Create Time Off Request - Create Time Off Request via HR Cloud CoreHR REST API. NOTE: REQUIRES the HR Cloud Time Off app to be installed on the tenant (currently not installed by default — request via Settings → Explore Apps → Time Off → 'I'M INTERESTED'). Without it the endpoint returns 403 or empty results.

Upsert Time Off Request - Update or create a Time Off Request via HR Cloud CoreHR REST API. If a Time Off Request with the supplied Id exists it is updated, otherwise a new request is created. NOTE: REQUIRES the HR Cloud Time Off app to be installed on the tenant (currently not installed by default — request via Settings → Explore Apps → Time Off → 'I'M INTERESTED'). Without it the endpoint returns 403 or empty results.

List Time Off Accruals - List Time Off Accrual History records via HR Cloud CoreHR REST API. Each record represents an adjustment (positive or negative) to an employee's time off balance for a given Time Off Type. NOTE: REQUIRES the HR Cloud Time Off app to be installed on the tenant (currently not installed by default — request via Settings → Explore Apps → Time Off → 'I'M INTERESTED'). Without it the endpoint returns 403 or empty results.

List Time Off Balances - List employee Time Off Balances via HR Cloud CoreHR REST API. Balances are read-only computed roll-ups of an employee's accrual history and Time Off Requests for a given Time Off Type. NOTE: REQUIRES the HR Cloud Time Off app to be installed on the tenant (currently not installed by default — request via Settings → Explore Apps → Time Off → 'I'M INTERESTED'). Without it the endpoint returns 403 or empty results.

List Time Off Types - List xTimeOffType records. Required for resolving xTimeOffTypeLookup on create_time_off_request and upsert_time_off_request.

List Employee Attachments - List Employee Attachments via HR Cloud CoreHR REST API. NOTE: REQUIRES the HR Cloud Workmates app to be installed on the tenant (currently not installed by default — request via Settings → Explore Apps → Workmates → 'I'M INTERESTED'). Without it the endpoint returns 403 or empty results.

Get Employee Attachment - Get Employee Attachment via HR Cloud CoreHR REST API. NOTE: REQUIRES the HR Cloud Workmates app to be installed on the tenant (currently not installed by default — request via Settings → Explore Apps → Workmates → 'I'M INTERESTED'). Without it the endpoint returns 403 or empty results.

Create Employee Attachment - Upload an attachment file to an employee. Content-Type is multipart/form-data per HR Cloud docs. NOTE: REQUIRES the HR Cloud Workmates app to be installed on the tenant (currently not installed by default — request via Settings → Explore Apps → Workmates → 'I'M INTERESTED'). Without it the endpoint returns 403 or empty results.

Delete Employee Attachment - Delete Employee Attachment via HR Cloud CoreHR REST API. NOTE: REQUIRES the HR Cloud Workmates app to be installed on the tenant (currently not installed by default — request via Settings → Explore Apps → Workmates → 'I'M INTERESTED'). Without it the endpoint returns 403 or empty results.

Download Employee Attachment(s) - Download one or more attachments belonging to an employee. Omit attachmentIds to download ALL attachments as a single zip. Provide a single attachmentId for one file, or a comma-separated list for multiple files (returned as a zip). NOTE: REQUIRES the HR Cloud Workmates app to be installed on the tenant (currently not installed by default — request via Settings → Explore Apps → Workmates → 'I'M INTERESTED'). Without it the endpoint returns 403 or empty results.

List Employee Forms - List Employee Forms via HR Cloud CoreHR REST API.

Get Employee Form - Retrieve a single form record for an employee, identified by formType + formId.

Download Employee Form - Download one or all forms for an employee as a zip file. Pass formIdentifier (formType_formId) to download a single form, or leave it empty to download all forms in one zip.

HR Cloud AI Agent Use Cases

Connect your AI agent to HR Cloud and help your team scale the HR operations they run by hand today.

Employee Onboarding

Use StackOne to connect your AI agent to your HRIS, identity management, and LMS to automate employee onboarding.

View

HR Policy Q&A Chatbot

Use StackOne to connect your AI agent to your HRIS, knowledge base, and messaging tools to automate HR policy Q&A.

View

Job Posting Distribution

Use StackOne to connect your AI agent to your ATS and job boards to automate job posting distribution.

View

More HRIS & HCM use cases More Recruiting use cases

Do More, Build Less

Integration Infrastructure for HR Cloud AI Agents

Multiple Interfaces

Access integrations via API, AI SDKs, MCP & A2A.

HR Cloud MCP server

Managed Authentication

Pre-built authentication UI.

Agent auth

Falcon Engine

Every HR Cloud action runs on Falcon.

Agent Execution Engine

StackOne Defender

88.7% prompt injection detection.

Prompt injection defense

Start Free Book a Demo

"What impressed us most about StackOne is its ambition and clarity. They're creating infrastructure that modern software and the entire AI agent ecosystem can rely on. The depth of secure integrations, the pace of delivery, and the team's foresight into AI's future uniquely position StackOne to redefine this category."

Luna Schmid, Partner at GV

"We've been impressed by how quickly and deeply StackOne integrates with complex enterprise systems -- and now, with their focus on agent-to-agent interoperability, they're unlocking even more powerful use cases for customers. StackOne delivers all of the above in a universal layer -- without compromise."