Trigger Pipeline
bitbucket.trigger_pipeline
ActionBusiness appsconnection required
Calls the Bitbucket API with the connection's credentials.
Run a repository's pipeline on a branch.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Username & password
- Providers
- Bitbucket
- Secret shape
- the app password, or {"app_password": "…"}
- Config it needs
- workspace, user
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
repo Repository slug. | string | Yes | — | — | — |
branch Branch (default main). | string | No | — | — | — |
Output
One shape.
result
The provider's response object, as returned.
Extra keys beyond the ones listed can appear.
{}Related Bitbucket nodes
Solutions with Bitbucket
See Trigger Pipeline run in a workflow.
In a technical demo we add the Bitbucket connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.