n8n - 💡(How to fix) Fix Bug: Bitbucket Trigger credential validation fails with Atlassian scoped API tokens

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

  • error: all
RAW_BUFFERClick to expand / collapse

Bug Description

The Bitbucket Trigger credential validation in n8n fails when using the new Atlassian scoped API tokens for Bitbucket Cloud.

The same token works successfully in Postman and direct Bitbucket API calls, but n8n shows:

Authorization failed - please check your credentials

or:

Your credentials lack one or more required privilege scopes

even when all required Bitbucket scopes are enabled.

To Reproduce Open Atlassian API token management Create a scoped API token for Bitbucket Cloud Enable scopes: read:user:bitbucket read:workspace:bitbucket read:repository:bitbucket read:webhook:bitbucket write:webhook:bitbucket delete:webhook:bitbucket Open n8n → Credentials → Bitbucket API Enter: Email = Atlassian email or Bitbucket username Access Token = newly generated scoped token Click Save Expected behavior

n8n should validate the credential successfully and allow Bitbucket Trigger usage with Atlassian scoped API tokens.

Actual behavior

Credential validation fails with:

Authorization failed - please check your credentials

or:

Your credentials lack one or more required privilege scopes

even though:

the token is valid the token works in Postman Bitbucket API endpoints respond correctly webhook scopes are included

Verification

The same token works successfully using curl:

curl -u "[email protected]:API_TOKEN"
https://api.bitbucket.org/2.0/user

Response returns valid user JSON.

Only n8n credential validation fails.

<img width="733" height="439" alt="Image" src="https://github.com/user-attachments/assets/6f9682ce-244e-45ac-af77-582ccd00e190" />

To Reproduce

To Reproduce Open Atlassian API token management Create a scoped API token for Bitbucket Cloud Enable scopes: read:user:bitbucket read:workspace:bitbucket read:repository:bitbucket read:webhook:bitbucket write:webhook:bitbucket delete:webhook:bitbucket Open n8n → Credentials → Bitbucket API Enter: Email = Atlassian email or Bitbucket username Access Token = newly generated scoped token Click Save

Expected behavior

Expected behavior

n8n should validate the credential successfully and allow Bitbucket Trigger usage with Atlassian scoped API tokens.

Debug Info

Debug info

core

  • n8nVersion: 2.18.5
  • platform: docker (cloud)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: 5
  • license: enterprise (sandbox)
  • consumerId: 00000000-0000-0000-0000-000000000000

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 168 hours
  • maxCount: 2500 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/147.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-05-08T07:21:02.186Z

Operating System

Windows

n8n Version

cloud

Node.js Version

cloud

Database

SQLite (default)

Execution mode

main (default)

Hosting

n8n cloud

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Expected behavior

n8n should validate the credential successfully and allow Bitbucket Trigger usage with Atlassian scoped API tokens.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

n8n - 💡(How to fix) Fix Bug: Bitbucket Trigger credential validation fails with Atlassian scoped API tokens