Supabase integration

Quick start

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

OverSkill hosts the OAuth application for Supabase. End-users click Connect on the integration card in your app, complete the OAuth flow with Supabase, and OverSkill stores the access token scoped to their account. No client_id / client_secret configuration needed on your side.

Supported auth schemes: OAUTH2, API_KEY.

Available actions

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

• SUPABASE_ALPHA_CREATE_API_KEY
• SUPABASE_ALPHA_DELETE_API_KEY
• SUPABASE_ALPHA_DELETE_THIRD_PARTY_AUTH_INTEGRATION
• SUPABASE_ALPHA_GET_THIRD_PARTY_INTEGRATION
• SUPABASE_ALPHA_LIST_THIRD_PARTY_AUTH_INTEGRATIONS
• SUPABASE_ALPHA_UPDATE_API_KEY
• SUPABASE_APPLY_A_MIGRATION
• SUPABASE_BETA_ACTIVATE_CUSTOM_HOSTNAME
• SUPABASE_BETA_ACTIVATE_VANITY_SUBDOMAIN
• SUPABASE_BETA_AUTHORIZE_USER_THROUGH_OAUTH
• SUPABASE_BETA_CHECK_VANITY_SUBDOMAIN_AVAILABILITY
• SUPABASE_BETA_CREATE_READ_REPLICA