Expofp integration

Quick start

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

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

• EXPOFP_ADD_CATEGORY
• EXPOFP_DELETE_EXHIBITOR
• EXPOFP_DELETE_SESSION_SPEAKERS
• EXPOFP_DELETE_SESSION_TRACKS
• EXPOFP_GET_BULK_READ_EXHIBITORS_TEMPLATE
• EXPOFP_GET_OFFLINE_ARCHIVE
• EXPOFP_GET_OR_CREATE_OFFLINE_ARCHIVE
• EXPOFP_GET_SESSION_TRACKS
• EXPOFP_LIST_ALL_EXPO_EXTRAS
• EXPOFP_LIST_ALL_EXPOS
• EXPOFP_LIST_CATEGORIES
• EXPOFP_LIST_EXHIBITORS