TriggerBitbucketReal-timeUpdated June 2026

When does Bitbucket fire on new issues?

Short answer: In TinyCommand, add the Bitbucket Issue Created trigger to a workflow and publish. It listens through a Bitbucket webhook and fires your workflow within seconds of the event, with no polling and no code. Add a filter if you only want some events to start a run.

Use this trigger All 4 Bitbucket triggers

Anatomy

What this trigger looks like in a workflow.

Drop it on the canvas. Configure a couple of fields. Publish.

In the builder

Trigger

Issue Created

When the matching event happens

new issue createdissue addedon issue createdwatch for issue createdwhen issue creatednew issuewhen an issue is created

What this trigger returns

for the curious

You don’t need to read this. TinyCommand 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.

{
  "id": 1,
  "state": "new",
  "title": "Bug report",
  "priority": "major",
  "reporter": "User"
}

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
id	number	1
state	string	"new"
title	string	"Bug report"
priority	string	"major"
reporter	string	"User"

Pairs with

Drop these actions after Issue Created.

Add Labels to Message

Gmail · Email

Add Reaction

Slack · Communication

Add Sheet Tab

Google Sheets · Spreadsheets & Databases

Create Company

HubSpot · CRM & Sales

FAQ

Questions about Issue Created.

How does the Issue Created trigger work in Bitbucket?

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.

Is the Issue Created trigger real-time?

Yes. Issue Created uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in Bitbucket.

What data does Issue Created 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 Issue Created 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 Issue Created?

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

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.

Trigger

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.

Trigger

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".