Interact with the Bitbucket Cloud API using the Bitbucket Agent Node
The Bitbucket Agent Node is a powerful component in the Pathlit workflow builder that allows you to interact with the Bitbucket Cloud API. This node enables you to automate tasks and queries within your Bitbucket repositories, such as retrieving pull requests, branches, commits, and source code information.
To set up the Bitbucket Agent Node, you need to configure the following parameters:
Repository URL:
The URL of the Bitbucket repository you want to interact with. This should be in the format https://bitbucket.org/{workspace}/{repo}
.
Query:
A command or question that instructs the agent on what to do, such as “What are the latest pull requests?”
Inputs:
Outputs:
Pull Request Management:
Automate the retrieval of pull request details for review or reporting purposes. The node can fetch the latest pull requests and provide summaries or details as required.
Branch Monitoring:
Set up workflows to monitor branch updates or changes. This can be useful for continuous integration and deployment pipelines where branch status is critical.
Commit Analysis:
Use the node to analyze recent commits for code changes, review purposes, or audit trails. This can help in maintaining code quality and tracking changes.
Source Code Retrieval:
Automate the retrieval of specific source code files or directories for backup, analysis, or deployment purposes.
Invalid Bitbucket URL:
Ensure the repository URL is correctly formatted and points to a valid Bitbucket repository. The node will raise an error if the URL is not a bitbucket.org
URL or if it cannot extract the repository details.
Authentication Issues:
If the node cannot access the Bitbucket API, check that the authentication token is valid and that you have the necessary permissions. Re-authenticate if necessary.
Unsupported Model:
Ensure that the selected model supports function calling. If not, choose a compatible model from the available options.
If you encounter any issues with the Bitbucket Agent Node that are not covered in this documentation, please reach out to our support team for assistance.
Trigger workflows based on incoming emails
Route input data based on specified prompts and options
Import files from Google Drive into your workflow