Bitbucket integration

Quick start

Call Bitbucket from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to Bitbucket'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(
  "BITBUCKET_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 Bitbucket. End-users click Connect on the integration card in your app, complete the OAuth flow with Bitbucket, and OverSkill stores the access token scoped to their account. No client_id / client_secret configuration needed on your side.

Supported auth schemes: OAUTH2.

Available actions

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

• BITBUCKET_APPROVE_PULL_REQUEST
• BITBUCKET_BROWSE_REPOSITORY_PATH
• BITBUCKET_CREATE_BRANCH
• BITBUCKET_CREATE_ISSUE
• BITBUCKET_CREATE_ISSUE_COMMENT
• BITBUCKET_CREATE_PULL_REQUEST
• BITBUCKET_CREATE_PULL_REQUEST_COMMENT
• BITBUCKET_CREATE_REPOSITORIES_COMMIT_REPORTS_ANNOTATIONS
• BITBUCKET_CREATE_REPOSITORIES_COMMITS2
• BITBUCKET_CREATE_REPOSITORY
• BITBUCKET_CREATE_SNIPPET_COMMENT
• BITBUCKET_CREATE_TEAMS_PIPELINES_CONFIG_VARIABLES