Bug Description
Describe the bug
When using the HTTP Request node with Predefined Credential Type (e.g. Brevo API,
WordPress API, WooCommerce API), the execution log shows a warning icon indicating
that credentials are not set — even though:
- The credentials are correctly configured and selected in the node
- The execution completes successfully (the authenticated action is performed)
- The same behavior is reproducible across multiple services
This creates a persistent false positive in the execution panel, making it
impossible to distinguish real credential errors from this spurious warning.
Actual behavior
A "credentials not set" warning is shown on every HTTP Request node using
Predefined Credential Type, regardless of whether credentials are actually set.
Environment
- n8n version: 2.13.2
- Running via: Docker (self-hosted)
- Database: (default)
- Affected services: Brevo, WordPress, WooCommerce (reproduced across multiple services)
Additional context
The issue appears to be a display/logging bug in how n8n records credential
references for the generic HTTP node — the execution result is correct,
but the credential reference is not being properly logged for this auth type.
Community thread with screenshots and discussion:
https://community.n8n.io/t/warning-about-credentials-not-set-using-http-node-although-the-node-is-working-and-credentials-are-set/278467
To Reproduce
- Create an HTTP Request node
- Set Authentication → Predefined Credential Type
- Select any credential (e.g. Brevo, WordPress, WooCommerce)
- Execute the workflow successfully
- Open the execution log → warning icon appears on the node with message
suggesting credentials are not set
Expected behavior
No warning should appear when credentials are correctly set and the execution
succeeds. The warning should only appear when credentials are genuinely missing
or invalid.
Debug Info
Debug info
core
- n8nVersion: 2.13.2
- platform: docker (self-hosted)
- nodeJsVersion: 24.13.1
- nodeEnv: production
- database: postgres
- executionMode: regular
- concurrency: -1
- license: enterprise (production)
- consumerId: 8c218067-ae71-43d0-b12a-13c5cda8bd76
storage
- success: all
- error: all
- progress: false
- manual: true
- binaryMode: filesystem
pruning
- enabled: true
- maxAge: 336 hours
- maxCount: 10000 executions
client
- userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/146.0.0.0 safari/537.36
- isTouchDevice: false
security
Generated at: 2026-03-24T17:07:03.482Z
Operating System
Ubuntu Linux 22.04
n8n Version
2.13.2
Node.js Version
24.13.1
Database
PostgreSQL
Execution mode
main (default)
Hosting
self hosted
Bug Description
Describe the bug
When using the HTTP Request node with Predefined Credential Type (e.g. Brevo API,
WordPress API, WooCommerce API), the execution log shows a warning icon indicating
that credentials are not set — even though:
This creates a persistent false positive in the execution panel, making it
impossible to distinguish real credential errors from this spurious warning.
Actual behavior
A "credentials not set" warning is shown on every HTTP Request node using
Predefined Credential Type, regardless of whether credentials are actually set.
Environment
Additional context
The issue appears to be a display/logging bug in how n8n records credential
references for the generic HTTP node — the execution result is correct,
but the credential reference is not being properly logged for this auth type.
Community thread with screenshots and discussion:
https://community.n8n.io/t/warning-about-credentials-not-set-using-http-node-although-the-node-is-working-and-credentials-are-set/278467
To Reproduce
suggesting credentials are not set
Expected behavior
No warning should appear when credentials are correctly set and the execution
succeeds. The warning should only appear when credentials are genuinely missing
or invalid.
Debug Info
Debug info
core
storage
pruning
client
security
Generated at: 2026-03-24T17:07:03.482Z
Operating System
Ubuntu Linux 22.04
n8n Version
2.13.2
Node.js Version
24.13.1
Database
PostgreSQL
Execution mode
main (default)
Hosting
self hosted