TriggerBitbucketReal-timeUpdated May 2026
When does Bitbucket fire on commits?
Short answer: Drop the "Bitbucket → Push to Branch" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Bitbucket, not on a polling schedule.
Anatomy
What this trigger looks like in a workflow.
Drop it on the canvas. Configure a couple of fields. Publish.
In the builder
Trigger
Push to Branch
When the matching event happens
watch for pushnew pushwhen pushon pushwhen code is pushed to a bitbucket repository
What this trigger returns
for the curiousYou don’t need to read this. Tiny Command auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.
{"author": "Developer","branch": "main","commits": 1,"repository": "team/repo"}
Output shape
Fields available to downstream nodes.
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| author | string | "Developer" |
| branch | string | "main" |
| commits | number | 1 |
| repository | string | "team/repo" |
Pairs with
Drop these actions after Push to Branch.
FAQ
Questions about Push to Branch.
How does the Push to Branch trigger work in Bitbucket?
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".
Is the Push to Branch trigger real-time?
Yes. Push to Branch uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in Bitbucket.
What data does Push to Branch return?
The full event payload from Bitbucket. The output shape table on this page lists every field, its type, and an example value so you can map fields into downstream nodes.
Can I filter Push to Branch so only some events start a workflow?
Yes. Add a Filter node right after the trigger and match on any field, whether that's subject, sender, status, or anything else in the payload. Workflows only continue when the filter passes.
Do I need Bitbucket admin permissions to use Push to Branch?
For most Bitbucket accounts a standard user can authorize the trigger. Some Bitbucket plans require an admin to enable third-party webhooks. Check Bitbucket's docs if the trigger fails to register.
More triggers
Other Bitbucket triggers.
Trigger
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.
TriggerPull 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.
TriggerPull 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.
Build a workflow on this trigger.
One trigger. 10+ downstream actions. Zero glue.
