ceven

Bitbucket

Syncs your code reviews and issue tracking with your project management tools, automates the creation of development branches from tickets, and monitors pull request status for release notes.

Try Bitbucket in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Bitbucket integration

    • Describe the outcome and Ceven picks the right Bitbucket calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Bitbucket data, across all 105 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Bitbucket access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Bitbucket, when, and on whose behalf.
    • The agent pauses and asks when Bitbucket is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Bitbucket.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Bitbucket action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Bitbucket, and when to use it.

Create branch
Use this when a new feature or bug fix needs a dedicated branch based on a specific commit hash.
Create issue
Log a new bug or task in a repository and assign it to a user with the right permissions.
Create issue comment
Add a markdown formatted comment to an existing issue to provide updates or feedback.
Create pull request
Open a pull request to merge changes from a source branch into a destination branch.
Create repository
Initialize a new git repository within a workspace, optionally specifying a project key.
Create snippet comment
Post a new comment or a threaded reply to a shared code snippet.
Delete issue
Permanently remove a specific issue from a repository using the issue id.
Delete repository
Permanently delete a repository. This is an irreversible action that does not affect forks.
Get current user
Pull profile details for the authenticated user including uuid and display name.
Get file
Retrieve the raw content of a specific file at a given commit, branch, or tag.
Get pull request
Pull full details for a single pull request by its unique id.
List pull requests
List pull requests in a repository, filtered by open, merged, or declined states.
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.
Get file from repository
Retrieves a specific file's content from a bitbucket repository at a given commit (hash, branch, or tag), failing if the file path is invalid for that commit.
Get snippet
Retrieves a specific bitbucket snippet by its encoded id from an existing workspace, returning its metadata and file structure.
List repositories in workspace
Lists repositories in a specified bitbucket workspace, accessible to the authenticated user, with options to filter by role or query string, and sort results.
List workspace members
Lists all members of a specified bitbucket workspace; the workspace must exist.
List workspaces
Lists bitbucket workspaces accessible to the authenticated user, optionally filtered and sorted.
Update an issue
Updates an existing issue in a bitbucket repository by modifying specified attributes; requires `workspace`, `repo slug`, `issue id`, and at least one attribute to update.

22 actions · scroll to see them all

Frequently asked questions

Ceven operates using the permissions of the user who authorized the OAuth2 connection. If the authenticated user has read only access to a specific repository, the agent cannot create branches or merge pull requests in that repo. We do not bypass Bitbucket access control lists. When a workflow attempts a write action, Bitbucket validates the token scope and user permissions in real time. If the action is denied, Ceven returns a clear permission error to the workflow log. This ensures that your internal security policies and repository restrictions remain the final authority on who can modify code or delete issues.
Yes. Ceven connects to Bitbucket webhooks to listen for specific events like pull request creation, commit pushes, or issue updates. When an event fires, Bitbucket sends a payload to Ceven, which then matches the event to your configured workflow. For example, you can set up a trigger where a merged pull request automatically prompts the agent to update a deployment log or send a notification to a Slack channel. This allows you to build a reactive development pipeline where code changes drive the rest of your business processes without manual intervention.
No. Ceven does not clone or store your entire repository. When a workflow needs to read a file or a pull request, the agent makes a targeted API call to Bitbucket to retrieve that specific piece of data. The content is held in volatile memory only for the duration of the prompt processing and is not used to train global models. We treat your source code as highly sensitive data. All transit occurs over encrypted channels, and the agent only accesses the specific files or metadata required to complete the task you requested.
Bitbucket imposes rate limits on its API to ensure platform stability. If Ceven encounters a rate limit error, the agent implements an exponential backoff strategy, pausing the workflow and retrying the request after the suggested wait period. For very large workspaces with thousands of repositories, we recommend optimizing your workflows to use filters rather than listing all resources. If you consistently hit limits during heavy backfills, you can schedule your synchronization workflows to run during off peak hours to avoid contention with your team's manual API usage.
Yes. Ceven can retrieve snippets and post comments to them. This is particularly useful for knowledge sharing workflows. You can set up a process where the agent monitors a specific channel for common technical questions and then searches your Bitbucket snippets for a relevant code example to share. Once the snippet is found, the agent can post the link and even add a new comment to the snippet to track how often it is being used as a reference by the team.
Ceven allows you to select which workspaces the agent can access during the OAuth flow. Once connected, you can specify the workspace slug in your workflow actions. The agent can list all available workspaces the user has access to, making it easy to switch contexts between different projects or clients. If you manage multiple clients in separate workspaces, you can build a single workflow that iterates through them to generate a global report on open pull requests or pending security issues across your entire organization.
Ceven is subject to the response size limits of the Bitbucket API. For extremely large files, the API may truncate the response or return an error. To handle this, we recommend using the agent to read specific files or diffs rather than attempting to ingest massive binary files or giant monolithic logs. If a file is too large for a single prompt window, the agent can be instructed to read the file in chunks if the API supports range requests, though for most code files, the standard retrieval is sufficient.
Yes. You can build a cleanup workflow that lists all branches in a repository, checks their last commit date, and cross references them with merged pull requests. If a branch was merged more than thirty days ago and has no active activity, the agent can call the delete branch action. This keeps your repository clean and prevents the branch list from becoming cluttered. You can also add a step to notify the original branch creator via email or chat before the deletion occurs to ensure no unpushed work is lost.

Alternatives to Bitbucket

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

GitHub logoGitHubGitLab logoGitLabAzure DevOps logoAzure DevOps

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Bitbucket and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free