Apaleo integration

Quick start

Call Apaleo from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to Apaleo's public Composio identifier — your app references it by name and OverSkill handles the OAuth round-trip.

// In your generated app's worker handler:
const composio = composioClient(env);

const result = await composio.execute(
  "APALEO_ACTION_NAME",
  { /* action parameters — see Actions section below */ }
);

return new Response(JSON.stringify(result), {
  headers: { "Content-Type": "application/json" }
});

Replace ACTION_NAME with one of the slugs listed in the Actions section below. The composio client handles auth + rate limits automatically — no API key is exposed to user code.

Setup

OverSkill hosts the OAuth application for Apaleo. End-users click Connect on the integration card in your app, complete the OAuth flow with Apaleo, and OverSkill stores the access token scoped to their account. No client_id / client_secret configuration needed on your side.

Supported auth schemes: OAUTH2.

Available actions

29 actions exposed via the Apaleo integration. Each maps to a callable slug — pass it to composio.execute(...) in your worker code.

• APALEO_ARCHIVE_A_PROPERTY
• APALEO_CHECK_IF_A_PROPERTY_EXISTS
• APALEO_CHECK_IF_A_UNIT_ATTRIBUTE_EXISTS
• APALEO_CHECK_IF_A_UNIT_EXISTS
• APALEO_CHECK_IF_A_UNIT_GROUP_EXISTS
• APALEO_CLONES_A_PROPERTY
• APALEO_CREATE_A_UNIT
• APALEO_CREATE_A_UNIT_ATTRIBUTE
• APALEO_CREATE_A_UNIT_GROUP
• APALEO_CREATE_MULTIPLE_UNITS
• APALEO_CREATES_A_PROPERTY
• APALEO_DELETE_A_UNIT