Input Field

the input field node connects your workflow to a specific form input, lets you read or set its value, and provides helper methods to work with that value safely throughout the flow overview the input field node represents a single form control (text, email, number, password, checkbox, etc ) on your page it captures the user’s input, exposes that value to other nodes, and lets you programmatically get, set, and validate the field using built‑in methods core identity these properties uniquely identify the input in your workflow and ui input id system‑generated identifier for this specific input instance (for example, id 176534108019832753) used in advanced code snippets (e g , input id 176534108019832753 get() or flowresults inputs\['id 176534108019832753'] set('value')) to access the field directly name human‑readable label for the input (for example, department) often used as the key when sending data to apis or when referring to this input in docs and ui type the input control type, inferred automatically from the dragged element (text, email, number, etc ) determines how the ui renders and how validation rules can be applied variable optional workflow variable name (e g , department) that can be used with helpers like getvalue('department') in other nodes data source configuration this section decides where the input’s value comes from when the workflow runs use default value (no source) the field value comes directly from the user’s manual input in the form ideal for standard, user‑driven inputs such as email, name, or comments from node id pre fills or drives the input from another node’s output under the hood, this is equivalent to using helpers like dataflow\ getbynodeid('\<node id>') to fetch a value useful for read‑only fields or when you want to show previously fetched data inside an input from template variable computes the input value from a template expression or workflow variable, such as {{user email}} or {{dataflow\ current() email}} lets you bind the field to higher‑level workflow variables like currentuser, calculatedvalue, or selecteditem using getvalue('currentuser') and similar helpers available variables helper the available variables helper panel shows all variables and helper functions you can use when templating the input’s value or when writing expressions in downstream nodes previous node helpers dataflow\ current() – get the most recent node result dataflow\ previous() – get the result from the previous node dataflow\ get('apiresponse') – shortcut to fetch named results like api responses, form submission data, or ai responses workflow variables items like userinput, formdata, apiresponse, or calculatedvalue, accessible via getvalue('\<variablename>') useful to keep form values and computed data in a single, reusable place available inputs individual input variables such as username, email, password, firstname, lastname, phonenumber, etc , accessible via getvalue('\<inputname>') makes it easy to reuse input values in validation logic, api bodies, or conditional nodes pro tips use dataflow\ current() for the latest result access variables with getvalue('variablename') check available names with dataflow\ getavailablenames() to see what you can safely reference in templates advanced methods & documentation the advanced methods section exposes a small api to interact with the input programmatically available input methods get() retrieves the current value of the input const value = input get(); example typically used in custom logic or when you need to inspect the field value before passing it downstream set(value) updates the input value and triggers change events input set("new value"); example ideal for pre filling fields or dynamically changing values based on other nodes onchange(callback) registers a real time change listener on the input input onchange((val) => console log(val)); example useful for interactive flows where later nodes should react as the user types clear() clears the input field and resets it to an empty state input clear(); example commonly used after a successful form submission focus() sets focus on the input element in the ui input focus(); example helpful for guiding the user to the next required field advanced usage by id input id 176534108019832753 get(); direct access using the generated id flowresults inputs\['id 176534108019832753'] set('value'); access via flowresults these patterns are useful when building complex flows where you need explicit control over specific inputs typical workflow usage add the input node drag an input field node connected to a form input (e g , email, department, username) confirm the name, type, and variable so you can reference them later choose the value source leave as default for user entered values or select from node id to bind it to another node’s output, or from template variable to compute the value from workflow variables or templates connect downstream consumers attach condition/if nodes, api nodes, or ai nodes that will use this value in those nodes, access the value via {{dataflow\ getbynodeid("\<input id>")}}, dataflow\ current(), or getvalue('\<variablename>') as needed example flow email capture and submission input field (email) → condition node (validate email format) → api post node the input node supplies the user’s email; the condition node checks the pattern using input get() or getvalue('email'); the api node uses this email in its request body multi input form submission several input nodes (firstname, lastname, department, phonenumber) → condition node (required fields) → api post → paragraph or heading to show a success message all input values are aggregated via workflow variables like formdata or individual getvalue('\<inputname>') helpers data driven personalization api node fetches user profile → input nodes prefilled with from template variable (e g , {{user email}}) → heading/paragraph nodes display personalized content and ai/email nodes use the captured values for notifications why the input field node is helpful removes the need for manual dom wiring or custom event listeners; everything is managed via a consistent node interface provides standardized get / set / clear / focus / validate patterns that are easy to reuse across flows and easy to reason about the available variables helper and autocomplete make it safer to work with workflow data, reducing naming mistakes and making complex forms easier to maintain