Endpoint → TInput
Admits data from an endpoint into a service pipeline.
When to use
Use Input at every external entry point. An endpoint can be used by at most one Input per service.
Behavior
- Deserializes the endpoint payload into valueType.
- May expose an Error consumer for transport or parsing failures.
- Can reference a result stream for request/response transports.
General properties
Identity, ownership and operator-specific mode.
typeTransformationTypeOperator kind. It controls available properties, valid sources and generated interfaces.
RequiredAllowed:Input, Map, Filter, Join, MultiJoin, Process, FlatMap, FlatMapIterable, KeyBy, Merge, Split, Case, Sink, CycleLink, Error, Delay, WhennamestringHuman-readable stream name shown in the designer and used to derive default generated symbols.
RequiredendpointEndpointExternal entry or exit point used by Input or Sink.
RequiredserviceServiceService that owns the stream. Connected streams must belong to the same service.
RequiredConnections properties
Upstream graph references accepted by this operator.
resultStreamStreamOptional result stream for a request/response endpoint. Commonly points to the result-producing Sink path.
Data Types properties
Message contracts visible at this node.
valueTypeTypeOutput or response message contract. The exact meaning is operator-specific.
RequiredDefault:UnknownTypeExecution properties
Pipeline placement and runtime policy.
pipelinestringVisual and configuration grouping inside the owning service.
Position properties
Designer-only canvas coordinates.
xPosnumberHorizontal designer coordinate. It has no runtime effect.
RequiredyPosnumberVertical designer coordinate. It has no runtime effect.
RequiredConfiguration example
type: Input
endpoint: ordersHttp
valueType: OrderRequest
pipeline: ingress