Developer ToolsReal-timeUpdated June 2026

Bitbucket integration

Repository and PR events from Bitbucket

Bitbucket is Atlassian's Git platform, often deployed alongside Jira for teams that wanted everything from one vendor. Four triggers cover the dev lifecycle: Push (commits to any branch), Pull Request Created, Pull Request Merged (the post-merge fan-out moment), and Issue Created. Ten actions handle the operational surface: Create Pull Request, Create Issue, Add PR Comment, Get Pull Request, Get Repository, List Branches, List Commits, List Pull Requests, plus the related read endpoints. Authorize with a Bitbucket App Password (per-user OAuth-style credential with explicit scopes) or via OAuth for org-wide setups. The integration works against Bitbucket Cloud out of the box; Bitbucket Data Center is supported via API token with the on-prem URL configured at connection setup. Common patterns: a Pull Request Merged on main triggers a Jira ticket transition (closes the linked story), pings the deploy channel in Slack, and runs a workflow that updates the release notes in Notion; or Issue Created syncs the bug into Linear's backlog with the original Bitbucket link preserved.

Connect Bitbucket See 4 triggers

No credit card required · Set up in under 2 minutes

4triggers

10actions

≈ 2 minto set up

Freetier · no card

Triggers

Workflows start when Bitbucket does.

4 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.

Real-time · webhook-driven

Trigger live

When issue created

Fires when a new issue is created in a Bitbucket repository. Payload includes the issue title, body, reporter, labels, and milestone if assigned. Useful for "auto-route issues to the right team channel" or "create matching Linear/Jira issue for cross-tracker sync" workflows.

See what it returns →

Trigger live

When pull request created

Fires when a pull request opens in a Bitbucket repository. Payload includes the source/destination branches, title, author, and reviewers. The base hook for "auto-assign reviewers", "post to Slack PR-review channel", "trigger CI on PR-open" workflows.

See what it returns →

Trigger live

When pull request merged

Fires when a PR merges to its destination branch. Useful for "auto-deploy main on merge", "transition the related Jira issue to Resolved", "send the PR contributor a thanks note" downstream automations.

See what it returns →

Trigger live

When push to branch

Fires when commits are pushed to any branch (or a specific branch if scoped). Payload includes the commits with messages and authors. Useful for "post commit message to engineering Slack" or "kick off custom CI for branches CI doesn't watch".

See what it returns →

Actions

Do anything Bitbucket can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs	Open action
Add PR Comment	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.	4 inputs	View
Create Issue	Files a new issue in a Bitbucket repository with title, content, kind (bug/enhancement/task), priority, assignee. For "Sentry error → file a Bitbucket issue" or "support ticket marked as bug → file repo issue" workflows.	6 inputs	View
Create Pull Request	Opens a new PR from source branch to destination branch with title, description, and reviewers. Useful for automation that auto-creates PRs from generated branches (e.g., dependabot-style auto-update workflows).	7 inputs	View
Get Pull Request	Returns the PR by ID with all metadata — branches, reviewers, status, merge conflicts, build status. The standard lookup for cross-tool sync workflows that need current PR state.	3 inputs	View
Get Repository	Returns the repository with name, description, language, visibility, fork info, recent activity. Useful for "show me all repos this team owns" inventory workflows or for validating a repo exists before downstream operations.	2 inputs	View
List Branches	Returns the repository's branches with last commit info. Useful for "find branches that haven't been touched in 90+ days for cleanup" maintenance workflows.	5 inputs	View
List Commits	Paginated commits with optional branch and author filters. For "weekly digest of commits by contributor" reporting workflows or for "what shipped in the last release" changelog-generation patterns.	4 inputs	View
List Pull Requests	Returns paginated PRs with filter by state (OPEN, MERGED, DECLINED, SUPERSEDED), source/destination branch, author. The base query for "PRs awaiting review" daily nudges or for code-review velocity reporting.	3 inputs	View
List Repositories	Returns paginated repos in the workspace with name, slug, language, visibility. Useful for inventorying team repos and for "iterate over every repo" cross-repo automation patterns.	3 inputs	View
Merge Pull Request	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.	5 inputs	View

Recipes

Pre-built Bitbucket workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Bitbucket → Slack alerts

AI-triage every Bitbucket event, ping the right channel only when it matters.

Bitbucket → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Bitbucket → Notion database

Turn Bitbucket into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Bitbucket once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Bitbucket field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Bitbucket integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Bitbucket to Tiny Command?

Open the Tiny Command workflow builder, drop in a Bitbucket node, and click Connect. Authorize Bitbucket once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Bitbucket triggers does Tiny Command support?

Tiny Command supports 4 real-time Bitbucket triggers, including "Issue Created", "Pull Request Created", "Pull Request Merged". Each trigger fires within seconds of the event happening in Bitbucket.

What Bitbucket actions can I run from a workflow?

10 Bitbucket actions are available out of the box, covering developer tools operations like "Add PR Comment". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Bitbucket integration real-time?

Yes. Issue Created and every other Bitbucket trigger uses webhooks or push subscriptions, so workflows fire within seconds of the event in Bitbucket rather than on a polling schedule.

Do I need to write code to use Bitbucket with Tiny Command?

No. Every Bitbucket trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Bitbucket API endpoint directly.

How much does the Bitbucket integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Bitbucket integration itself has no per-app surcharge.

Bitbucket integration

Workflows start when Bitbucket does.

Do anything Bitbucket can do, from a workflow.

Pre-built Bitbucket workflows.

Three things worth knowing.

Questions about the Bitbucket integration.

More developer tools apps people connect.

Do more with Bitbucket.