Integration · Developer
AI agents for Bitbucket
Comment on and read pull requests, and start Bitbucket Pipelines, in the Bitbucket Cloud repositories your Atlassian API token can reach.
- Actions
- 3
- Read
- 1
- Write
- 2
Actions
What your agents can do in Bitbucket
3 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 1
Look things up. Nothing changes.
Get a pull request
Reads one pull request by its ID: title, description, state (OPEN, MERGED, DECLINED or SUPERSEDED), author, source and destination branches, and web address.
Write 2
Create, change or send.
Comment on a pull request
Adds a comment in Markdown to a pull request, by its ID.
Run a pipeline
Starts Bitbucket Pipelines on the latest commit of a branch or tag.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Enter the API credentials from your Bitbucket account.
What you enter
- Atlassian account email
- API token
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Bitbucket data
Ask a question in plain words. The agent can get a pull request in Bitbucket, then answers with what it found.
- 02
Let an agent update Bitbucket
Have the agent comment on a pull request or run a pipeline in Bitbucket as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Bitbucket and Slack: it can get a pull request in Bitbucket and post a summary to a Slack channel in the same run.
Works well with
More Developer tools
- GitHub4 actionsOpen and comment on issues, and start GitHub Actions workflows, in the repositories a personal access token can reach.
- GitLab4 actionsOpen and comment on issues, and start CI/CD pipelines, in the GitLab.com projects an access token can reach.
- Sentry3 actionsList, read, resolve and ignore error issues in a sentry.io organization, in its US or EU (Germany) data region.
- Datadog2 actionsPost events to the Datadog Event Explorer and send custom metric points, on any Datadog site, with an API key.
- PagerDuty4 actionsOpen, acknowledge and resolve PagerDuty incidents, add notes to them, and see who is on call for a schedule.
- App Store Connect8 actionsLook after iPhone, iPad and Mac apps on Apple's App Store.
FAQ
Bitbucket and MyDeepAgents
Can MyDeepAgents connect to Bitbucket?
Yes. The Bitbucket connector has 3 actions: 1 reads and 2 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Bitbucket?
Enter the API credentials from your Bitbucket account. You'll need: Atlassian account email and API token. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Bitbucket without asking?
Only if you let it. Each of the 2 actions that change data can be set to wait for a person's approval before it runs.
Can I use Bitbucket in workflows as well as agents?
Yes. Every Bitbucket action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Bitbucket to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.