ActionBitbucketUpdated May 2026

How do I programmatically merge a Bitbucket PR?

Short answer: Drop the "Bitbucket → Merge Pull Request" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 10 Bitbucket actions

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Merge Pull Request support batch operations?

Yes. Run Merge Pull Request inside a Loop node to process arrays. Tiny Command handles Bitbucket's rate limits automatically so you don't have to throttle manually.

More actions