Per-pair page

Connect Bitbucket to Slack in two minutes.

Real-time triggers from Bitbucket, ready-made actions in Slack. Filter, transform, and route without writing a line of code.

Connect Bitbucket and Slack See reverse direction

Trigger app

Bitbucket as the trigger

Workflows fire when something happens in Bitbucket.

Action app

Slack as the action

Workflows do something in Slack, instantly.

See all 45 actions →

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

Bitbucket → Slack

When something happens in Bitbucket, do it in Slack.

4 Bitbucket triggers wired to 45 Slack actions. Most-used pairing: Issue Created → Raw API Request.

Slack → Bitbucket

Or fire it the other way around.

13 Slack triggers wired to 10 Bitbucket actions downstream.

See Slack → Bitbucket →

Popular pairings

Common Bitbucket → Slack workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 180 combinations

When issue created in Bitbucket, raw api request in Slack.

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.

When issue created in Bitbucket, add reaction in Slack.

When issue created in Bitbucket, archive channel in Slack.

When issue created in Bitbucket, cancel scheduled message in Slack.

When pull request created in Bitbucket, raw api request in Slack.

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.

When pull request created in Bitbucket, add reaction in Slack.

When pull request created in Bitbucket, archive channel in Slack.

When pull request created in Bitbucket, cancel scheduled message in Slack.

When pull request merged in Bitbucket, raw api request in Slack.

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.

How it works

Connect Bitbucket and Slack in five steps.

No code, no glue, no half-day setup. Each step is one click.

1
Connect
Authorize Bitbucket and Slack
Open Tiny Command, authorize Bitbucket and Slack once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Bitbucket trigger
Drop the Bitbucket → Issue Created trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/bitbucket.trigger-issue-created
3
Transform
Add a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
4
Action
Add the Slack action
Drop the Slack → Raw API Request action below it. Map fields from the Bitbucket payload into the Slack inputs.
slack.api-request
5
Publish
Publish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Bitbucket + Slack.

How long does it take to connect Bitbucket and Slack on Tiny Command?

Under two minutes. Authorize Bitbucket and Slack once each, drop the Bitbucket trigger and Slack action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.

Is the Bitbucket ↔ Slack integration real-time?

Yes. Both Bitbucket and Slack expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.

Can I filter or transform data between Bitbucket and Slack?

Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Slack.

What Bitbucket events can trigger a Slack workflow?

Any of the 4 Bitbucket triggers, including "Issue Created". Each fires in real time when the matching event happens in Bitbucket.

Do I need a paid plan to use Bitbucket with Slack?

No. There's a free tier that covers most Bitbucket+Slack use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.

What if I want Slack → Bitbucket instead?

Build it the same way, in reverse. There's a dedicated /integrations/slack/with/bitbucket page with the reverse-direction triggers and actions.

Other apps that pair well with Bitbucket.

Bitbucket + Gmail

Bitbucket + Google Sheets

Spreadsheets & Databases