Heading

heading element the heading element node renders a heading (h1–h6) on the page and keeps its text synchronized with your data flow it is designed for titles, subtitles, and section labels that may change based on upstream node outputs purpose display dynamic or static headings on the page (h1–h6) without writing custom front‑end code bind heading text to data from previous nodes (api responses, database queries, forms, etc ) map each logical heading node to a specific visual heading instance using a unique identifier key fields heading id system‑generated identifier that uniquely associates the node with a heading instance on the page (for example, nested 1761902229088 8522) used by the runtime to determine which specific heading element to update when the node executes text value logical text source for the heading; accepts both static and templated content supports template expressions such as {{dataflow\ current() title}}, order #{{orderid}}, or (item field) to pull values from upstream nodes content final rendered string shown in the ui, such as welcome to our website can be purely static or built from one or more template tokens, for example welcome, {{user name}} note optional, non executing field for internal comments such as implementation notes, usage hints, or todos does not affect runtime behavior and is visible only in the editor configuration workflow add a heading node drag the desired heading level (h1–h6) onto the canvas or onto an existing heading area in your page layout a heading id is automatically assigned to link this node to the corresponding visual heading element define text binding in text value , enter either a static label (for example, order details) or a template expression such as order #{{dataflow\ current() id}} or (item title) in content , specify the final phrase to render; this may mirror the text value or combine multiple tokens, e g , welcome to our website, {{user firstname}} connect upstream data link an upstream node whose output will be used in the heading (api node, query node, form node, etc ) use helpers such as {{dataflow\ getbynodeid("api 123") id}} within text value or content to inject data from a particular node usage examples order confirmation title api node fetches order details → heading h2 node with text value order #{{dataflow\ getbynodeid("orders api") id}} the heading renders as order #12345, automatically reflecting the fetched order id personalized welcome banner authentication node provides the current user → heading h1 node with content welcome to our website, {{user name}} each logged in user sees a personalized heading without additional ui logic context aware section heading filter node outputs the active category → heading h3 node with content top results for {{filters category}} when the user changes filters, the section title updates to match the current context