Receive signal: <SignalName>
Description
Trigger node that starts the pipeline each time the matching signal is emitted. Each signal parameter appears as a typed output pin carrying the payload sent by the emitter. The pipeline subscribes automatically when saved and runs once per Send Signal invocation.
When to use
Use Receive signal as the entry point for any pipeline that should react to an event emitted by another pipeline. The pipeline subscribes to the named signal automatically when saved; no manual wiring between pipelines is needed. Every call to the matching Send signal node enqueues one execution intent for each subscriber, so the pipeline runs once per emission.
The output pins are determined by the signal’s parameter list. Each named parameter appears as a labelled output pin, typed to the Model the parameter references. Wire those pins into downstream nodes to process the payload data.
Execution is asynchronous: the emitting pipeline does not wait. Any JVM in the cluster may claim and run the intent via SKIP LOCKED, so load is distributed statistically across all running instances.
Pins
Execution pins
| Pin | Direction |
|---|---|
| Out | Output |
Example
A pipeline subscribes to OrderPlaced via Receive signal: OrderPlaced. The
signal carries a single parameter order (typed to the Order model). The pipeline
wires the order output pin through a series of HTTP request nodes to update a
warehouse management system and send a fulfilment notification — all without the
order-processing pipeline having to know about warehouse integration.