Currently, when a node has a configuration error (e.g., an invalid Actor ID or a missing required field), the user gets cryptic “Bad Request” errors or hidden “Workflow issues” alerts. This creates a massive barrier for new users.
Suggested Solution:
Implement real-time field validation similar to smartphone keyboard corrections:
- Visual Cues: Highlight the specific field causing the error in red inside the node configuration.
- Smart Suggestions: If an Actor ID is incorrect, provide a hint or a search/lookup directly in the field.
- Proactive Linter: Check for common syntax errors (like missing slashes/tildes or incorrect JSON keys) before execution.