+
Connect Bitbucket to GitHub
Automate Bitbucket and GitHub with AI
Teams mirroring repos across Bitbucket and GitHub lose track of which side has the latest branch and open reviews. Operator.io points OpenClaw at Bitbucket and GitHub so new pull requests on one show up against the matching repo on the other, merge state stays in step, and an issue opened in one can be copied to the other with the link kept. Tell it what is awaiting review and it lists open pull requests from both Bitbucket and GitHub in one reply.
It reaches both apps directly or through connectors like Composio MCP and Pipedream MCP, which handle the sign in and token refresh, so there is no Zap to build and no API keys to paste.
What your agent can do with Bitbucket and GitHub
What your agent does in Bitbucket
Approve Pull Request
Tool to approve a pull request as the authenticated user. Use when you need to formally approve changes in a pull request review process.
Browse repository path
Tool to retrieve content for a file path or browse directory contents at a specified revision in a Bitbucket repository. Use when you need flexible access to repository content - returns raw file data for files or paginated directory lis...
Create a branch
Creates a new branch in a Bitbucket repository from a target commit hash; the branch name must be unique, adhere to Bitbucket's naming conventions, and not include the 'refs/heads/' prefix.
Create an issue
Creates a new issue in a Bitbucket repository, setting the authenticated user as reporter; ensures assignee (if provided) has repository access, and that any specified milestone, version, or component IDs exist.
Create an issue comment
Adds a new comment with markdown support to an existing Bitbucket issue.
Create a pull request
Creates a new pull request in a specified Bitbucket repository, ensuring the source branch exists and is distinct from the (optional) destination branch.
What your agent does in GitHub
Abort Repository Migration
Tool to abort a repository migration that is queued or in progress. Use when you need to cancel an ongoing migration operation.
Accept a repository invitation
Accepts a PENDING repository invitation that has been issued to the authenticated user.
Add app access restrictions
Adds GitHub Apps to the list of apps allowed to push to a protected branch. The branch must already have protection rules with restrictions enabled. This endpoint only works for organization repositories, not personal repositories. Apps...
Add a repository collaborator
Adds a GitHub user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation ma...
Add assignees to an issue
Adds assignees to a GitHub issue. This action only adds users - it does not remove existing assignees. Changes are silently ignored if the authenticated user lacks push access to the repository.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's GitHub account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the...
How it works
Tell the agent what you want to happen between Bitbucket and GitHub, for example to watch one and act in the other, or to keep the two in step. It reads what it needs from Bitbucket, works out what to do, and runs the matching action in GitHub without you mapping a single field.
You can have it run once, on a schedule, or whenever something changes. Ask it for a status any time and it reads the latest from both apps back to you in the same chat.
Common questions about Bitbucket and GitHub
- How do I connect Bitbucket and GitHub to Operator?
- You authorize Bitbucket and GitHub once each from your Operator dashboard. Operator holds both connections and refreshes the access tokens for you, so your agent keeps working across them without you signing in again.
- What can my agent do across Bitbucket and GitHub?
- You describe the outcome in plain language and your agent works between the two, reading from one and acting in the other. It picks the right Bitbucket and GitHub actions on its own, so you do not map fields or pick triggers.
- Can my agent keep Bitbucket and GitHub in sync?
- Yes. It can watch Bitbucket and act in GitHub, or keep both in step, reading from one and running the matching update in the other. This runs on demand when you ask or on a schedule you set.
- Do I need to build a workflow or write code?
- No. There is no workflow to build, no fields to map, and no API keys to paste. Operator manages both connections, and you give the agent instructions in plain language.
Bitbucket and GitHub integrations
Put your agent on Bitbucket and GitHub
Sign in, connect both apps, and hand your agent the work. The same setup reaches every app in the catalog. Your first week is free.
Try for free