Node settingsCopy Anchor Link

Select a node in Actionflow Studio to open its inspector. The inspector edits the node's saved configuration. It does not run that node in isolation and it does not prove that a provider call will succeed.

What the inspector editsCopy Anchor Link

The inspector does not turn the graph into a typed compiler. Handle names and runtime values are not a promise of static type compatibility. A node function still validates or fails on the value it receives.

Required input resolutionCopy Anchor Link

At runtime, a required input can be supplied by one of these paths:

1. A non-empty value saved in the node's inputData.inputs.
2. A connected data edge whose targetHandle matches the required input name.
3. A run input keyed as {nodeId}_{inputName} on the ingress surface that supports it. This is a runtime execution value; it is not a universal way to satisfy validateFlow.

A default execution edge to node-target only orders the target node. It does not fill a required named input. This distinction is enforced by validateRegularNodes and validateAiNodes for reachable nodes.

The Flow inputs extractor reads required definitions for reachable nodes and uses the current node catalog definitions where available. An Actionflow Studio run form can therefore expose fields that are empty in the saved graph. The exact behavior depends on the ingress path: API and webhook validation currently examines the saved graph before the caller's inputs are merged into the execution copy. If a required field is blank in the saved graph, do not assume a run input will bypass validation; save a value, connect the required handle, or fix the graph for that ingress.

Mappings and missing pathsCopy Anchor Link

Use a saved placeholder such as:

{{nodeId.outputPath}}

A reference can resolve only when the referenced node is executable/reachable and the output path exists. A missing node, missing path, circular reference, or unreachable reference becomes an empty string in an embedded text mapping or an undefined value in an exact mapping. Resolution can also call executeNode for a reachable referenced node and run downstream work early, so a placeholder is not a side-effect-free lookup. Add an explicit execution edge when ordering matters. The downstream node may handle that value, ignore it, or fail. Inspect the actual resolved input and output rather than treating the placeholder text as proof of a value.

Loop mappingsCopy Anchor Link

Loop can use manual items or inherit its items from another node's output. Manual mode accepts an array or a JSON array string. In inherited mode, the exact reference must resolve to an actual array; a single object or a JSON string containing an array is not iterated. The output mode also changes the per-iteration placeholder root: outputAsObject: true (the seeded default) uses {{loopNodeId.iteration}} for the current item and metadata, while outputAsObject: false uses {{loopNodeId.item}} for the current item. {{loopNodeId.result}} and nested result.* paths refer to the aggregate result regardless of output mode.

Credentials and modelsCopy Anchor Link

Flow validation checks reachable nodes, not disconnected nodes. For a reachable node it can report:

• a missing or incorrectly selected organization connection;
• a disabled node category or integration;
• a missing AI platform model;
• a missing BYOK service/model or organization credential;
• missing required inputs;
• invalid Loop configuration.

Flow Requirements is a focused editor view for missing connections. It does not test a provider, validate OAuth scopes, or guarantee that a credential will work at runtime.

Files and outputCopy Anchor Link

A file selected in an Actionflow Studio node form is uploaded before the node value is saved; the graph stores a durable file reference rather than a browser File object. The upload is an organization uploaded file, not automatically a generated Flow artifact. See Artifacts for the four separate file surfaces and the current plan-limit limitation.

RelatedCopy Anchor Link

• Actionflow Studio
• Execution model
• ActionFlow requirements
• Node requirements
• Node handles
• Credential management
• Troubleshooting