NodeFox

Lesson 17 · Intermediate

Run a network as an App or Automation

Create an input contract and reuse it for individual or batch runs.

1:45 video guide + written guide

Source-based instructional visualization · synthetic examples · AI narration. This explains configuration and behavior; it is not a recording of a verified live run.

Jump to a chapter

Before you start

A signed-in NodeFox workspace. Use synthetic data and prepare outputs before enabling external writes.

  1. 01Define the App fields

    Create an App pointing to the learning network. Add contract text and minimum notice days. Use stable variable names such as contract_text and minimum_notice_days. Set clear labels and appropriate field types.

  2. 02Read the same variables

    In the target graph, configure Global Get nodes with those exact names. Normalize the number before comparing it. The form and graph must agree on names and types; matching visible labels is not enough.

  3. 03Test one submission

    Submit the sample Clause 8.2 text and 60-day policy. Inspect the resulting data and decision. This example must request review because 30 is less than 60. Keep the output local until the mapping is verified.

  4. 04Scale to a small batch

    Create an Automation using a bounded list or CSV column and any fixed shared inputs. Preview the items before running. Inspect completed, waiting and failed runs separately rather than treating the batch as one undifferentiated success.

Example configuration or input

contract_text = "Clause 8.2: renewal notice is 30 days."
minimum_notice_days = 60

Expected result

One review request for the sample, with the source clause and policy value preserved.

If the result is wrong

An empty Global Get often indicates a variable-name mismatch. A waiting batch item needs its own decision or missing prerequisite resolved.