Graphhopper integration

Quick start

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

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

• GRAPHHOPPER_CLUSTER_POST
• GRAPHHOPPER_GEOCODE_GET
• GRAPHHOPPER_GET_CLUSTER_SOLUTION
• GRAPHHOPPER_GET_MATRIX
• GRAPHHOPPER_GET_MATRIX_SOLUTION
• GRAPHHOPPER_GET_ROUTE
• GRAPHHOPPER_ISOCHRONE_GET
• GRAPHHOPPER_MATRIX_POST
• GRAPHHOPPER_PROFILES_GET
• GRAPHHOPPER_ROUTE_POST
• GRAPHHOPPER_SUBMIT_MATRIX_JOB
• GRAPHHOPPER_UPLOAD_GPX_FILE