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.
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 |
{"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}}"}
{"id": 42,"state": "MERGED","merge_commit": {"hash": "abc123"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
