Called by pipeline
Description
Trigger node that starts the pipeline when another pipeline's Run pipeline node calls it. Each trigger parameter the pipeline declares appears as a typed output pin carrying the value the caller supplied. A pipeline can have at most one of these, because a call has to start in one unambiguous place.
When to use
Use Called by pipeline to turn a pipeline into something another pipeline can invoke by name. Placing the node is what makes the pipeline callable at all — without one, no Run pipeline node can target it.
Its output pins come from the pipeline’s own trigger-parameter declaration, edited on the Trigger parameters tab. Each declared parameter becomes a labelled output pin here and a matching input pin on every Run pipeline node pointing at this pipeline, so the two ends of the call stay in step.
Prefer this over Receive signal when exactly one pipeline should run. A signal is a broadcast: the sender names an event and every subscriber runs, which makes “run the Prod copy and not the Test copy” impossible to express. A call names one pipeline.
Every output pin can be null. An unwired argument pin on the caller sends an explicit null, a parameter added after a call was queued is absent from it, and a manual run through the Run button passes nothing at all.
Pins
Execution pins
| Pin | Direction |
|---|---|
| Out | Output |
Example
A shared Update products in Viskan pipeline starts with Called by pipeline and
declares one trigger parameter, products (an array of the Product model). Several
other pipelines — a nightly full sync, an ad-hoc price correction, a webhook handler —
each end with a Run pipeline node wired to that pipeline, passing whichever products
they gathered. The integration logic lives in one place, and each caller decides what to
send.