LeadBoxer integration

Quick start

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

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

• LEADBOXER_ADD_OR_UPDATE_LEAD_TAGS
• LEADBOXER_DELETE_CTD
• LEADBOXER_GET_EVENTS
• LEADBOXER_GET_LEAD_SCORE_FORMULA
• LEADBOXER_GET_SESSIONS
• LEADBOXER_LOG_EVENT
• LEADBOXER_MANAGEMENT_CTD
• LEADBOXER_POST_EVENT
• LEADBOXER_VIEWS_LEAD_DETAIL