Hub Planner integration

Quick start

Call Hub Planner from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to Hub Planner'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(
  "HUB_PLANNER_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

End-users supply their own Hub Planner API key. OverSkill provides a pre-built connection form via the integration card — your app can call the composio client immediately once the user has connected.

Available actions

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

• HUB_PLANNER_ADD_CLIENTS_TO_PROJECT
• HUB_PLANNER_ADD_PROJECT_CUSTOM_FIELD_CHOICES
• HUB_PLANNER_ADD_PROJECTS_TO_GROUP
• HUB_PLANNER_ADD_PROJECT_TAGS
• HUB_PLANNER_ADD_RESOURCE_CUSTOM_FIELD_CHOICES
• HUB_PLANNER_ADD_RESOURCES_TO_PROJECT
• HUB_PLANNER_ADD_RESOURCES_TO_RESOURCE_GROUP
• HUB_PLANNER_ADD_RESOURCE_TAGS
• HUB_PLANNER_CREATE_BILLING_RATE
• HUB_PLANNER_CREATE_BOOKING
• HUB_PLANNER_CREATE_BOOKING_CATEGORY
• HUB_PLANNER_CREATE_CLIENT