apaleo MCP integration for AI agents.
Connect AI agents to apaleo through 29 structured actions, including check property exists, create multiple units, archive property, and clone property. Revi…
- ACTION CONTRACTS
- 29
- AUTHENTICATION
- OAuth 2.0
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the apaleo integration exposes
The apaleo Agent App exposes 29 provider-backed actions for productivity and finance work. Its current contract lets an authorized agent check whether a property exists by id, create multiple units in a single bulk request, and archive a live property by id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0. 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 apaleo account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real apaleo capabilities.
Showing 12 of 29 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
check_property_existsREADCheck whether a property exists by ID.
INPUTS: id
create_multiple_unitsWRITECreate multiple units in a single bulk request.
INPUTS: units / idempotencyKey
archive_propertyHIGH IMPACTArchive a live property by ID.
INPUTS: id
clone_propertyREVIEWClone an existing property into a new property with inventory and rate plans.
INPUTS: code / name / companyName / managingDirectors / commercialRegisterEntry
check_unit_attribute_existsREADCheck whether a unit attribute definition exists by ID.
INPUTS: id
check_unit_existsREADCheck whether a unit exists by ID.
INPUTS: id
check_unit_group_existsREADCheck whether a unit group exists by ID.
INPUTS: id
count_propertiesREADReturn the total number of properties accessible to the connected apaleo account.
count_unit_groupsREADReturn the total number of unit groups matching the provided filters.
INPUTS: propertyId / unitGroupTypes
count_unitsREADReturn the total number of units matching the provided filters.
INPUTS: propertyId / unitGroupId / unitGroupIds / unitAttributeIds / isOccupied
create_propertyWRITECreate a new property in apaleo.
INPUTS: code / name / companyName / managingDirectors / commercialRegisterEntry
create_unitWRITECreate a new unit.
INPUTS: propertyId / name / description / unitGroupId / maxPersons
INPUT CONTRACTS
Know what the action needs before it runs.
check_property_exists
idOPTIONAL- The apaleo resource ID.
create_multiple_units
unitsREQUIRED- Units to create in bulk.
idempotencyKeyOPTIONAL- Optional idempotency key used to safely retry the request.
archive_property
idOPTIONAL- The apaleo resource ID.
clone_property
codeREQUIRED- Property code shown in reports and table views.
nameREQUIRED- Localized property name.
companyNameREQUIRED- Legal company name for the property.
managingDirectorsOPTIONAL- Managing directors shown on invoices.
commercialRegisterEntryREQUIRED- Commercial register entry shown on invoices.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Check Property Exists
Check whether a property exists by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
check_property_existsControl Create Multiple Units
Create multiple units in a single bulk request. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_multiple_unitsVerify with Check Unit Attribute Exists
Check whether a unit attribute definition exists by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
check_unit_attribute_existsSAFETY BOUNDARY
Operate apaleo with explicit limits
- Authorize apaleo with OAuth 2.0 and grant only the provider access required by the selected actions.
- 10 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `archive_property`, `delete_unit`, and `delete_unit_attribute` as high-impact operations and require an explicit approval boundary.
- The sampled contract declares provider scopes including `apaleo.properties.manage`, `apaleo.unit_attributes.read`, `apaleo.units.read`, and `apaleo.unit_groups.read`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the apaleo task completed successfully.
CONNECTION MODEL
OAuth 2.0
apaleo uses OAuth 2.0. Connection requirements and availability are determined by the provider and the Working Machines deployment.
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
- 16
- WRITE SIGNALS
- 6
- HIGH IMPACT
- 4
- REVIEW SIGNALS
- 3
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 apaleo.