How to add pr comment in Bitbucket

Add PR Comment 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
Comment content	string	Required	Comment. Example: LGTM! Ship it.

Sample request

{
  "workspace": "e.g. my-team",
  "repo_slug": "e.g. my-project",
  "pr_id": "e.g. 42",
  "content": "e.g. LGTM! Ship it."
}

Returns

{
  "id": 1,
  "content": {
    "raw": "LGTM! Ship it."
  },
  "created_on": "2025-01-15T12:00:00Z"
}

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

FAQ

Questions about Add PR Comment.

What does the Add PR Comment action do in Bitbucket?

Posts a comment on a pull request. Useful for AI-driven code-review bots, for cross-tool notifications ("Linear issue X closed → comment on the linked PR"), or for automated linting/style feedback.

What inputs does Add PR Comment require?

Required: Workspace, Repository Slug, PR ID, Comment. 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 Add PR Comment support batch operations?

Yes. Run Add PR Comment inside a Loop node to process arrays. TinyCommand handles Bitbucket's rate limits automatically so you don't have to throttle manually.

More actions