Dependency badge tooltips now explain clickability
The resource dependency badge in the workflow editor now explicitly tells users the badge is interactive, with refined sizing and colors that align it with other related badges.
The resource dependency badge in n8n's workflow editor looked like a static indicator, but it was actually a clickable element that opened a dropdown showing resource dependencies. The old tooltips simply said "1 dependency" or "3 dependencies" — ambiguous language that left users guessing about what the badge did.
The tooltips have been rewritten to be direct: "Click to view resources referenced by this workflow." Users no longer need to guess whether the badge is interactive. The badge itself was also resized and restyled so it visually aligns with other related badges in the interface, creating a more cohesive look across the editor.
These changes live in the frontend editor UI, specifically refining the DependencyPill component that appears when workflows reference credentials, data tables, or other workflows.
View Original GitHub Description
Summary
Adjust size by a pixel to align with other badges. Update the tooltip to be explicit about the badges being clickable.
Update +n not accessible to you color to:
<img width="273" height="147" alt="image" src="https://github.com/user-attachments/assets/35d5d077-edce-4a47-8db2-5a99009edade" />
<img width="235" height="232" alt="image" src="https://github.com/user-attachments/assets/e17664d7-dfc0-4978-bd6e-91ab47ec0c1b" />
Related Linear tickets, Github issues, and Community forum posts
https://linear.app/n8n/issue/ADO-5042/feature-workflow-dependency-feedback
Review / Merge checklist
- I have seen this code, I have run this code, and I take responsibility for this code.
- 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)