SegmindSegmind / Docs
Node Types

Input Nodes

Feed data into PixelFlow workflows: text, number, dropdown, multi-select, JSON, and boolean inputs, plus file uploads with an inline inpainting mask tool.

Input nodes supply the values your workflow runs on. They come in two flavors — text and file — each with several modes.

Screenshot coming soon

Input node modes

/images/pixelflow/nodes/input-types.webp

Text inputs

ModeUse it for
Plain textPrompts and free-form strings
NumberNumeric parameters, with optional min/max/step
DropdownOne choice from a fixed list you define
Multi-selectSeveral choices from a fixed list
JSONStructured payloads passed through as-is
BooleanOn/off switches

Dropdown and multi-select options are defined on the node, which keeps published APIs constrained to valid values.

File inputs

File inputs accept uploads by drag-and-drop or file picker:

ModeAccepts
Any fileAnything a downstream model can consume — images, video, audio, PDFs, and more
Image / Video / AudioHints the expected media type
InpaintingAn image plus a mask you paint directly in the node

Uploaded files are stored in your asset gallery and passed downstream as URLs.

The inpainting mask tool

In Inpainting mode, the node opens a masking canvas: brush over the regions you want the model to regenerate, and the node outputs the image and the mask on separate ports — wire each to the matching parameters of an inpainting model.

Video coming soon

Painting an inpainting mask inside the input node

https://segmind-resources.s3.amazonaws.com/docs/pixelflow/nodes/inpaint-mask-tool.mp4

Key names: exposing inputs as API parameters

Give an input node a key name to make it a named parameter of your published API — the key name becomes the JSON field callers send. Inputs without a key name keep their canvas value when the workflow runs as an API.

Prefer input nodes over hard-coding values in model forms for anything you'll want to change per run — they're what become your API's parameters when you publish.

On this page