feat(workflow): improve Add node discovery

[adityashirsatrao007]

Description

This PR improves the discoverability of the 'Add node' action in the workflow builder by making it always visible in the action menu.

Changes:

1. Pin the 'Add node' action - Changed \isPinned\ from \alse\ to \ rue\ for the \ADD_NODE\ action so it's always visible and easily accessible when viewing a workflow
2. Unpin 'Add to favorites' and 'Remove from favorites' - These actions are less frequently used in the workflow context, so they've been unpinned to make room for the more relevant 'Add node' CTA

Files Changed:

• \packages/twenty-front/src/modules/action-menu/actions/record-actions/constants/WorkflowActionsConfig.tsx\

Fixes #16538

---

Note

Pins ADD_NODE in the workflow action menu and unpins ADD_TO_FAVORITES/REMOVE_FROM_FAVORITES to prioritize workflow-related actions.

• Workflow action menu config (WorkflowActionsConfig.tsx):
  • Pinning: Set isPinned: true for WorkflowSingleRecordActionKeys.ADD_NODE.
  • Unpinning: Set isPinned: false for SingleRecordActionKeys.ADD_TO_FAVORITES and SingleRecordActionKeys.REMOVE_FROM_FAVORITES under propertiesToOverwrite.

^{Written by Cursor Bugbot for commit 67b65df. This will update automatically on new commits. Configure here.}

[greptile-apps]

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

[cubic-dev-ai]

No issues found across 1 file

[Copilot]

Pull request overview

This PR enhances the discoverability of the "Add node" action in workflow management by making it always visible in the action menu, while deprioritizing less frequently used favorite-related actions.

• Changed the ADD_NODE action to be pinned by default for better visibility
• Unpinned ADD_TO_FAVORITES and REMOVE_FROM_FAVORITES actions to make room for more relevant workflow actions

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[FelixMalfait]

Thank you!

[guillim]

IMO we should link to the previous node by default. otherwise we have an orphan node creation, and that is not what users expect

[FelixMalfait]

@guillim I think that goes again the goal of the change which was actually to make branching more discoverable
(@Bonapara fyi)

[FelixMalfait]

didn't realize I hadn't merged. I think we can merge like this for now but if you have better ideas to make branching more discoverable @guillim happy to chat on Discord, I'm also not 100% convinced it's very intuitive yet but still feel it's a step in the right direction!

[twenty-eng-sync]

Hey @FelixMalfait! After you've done the QA of your Pull Request, you can mark it as done here. Thank you!

[guillim]

@guillim I think that goes again the goal of the change which was actually to make branching more discoverable (@Bonapara fyi)

ok fine with me. I was not aware of that behaviour