What this operation supports in Bitbucket
Makes a direct call to any Bitbucket API endpoint that doesn't already have its own dedicated action.
Implementation details
This is a fallback for API surface area outside the dedicated actions already available, like certain pipeline or webhook endpoints, rather than a replacement for those dedicated actions where one already exists.
Operational considerations
Since this bypasses the validation a dedicated action would normally provide, the endpoint path and payload need to match Bitbucket's API documentation exactly rather than relying on built-in field mapping.
Use cases
Generic API call to Bitbucket used to initiate actions from external systems.
- Trigger a build or deployment step in Bitbucket from an external CI system.
- Query repository metadata to align automation decisions with Bitbucket data.
- Push status updates to Bitbucket via a single API call in a pipeline.
- Fetch contextual data to enrich automation decisions using Bitbucket as the data source.