Short answer: Drop the "Bitbucket → Create Pull Request" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
Title title | string | Required | Title. Example: Fix login redirect |
Source Branch source_branch | string | Required | Source Branch. Example: feature/login-fix |
Destination Branch destination_branch | string | Required | Destination Branch. Example: main |
Description description | string | Optional | Description |
Close Source Branch on Merge close_source_branch | options | Optional | Close Source Branch on Merge. Options: Yes, No |
{"workspace": "e.g. my-team","repo_slug": "e.g. my-project","title": "e.g. Fix login redirect","source_branch": "e.g. feature/login-fix","destination_branch": "e.g. main"}
{"id": 1,"links": {"html": {"href": "https://bitbucket.org/team/project/pull-requests/1"}},"state": "OPEN","title": "Fix login redirect"}
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.
Triggered by anything in the catalog. Free tier available. No credit card.