ActionBitbucketUpdated September 2026

How do I programmatically merge a Bitbucket PR?

Short answer: You can merge pull request in Bitbucket by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Bitbucket Merge Pull Request action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Merge Pull Request in Bitbucket — start free All 10 Bitbucket actions

Merge Pull Request in Bitbucket — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Workspace workspace	string	Required	Workspace. Example: my-team
Repository Slug repo_slug	string	Required	Repository Slug. Example: my-project
PR ID pr_id	string	Required	PR ID. Example: 42
Merge Strategy merge_strategy	options	Optional	Merge Strategy. Options: Merge Commit, Squash, Fast-Forward
Close Source Branch close_source_branch	options	Optional	Close Source Branch. Options: Yes, No

Sample request

{
  "workspace": "e.g. my-team",
  "repo_slug": "e.g. my-project",
  "pr_id": "e.g. 42",
  "merge_strategy": "{{trigger.merge_strategy}}",
  "close_source_branch": "{{trigger.close_source_branch}}"
}

Returns

{
  "id": 42,
  "state": "MERGED",
  "merge_commit": {
    "hash": "abc123"
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Merge Pull Request.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Bitbucket

2 Google Sheets triggers

HubSpot → Bitbucket

18 HubSpot triggers

FAQ

Questions about Merge Pull Request.

What does the Merge Pull Request action do in Bitbucket?

Merges a PR using the configured strategy (merge_commit, squash, fast_forward). Requires CI to pass and reviewers to approve per branch protection. Useful for auto-merge bots that wait for green CI + approvals and merge automatically.

What inputs does Merge Pull Request require?

Required: Workspace, Repository Slug, PR ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Bitbucket returns an error?

The run history shows the failed step with its input and the error message Bitbucket returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Merge Pull Request support batch operations?

Run Merge Pull Request inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Bitbucket's rate limits.

More actions