NODE REQUEST GUIDEUse this form to describe a node you want to create.Node Name:What should this node be called?Required Artifacts: optionalWhat input files, images, text, tables, folders, or prior node outputs does this node need?Transformation / Use: requiredWhat should the node do to the input, or what action should it perform?Connections: optionalDoes this node need an outside service, account, API, website, database, or app connection?Configurable Options: optionalWhat should the user be able to change each time they use this node?Output: optionalWhat should the node produce when it finishes?GUIDANCEDescribe the node as one useful workflow step.Small focused nodes are recommended, but not required. A node may perform multiple internal operations if that is useful. The runtime treats the node as one execution unit and records one primary outcome.Required Artifacts are what the node needs before it can run. Examples: image file, CSV, transcript, prior summary, folder of files, selected text.Transformation / Use is the actual job of the node. Examples: crop image, summarize transcript, post tweet, search mentions, convert CSV to JSON, generate invoice.Connections are external access paths the node needs. Examples: Twitter/X account, Google Drive, Shopify, email inbox, local model, website API.Configurable Options are user choices exposed in the UI. Examples: tone, max posts, date range, output format, target folder, include images, resize dimensions.Output is what comes out. Examples: text artifact, JSON artifact, image artifact, posted URL, report, table, status only.EXAMPLENode Name:Twitter Search Recent PostsRequired Artifacts:NoneTransformation / Use:Search recent Twitter/X posts matching a user-provided query and save the returned posts as a project artifact.Connections:Twitter/X connectionConfigurable Options:querymax resultslanguagedate range if supportedinclude media links yes/noOutput:JSON artifact containing normalized posts, author handles, timestamps, URLs, text, and media references.UNDERLYING RULEThe user defines what the node should do. The node owns the action and payload directive. The system only facilitates secure connection access. Credentials never enter the node definition, manifest, log, or artifact.