fix(entry-point): resolve dynamic ports correctly for Entry Point nodes

[betterclever]

Summary

Fixes ENG-114: Entry node issue

This PR fixes multiple issues with the Entry Point node's dynamic ports (runtime inputs):

Issues Fixed

Issue 1: Edge connections from wrong output port

When dragging from Input 2 on an Entry Point node, it would incorrectly connect from Input 1.

Root Cause: ReactFlow caches handle positions and wasn't being notified when dynamic ports changed.

Fix: Added `useEffect` in `WorkflowNode.tsx` that calls `updateNodeInternals()` whenever `effectiveOutputs` or `componentInputs` change, forcing ReactFlow to recalculate handle positions.

Issue 2: Entry Point shows 'Triggered' instead of actual inputs

When loading a workflow, the Entry Point would show the fallback 'Triggered' output instead of the configured runtime inputs (Input 1, Input 2, etc.). Opening the config panel would magically fix it.

Root Cause: Two bugs in `workflows.service.ts`:

1. The `parse()` method was passing the wrong object to `resolvePorts`:

   • Before: `nodeData.config` → `{params: {...}, inputOverrides: {...}}`
   • After: `nodeData.config.params` → `{runtimeInputs: [...]}`

2. Dynamic ports were only resolved when saving workflows, not when fetching.

Fix:

• Fixed param extraction to use `nodeData.config.params`
• Added `resolveGraphPorts()` method that resolves dynamic ports when fetching workflows
• `buildWorkflowResponse()` now applies port resolution before returning to frontend

Technical Details

The dynamic ports system now correctly:

• ✅ Resolves ports when creating/updating workflows (via `parse`)
• ✅ Resolves ports when fetching workflows (via `resolveGraphPorts`)
• ✅ Updates ReactFlow handle positions when ports change (via `updateNodeInternals`)
• ✅ Properly types the graph using `WorkflowGraph` instead of `any`

Files Changed

• `frontend/src/components/workflow/WorkflowNode.tsx` - Added `updateNodeInternals` effect
• `backend/src/workflows/workflows.service.ts` - Fixed param extraction + added `resolveGraphPorts`

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 122b2228ea

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Include legacy param locations in port resolution

The new resolveGraphPorts only reads nodeData.config?.params, so workflows saved before the config.params migration (where params live under node.data.parameters or directly on node.data.config) will resolve ports with {} and still show the fallback outputs (e.g., Entry Point stays on “Triggered”) when fetched. You already handle legacy locations in parse(), but fetch-time resolution doesn’t, so older workflows won’t get the fix until they’re re-saved. Consider using the same fallback chain as parse() to avoid leaving legacy graphs unresolved.

Useful? React with 👍 / 👎.