ComfyUI Node: Google AI - Workflow Analyzer

Google AI - Workflow Analyzer:

The GoogleAI_WorkflowAnalyzer is a powerful tool designed to analyze workflow data, specifically in JSON format, to identify and categorize different node types within a given workflow. This node is particularly beneficial for users who need to understand the structure and components of complex workflows, as it provides a detailed analysis of the node types present. By leveraging Google's AI capabilities, the Workflow Analyzer can process and interpret the workflow data, offering insights that can help streamline workflow management and optimization. Its primary goal is to simplify the understanding of workflow structures, making it easier for users to identify key components and potential areas for improvement.

Google AI - Workflow Analyzer Input Parameters:

workflow_json

The workflow_json parameter is a crucial input that accepts either a JSON string representing the workflow or a file path to a .json file containing the workflow data. This parameter is essential as it provides the raw data that the node will analyze. The JSON should accurately represent the workflow structure, including nodes and their types. The parameter supports multiline input, allowing for complex JSON structures, and defaults to an empty string if not provided. It is important to ensure that the JSON is valid and correctly formatted to avoid errors during analysis.

api_key

The api_key is an optional parameter that allows you to provide an API key for authentication purposes. This key is used to access Google's AI services, which are necessary for the node to perform its analysis. While the parameter defaults to an empty string, providing a valid API key ensures that the node can communicate with the AI services effectively, enhancing the accuracy and reliability of the analysis.

model

The model parameter specifies the AI model to be used for the analysis. It defaults to "gemini-3.1-pro-preview" and is part of the DIAG_MODELS options. This parameter influences the depth and type of analysis performed by the node, as different models may have varying capabilities and focus areas. Selecting the appropriate model can optimize the analysis for specific types of workflows or desired outcomes.

Google AI - Workflow Analyzer Output Parameters:

analysis_report

The analysis_report is the primary output of the GoogleAI_WorkflowAnalyzer. It is a string that contains a detailed report of the workflow analysis, including the types of nodes identified and their respective counts. This report provides valuable insights into the workflow's structure, helping users understand the composition and complexity of their workflows. The analysis report is essential for identifying potential improvements or optimizations in the workflow design.

Google AI - Workflow Analyzer Usage Tips:

• Ensure that the workflow_json is correctly formatted and represents the workflow accurately to avoid errors during analysis.
• Providing a valid api_key can enhance the node's performance by ensuring seamless access to Google's AI services.
• Choose the appropriate model based on the specific requirements of your workflow analysis to achieve the best results.

Google AI - Workflow Analyzer Common Errors and Solutions:

❌ No es un JSON válido ni una ruta existente.

• Explanation: This error occurs when the provided workflow_json is neither a valid JSON string nor a valid file path.
• Solution: Verify that the input is a correctly formatted JSON string or a valid path to a .json file.

⚠️ No se encontraron 'class_type' en el JSON.

• Explanation: This warning indicates that the JSON does not contain any nodes with a class_type attribute, which is necessary for analysis.
• Solution: Ensure that the JSON includes nodes with the class_type attribute to enable proper analysis.

❌ Error: <error_message>

• Explanation: A generic error message indicating an unexpected issue during the analysis process.
• Solution: Check the input parameters for correctness and ensure that the API key and model are valid. If the issue persists, consult the logs for more detailed error information.