How to navigate nodes in Graph view

How to Navigate Nodes in Graph View

Overview

The graph view is interactive. Every node in the graph is clickable and takes the user directly to the configuration area for that component. This makes the graph a fast path from a high-level view of the Digital Worker's structure to the precise settings for any individual part of it, without needing to navigate through separate menus.

Clicking a Node

Clicking a node in the graph opens the corresponding configuration area for that component. Depending on the node type, this may open a details panel within the graph view, display the proposed change with options to accept or discard it, or navigate to the full settings page for that component where manual edits can be made.

The behavior is consistent regardless of how the node reached its current state, whether it was added, updated, or flagged by MetaPrompter, or whether it is a stable component being inspected for reference.

What You Can Do from a Node

Once a node is open, the available actions depend on the component type. In general, users can review the current configuration of that component, inspect what MetaPrompter changed and what the previous value was, make further manual adjustments to the settings, and save or discard the changes for that component before returning to the graph.

For example, clicking a trigger node that MetaPrompter updated opens the trigger settings, where the new schedule or condition can be reviewed, adjusted if needed, and confirmed. Clicking a connector node opens the connector configuration, where integration details can be verified. Clicking an approval node shows the approval condition and the channel it routes to.

Navigating a Changed Configuration

After a MetaPrompter edit, the most efficient way to review changes is to use the graph as the primary navigation surface. Identify the nodes marked as added, updated, or flagged, click each one in turn to open its settings, review and adjust as needed, and return to the graph to continue. This creates a systematic path through every affected component without missing anything.

This approach is particularly important when a request has touched multiple components at once, which is common for edits that span instructions, tools, connectors, and triggers in a single prompt. The graph makes the full scope of the change visible and navigable from one place.