Neon integration

Quick start

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

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

• NEON_ACCEPT_PROJECTS_TRANSFER_REQUESTS
• NEON_ACCESS_PROJECT_DETAILS_BY_ID
• NEON_ADD_NEW_JWKS_TO_PROJECT_ENDPOINT
• NEON_ADD_PROJECT_EMAIL_PERMISSION
• NEON_ADD_ROLE_TO_BRANCH
• NEON_COUNT_PROJECT_BRANCHES
• NEON_CREATE_API_KEY_FOR_ORGANIZATION
• NEON_CREATE_AUTH_KEYS
• NEON_CREATE_AUTH_USER
• NEON_CREATE_BRANCH_DATABASE
• NEON_CREATE_BRANCHES_AUTH
• NEON_CREATE_BRANCHES_DATA_API