Brilliant Directories integration

Quick start

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

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

• BRILLIANT_DIRECTORIES_CREATE_ALBUM_PHOTO
• BRILLIANT_DIRECTORIES_CREATE_DATA_CATEGORY
• BRILLIANT_DIRECTORIES_CREATE_DATA_POST
• BRILLIANT_DIRECTORIES_CREATE_LEAD
• BRILLIANT_DIRECTORIES_CREATE_PORTFOLIO_GROUP
• BRILLIANT_DIRECTORIES_CREATE_UNSUBSCRIBE
• BRILLIANT_DIRECTORIES_CREATE_USER
• BRILLIANT_DIRECTORIES_CREATE_USERS_CLICK
• BRILLIANT_DIRECTORIES_CREATE_WIDGET
• BRILLIANT_DIRECTORIES_DELETE_ALBUM_PHOTO
• BRILLIANT_DIRECTORIES_DELETE_DATA_CATEGORY
• BRILLIANT_DIRECTORIES_DELETE_LEAD