Crustdata integration

Quick start

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

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

• CRUSTDATA_ENRICH_PERSON_SCREENER
• CRUSTDATA_FETCH_HEADCOUNT_BY_FACET_TIMESERIES
• CRUSTDATA_FETCH_INVESTOR_PORTFOLIO_DATA
• CRUSTDATA_FILTER_DECISION_MAKERS_DATA
• CRUSTDATA_POST_FUNDING_MILESTONE_TIME_SERIES_DATA
• CRUSTDATA_POST_HEADCOUNT_TIMESERIES_DATA
• CRUSTDATA_POST_JOB_LISTINGS_TABLE_DATA
• CRUSTDATA_POST_WEB_TRAFFIC_DATA
• CRUSTDATA_RETRIEVE_LINKED_IN_POSTS
• CRUSTDATA_SCREENER_COMPANY_INFORMATION
• CRUSTDATA_SCREEN_METRICS_AND_FILTER_CONDITIONS
• CRUSTDATA_SEARCH_COMPANIES_WITH_FILTERS