Credential type selection fixed in modal
Nodes with multiple credential types now correctly display the right fields when creating new credentials from any dropdown.
When a node supports multiple credential types, the "Create New Credential" modal now shows the correct fields for the type that was selected. Previously, clicking "Create New Credential" from the Beta API dropdown would incorrectly display Alpha API's fields—the modal always defaulted to the first credential type regardless of which one was requested. This fix ensures the requested credential type is honored, so users see exactly the fields they expect when creating credentials from any dropdown. The change is in the credential editing component used when configuring n8n nodes.
View Original GitHub Description
Summary
When a node has multiple credential types (e.g. Alpha API and Beta API), clicking “Create New Credential” from the Beta dropdown would open the modal showing Alpha’s fields instead.
Root cause: In CredentialEdit.vue, the selectedCredentialType computed ignored the activeId prop (which carries the requested credential type) when requiredCredentials was true. It always fell back to the first credential type from the node definition.
Fix: Added a check for props.activeId before the fallback, so the modal honors whichever credential type was actually requested.
Test: Verifies that when activeId is set to the second credential type, getNewCredentialName is called with that type — not the first one.
https://github.com/user-attachments/assets/37859ae6-c9e8-4dd6-9b81-4bed71d9a924
Related Linear tickets, Github issues, and Community forum posts
https://linear.app/n8n/issue/IAM-413/community-issue-nodecredentials-have-internally-only-one
Review / Merge checklist
- PR title and summary are descriptive. (conventions) <!-- **Remember, the title automatically goes into the changelog. Use `(no-changelog)` otherwise.** -->
- Docs updated or follow-up ticket created.
- Tests included. <!-- A bug is not considered fixed, unless a test is added to prevent it from happening again. A feature is not complete without tests. -->
- PR Labeled with
Backport to Beta,Backport to Stable, orBackport to v1(if the PR is an urgent fix that needs to be backported)