API-Based Retrieval of Path Trace Results from Triggered Automation

NetBrain does not currently provide a way for an external application to trigger a path trace through the Triggered Automation Framework and receive the resulting path data, such as device names along the path, back through the same API interaction. Applications that need this information must rely on a separate path calculation API call, which can sometimes produce a different path result than the one generated by the triggered automation, creating inconsistency between the two data sources. This enhancement would introduce a way for a triggered automation execution to return path trace results, such as the ordered list of devices in the path, directly in the API response or through a related endpoint, without requiring a second, independent path calculation call. Customers integrating NetBrain with external applications would benefit from consistent, reliable path data sourced from a single automation execution, reducing the need to build and maintain a separate integration path and improving accuracy for downstream checks that depend on that data.