Move Webhook Input to Inputs Section

[HugoCatarin0]

Enhancement Proposal: Move Webhook Input to Inputs Section

Currently, webhook inputs reside in Langflow’s "Data" section, which feels misaligned with their role as entry points for workflows. Relocating them to the "Inputs" section would streamline the UI, better reflect their purpose, and improve the overall user experience.

Advantages for Langflow/DataStax:

Logical Consistency: Webhooks are triggers that kick off workflows, akin to other inputs like prompts or APIs. Grouping them with "Inputs" aligns with standard design patterns, enhancing Langflow’s intuitiveness as it integrates with IBM’s ecosystem (post-acquisition, Q2 2025).
UI Clarity: A cleaner separation of inputs (active triggers) from data (static resources) reduces cognitive load, making Langflow’s interface more approachable for enterprise users.
Scalability Prep: As Langflow grows, a well-organized input category supports future additions like real-time triggers, keeping the platform cohesive.
Benefits for the Langflow Community:

Workflow Intuition: Users expect inputs to be where workflows start. Placing webhooks in "Inputs" mirrors this mental model—e.g., a webhook triggering a pipeline feels more natural alongside prompt inputs than buried in "Data."
Faster Onboarding: New users won’t hunt for webhook setup under "Data," where it feels out of place, speeding up their ability to build and test workflows.
Confidence Boost: A UI that matches intent (inputs as starters, data as resources) reduces confusion, letting users focus on creating rather than deciphering.
This small shift could make Langflow’s workflow design more instinctive and user-friendly. What do you think—could moving webhook inputs to "Inputs" refine the experience?