HR Partner MCP integration for AI agents.
Connect AI agents to HR Partner through 10 structured actions, including get applicant, get application, and get company. Review authentication, inputs, work…
- ACTION CONTRACTS
- 10
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the HR Partner integration exposes
The HR Partner Agent App exposes 10 provider-backed actions for productivity work. Its current contract lets an authorized agent retrieve one hr partner recruitment applicant by applicant id or email address, including their job applications when available, retrieve one hr partner recruitment application by application id, including applicant, job listing, scorecard, attachment metadata, interviews, and comments when available, and retrieve basic hr partner company information, optionally including custom fields and active modules. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected HR Partner account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real HR Partner capabilities.
Showing 10 of 10 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_applicantREADRetrieve one HR Partner recruitment applicant by applicant ID or email address, including their job applications when available.
INPUTS: applicant_id
get_applicationREADRetrieve one HR Partner recruitment application by application ID, including applicant, job listing, scorecard, attachment metadata, interviews, and comments when available.
INPUTS: application_id
get_companyREADRetrieve basic HR Partner company information, optionally including custom fields and active modules.
INPUTS: custom_fields / active_modules
get_employeeREADRetrieve one HR Partner employee by employee code, including detailed contact, address, tag, and custom field data when available.
INPUTS: employee_code
get_job_listingREADRetrieve one HR Partner recruitment job listing by job ID, including detailed content, custom form, scorecard, and stage data when available.
INPUTS: job_id
list_applicantsREADList HR Partner recruitment applicants, optionally filtered by name or email search text.
INPUTS: search
list_applicationsREADList HR Partner recruitment applications for one job listing with official filters such as source, stage, submitted date, and read flags.
INPUTS: job_id / source / stage / submitted_at_from / submitted_at_to
list_employeesREADList HR Partner employees with official filters such as search, department, location, status, tags, and employment dates.
INPUTS: search / department / location / group / position
list_job_listingsREADList HR Partner recruitment job listings with official filters such as search, department, publish dates, active state, and response email.
INPUTS: search / department / location / position / employment_status
list_lookupsREADRetrieve one HR Partner read-only lookup file such as departments, locations, positions, tags, stages, or training statuses.
INPUTS: lookup_name
INPUT CONTRACTS
Know what the action needs before it runs.
get_applicant
applicant_idREQUIRED- The HR Partner applicant ID or email address.
get_application
application_idREQUIRED- The HR Partner application ID.
get_company
custom_fieldsOPTIONAL- Whether to include configured company custom field definitions.
active_modulesOPTIONAL- Whether to include enabled HR Partner modules and feature flags.
get_employee
employee_codeREQUIRED- The HR Partner employee code.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Applicant
Retrieve one HR Partner recruitment applicant by applicant ID or email address, including their job applications when available. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_applicantVerify with Get Application
Retrieve one HR Partner recruitment application by application ID, including applicant, job listing, scorecard, attachment metadata, interviews, and comments when available. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_applicationSAFETY BOUNDARY
Operate HR Partner with explicit limits
- Authorize HR Partner with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned HR Partner data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in HR Partner rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the HR Partner task completed successfully.
CONNECTION MODEL
API key
HR Partner API key sent with the x-api-key header. Generate or manage API keys from your HR Partner account's API settings: https://developer.hrpartner.io/#authentication
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 10
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by HR Partner.