Breezy HR MCP integration for AI agents.
Connect AI agents to Breezy HR through 8 structured actions, including get candidate, get company, and get current user. Review authentication, inputs, workf…
- ACTION CONTRACTS
- 8
- 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 Breezy HR integration exposes
The Breezy HR Agent App exposes 8 provider-backed actions for productivity and communication work. Its current contract lets an authorized agent retrieve one breezy hr candidate by company, position, and candidate id, retrieve one breezy hr company by id, and retrieve the currently authenticated breezy hr user profile. 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 Breezy HR account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Breezy HR capabilities.
Showing 8 of 8 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_candidateREADRetrieve one Breezy HR candidate by company, position, and candidate ID.
INPUTS: companyId / positionId / candidateId
get_companyREADRetrieve one Breezy HR company by ID.
INPUTS: companyId
get_current_userREADRetrieve the currently authenticated Breezy HR user profile.
get_positionREADRetrieve one Breezy HR position by company and position ID.
INPUTS: companyId / positionId
list_companiesREADList Breezy HR companies available to the connected account.
list_position_candidatesREADList candidates on one Breezy HR position with optional page filters.
INPUTS: companyId / positionId / pageSize / page / sort
list_positionsREADList Breezy HR positions for a company with optional state and page filters.
INPUTS: companyId / state / pageSize / page / sort
search_candidates_by_emailREADSearch company-wide Breezy HR candidates by exact normalized email address.
INPUTS: companyId / emailAddress
INPUT CONTRACTS
Know what the action needs before it runs.
get_candidate
companyIdREQUIRED- The Breezy HR resource ID.
positionIdREQUIRED- The Breezy HR resource ID.
candidateIdREQUIRED- The Breezy HR resource ID.
get_company
companyIdREQUIRED- The Breezy HR resource ID.
get_position
companyIdREQUIRED- The Breezy HR resource ID.
positionIdREQUIRED- The Breezy HR resource ID.
list_position_candidates
companyIdREQUIRED- The Breezy HR resource ID.
positionIdREQUIRED- The Breezy HR resource ID.
pageSizeOPTIONAL- The number of candidates to return when opting into pagination. Breezy caps this value at 50.
pageOPTIONAL- The zero-based Breezy HR page number.
sortOPTIONAL- The Breezy HR sort field, such as updated.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Candidate
Retrieve one Breezy HR candidate by company, position, and candidate ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_candidateVerify with Get Company
Retrieve one Breezy HR company by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_companySAFETY BOUNDARY
Operate Breezy HR with explicit limits
- Authorize Breezy HR with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Breezy HR 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 Breezy HR rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Breezy HR task completed successfully.
CONNECTION MODEL
API key
Breezy HR Personal Access Token sent as the Authorization header value. Manage API access from Breezy HR company settings under Integrations > API: https://developer.breezy.hr/reference/customer-guide
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
- 8
- 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 Breezy HR.