FlowDrop Workflow Specification 1.0-draft

External invocation builds flat initial data

The payload has to arrive where the trigger's advertised output schema says it is. Keying it by node id put it somewhere only an expression naming that node could reach.

The rule

Normative: this is the rule
  1. The initial data for an externally invoked run is flat: the extracted trigger data at the top level, plus the identifiers of the trigger configuration and the trigger node, the same shape every other trigger kind builds.
  2. Since a trigger emits its whole initial data as the node's data output, the caller's payload is reachable at data.payload, which is what the trigger's declared output schema advertises.
  3. The initial data must not be keyed by node id.
Rule identifiers are permanent and are never renumbered. Each implementation publishes its own standing against these rules; this specification does not.spec 1.0-draft · OCX-1 · changed in spec 1.0