Bitbucket Cloud "PR merged" automation trigger never fires

Support Bug Reports
1

Cursor version: 3.22.7 (Universal)

Automation: N8N Deploy Watcher (Bitbucket)
Automation ID: 7649b6f3-b033-11f1-bf4b-42ffb4d10ea7
Trigger: Pull request merged in plooral/n8n (Bitbucket Cloud), by Anyone
Repository setting: Repository from Git Trigger
Status: Active, Run as: Me
Steps to reproduce

  1. Create an automation with the trigger “PR merged” on the Bitbucket Cloud
    repository plooral/n8n.
  2. Save it as Active.
  3. Open a pull request to master in plooral/n8n and merge it.
  4. Open Run History of the automation.
    Expected behavior
    A new run with the “PR merged” trigger appears for each merge into master.
    Actual behavior
    No run is created. Run History only contains the manual “Test run”
    (Sep 25, 15:44 UTC-3). No “PR merged” run has ever appeared.
    Merged pull requests that did not create a run (times in UTC-3):

  • PR #4, merge commit 21d11c7, Sep 25,

  • PR #6, merge commit 1092ae3, Sep 25,

  • PR #7, merge commit c1864a9, Sep 25,
    What works

  • Manual Test run succeeds and can read the repository and its pull requests.

  • Integrations: Bitbucket Cloud “Connected as ‘Stefany Borin’”,
    “Cursor app installed in ‘plooral’”.

  • Cursor Forge app is installed in the plooral workspace; no upgrade available.

  • A scheduled automation on the same repository runs normally.
    What we tried

  • Reconnected Bitbucket Cloud in Integrations.

  • Re-saved the automation without changes.

  • Merged a new pull request after re-saving; still no run.
    Possibly relevant

  • The Bitbucket repository was renamed from n8n-update to n8n.

  • A GitHub repository with the old name (plooral/n8n-update) is also connected
    and has its own active automations.
    Screenshots

  • Automation settings showing the “PR merged in n8n” trigger

  • Run History showing only the Test run

  • Integrations page showing Bitbucket Cloud connected
    Console errors
    None in Help > Toggle Developer Tools. The trigger fires server-side, so no
    IDE request is created when a pull request is merged.

    Captura de tela 25.09.2026 às 17.11.25 PM
    Captura de tela 25.09.2026 às 17.11.25 PM562×222 15.4 KB

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

6

Hey @Stefany_Borin, thanks for the detailed report.

I checked on our side and your setup is fine. The rename and the connected GitHub repo aren’t the cause. “PR merged” triggers for Bitbucket Cloud aren’t live for automations yet, even though the editor currently lets you save one and the Test run works. That’s why no run appears after a merge

Your scheduled automation keeps working as a fallback. I’ve flagged this to the team.