← Back

Full JSON for Task ID: 161

{
    "id": "161",
    "status": "failed",
    "input": [],
    "output": [],
    "error": {
        "name": "NodeOperationError",
        "node": {
            "id": "55df5ee1-4733-4447-913c-05cb9edb182e",
            "name": "AI Pricing",
            "type": "@n8n\/n8n-nodes-langchain.agent",
            "position": [
                -336,
                1088
            ],
            "parameters": {
                "text": "=# Processed Docs\n{{ $json.processed_doc }}\n\n# Additional Information\n{{ $json.additional_information }}",
                "notice": "",
                "options": {
                    "systemMessage": "=# Role\nYou are an expert data extraction specialist with deep expertise in document analysis, pricing structure interpretation, and JSON formatting. You excel at identifying and categorizing pricing-related information with precision and consistency.\n\n# Task\nExtract pricing information from provided documentation and output it in a specific JSON format that separates included and not included items.\n\n# Context\nUsers need to quickly understand what is and isn't included in pricing structures from various documents. This structured extraction enables clear comparison, analysis, and decision-making around pricing models. The JSON format ensures the data is machine-readable and easily integrated into other systems or workflows.\n\n# Instructions\nThe assistant should:\n\n1. **Analyze the provided documentation thoroughly** to identify all pricing-related information, specifically looking for items, features, services, or components that are explicitly mentioned as included or excluded from the pricing.\n\n2. **Extract included items** - any features, services, components, or benefits that are stated as part of the base price or included in the offering without additional cost.\n\n3. **Extract not included items** - any features, services, components, or benefits that are explicitly mentioned as excluded, requiring additional payment, or available as add-ons.\n\n4. **Output the information in the following exact JSON structure**:\n```json\n{\n  \"pricing_info\": {\n    \"included\": [],\n    \"not_included\": []\n  }\n}\n```\n\n5. **Populate the arrays** with clear, concise strings describing each item. Each item should be a separate element in the appropriate array.\n\n6. **Handle ambiguous cases** by only including items that are explicitly stated. If an item's inclusion status is unclear or not mentioned, omit it from both arrays rather than making assumptions.\n\n7. **Maintain consistency** in terminology and formatting across all extracted items, using the exact language from the source document where possible.\n\n8. **Return only valid JSON** with no additional commentary, explanations, or markdown formatting around the JSON output.\n\n\n**Apply Latvian language rules strictly**:\n   - Use \"numuri\" not \"istabas\" for rooms\n   - Use \"viesnīca tikai pieaugušajiem\" not \"pieaugušo viesnīca\" for adults-only hotels\n   - Use \"piekrastē\" not \"virs jūras\" or \"kalnā virs jūras\" for coastal locations\n   - Maintain correct Latvian grammar, gender agreement, and terminology throughout"
                },
                "promptType": "define",
                "needsFallback": false,
                "hasOutputParser": true,
                "aiAgentStarterCallout": "",
                "preBuiltAgentsCallout": ""
            },
            "typeVersion": 2.2
        },
        "tags": [],
        "level": "warning",
        "stack": "NodeOperationError: A Chat Model sub-node must be connected and enabled\n    at validateInputConfiguration (\/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1.30_08b575bec2313d5d8a4cc75358971443\/node_modules\/n8n-core\/src\/execution-engine\/node-execution-context\/utils\/get-input-connection-data.ts:219:11)\n    at ExecuteContext.getInputConnectionData (\/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1.30_08b575bec2313d5d8a4cc75358971443\/node_modules\/n8n-core\/src\/execution-engine\/node-execution-context\/utils\/get-input-connection-data.ts:259:2)\n    at ExecuteContext.getInputConnectionData (\/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1.30_08b575bec2313d5d8a4cc75358971443\/node_modules\/n8n-core\/src\/execution-engine\/node-execution-context\/execute-context.ts:180:39)\n    at getChatModel (\/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/@n8n+n8n-nodes-langchain@file+packages+@n8n+nodes-langchain_fc553bfe732254ec5207074cf9e2ceb7\/node_modules\/@n8n\/n8n-nodes-langchain\/nodes\/agents\/Agent\/agents\/ToolsAgent\/common.ts:281:36)\n    at ExecuteContext.toolsAgentExecute (\/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/@n8n+n8n-nodes-langchain@file+packages+@n8n+nodes-langchain_fc553bfe732254ec5207074cf9e2ceb7\/node_modules\/@n8n\/n8n-nodes-langchain\/nodes\/agents\/Agent\/agents\/ToolsAgent\/V2\/execute.ts:195:22)\n    at processTicksAndRejections (node:internal\/process\/task_queues:105:5)\n    at ExecuteContext.execute (\/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/@n8n+n8n-nodes-langchain@file+packages+@n8n+nodes-langchain_fc553bfe732254ec5207074cf9e2ceb7\/node_modules\/@n8n\/n8n-nodes-langchain\/nodes\/agents\/Agent\/V2\/AgentV2.node.ts:131:10)\n    at WorkflowExecute.executeNode (\/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1.30_08b575bec2313d5d8a4cc75358971443\/node_modules\/n8n-core\/src\/execution-engine\/workflow-execute.ts:1265:8)\n    at WorkflowExecute.runNode (\/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1.30_08b575bec2313d5d8a4cc75358971443\/node_modules\/n8n-core\/src\/execution-engine\/workflow-execute.ts:1446:11)\n    at \/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1.30_08b575bec2313d5d8a4cc75358971443\/node_modules\/n8n-core\/src\/execution-engine\/workflow-execute.ts:1847:27",
        "context": [],
        "message": "A Chat Model sub-node must be connected and enabled",
        "messages": [],
        "timestamp": 1764692037530,
        "workflowId": "gJ6Pjcm2EmKJTNZZ",
        "executionId": "8135",
        "errorResponse": {
            "name": "NodeOperationError",
            "node": {
                "id": "55df5ee1-4733-4447-913c-05cb9edb182e",
                "name": "AI Pricing",
                "type": "@n8n\/n8n-nodes-langchain.agent",
                "position": [
                    -336,
                    1088
                ],
                "parameters": {
                    "text": "=# Processed Docs\n{{ $json.processed_doc }}\n\n# Additional Information\n{{ $json.additional_information }}",
                    "notice": "",
                    "options": {
                        "systemMessage": "=# Role\nYou are an expert data extraction specialist with deep expertise in document analysis, pricing structure interpretation, and JSON formatting. You excel at identifying and categorizing pricing-related information with precision and consistency.\n\n# Task\nExtract pricing information from provided documentation and output it in a specific JSON format that separates included and not included items.\n\n# Context\nUsers need to quickly understand what is and isn't included in pricing structures from various documents. This structured extraction enables clear comparison, analysis, and decision-making around pricing models. The JSON format ensures the data is machine-readable and easily integrated into other systems or workflows.\n\n# Instructions\nThe assistant should:\n\n1. **Analyze the provided documentation thoroughly** to identify all pricing-related information, specifically looking for items, features, services, or components that are explicitly mentioned as included or excluded from the pricing.\n\n2. **Extract included items** - any features, services, components, or benefits that are stated as part of the base price or included in the offering without additional cost.\n\n3. **Extract not included items** - any features, services, components, or benefits that are explicitly mentioned as excluded, requiring additional payment, or available as add-ons.\n\n4. **Output the information in the following exact JSON structure**:\n```json\n{\n  \"pricing_info\": {\n    \"included\": [],\n    \"not_included\": []\n  }\n}\n```\n\n5. **Populate the arrays** with clear, concise strings describing each item. Each item should be a separate element in the appropriate array.\n\n6. **Handle ambiguous cases** by only including items that are explicitly stated. If an item's inclusion status is unclear or not mentioned, omit it from both arrays rather than making assumptions.\n\n7. **Maintain consistency** in terminology and formatting across all extracted items, using the exact language from the source document where possible.\n\n8. **Return only valid JSON** with no additional commentary, explanations, or markdown formatting around the JSON output.\n\n\n**Apply Latvian language rules strictly**:\n   - Use \"numuri\" not \"istabas\" for rooms\n   - Use \"viesnīca tikai pieaugušajiem\" not \"pieaugušo viesnīca\" for adults-only hotels\n   - Use \"piekrastē\" not \"virs jūras\" or \"kalnā virs jūras\" for coastal locations\n   - Maintain correct Latvian grammar, gender agreement, and terminology throughout"
                    },
                    "promptType": "define",
                    "needsFallback": false,
                    "hasOutputParser": true,
                    "aiAgentStarterCallout": "",
                    "preBuiltAgentsCallout": ""
                },
                "typeVersion": 2.2
            },
            "tags": [],
            "level": "warning",
            "stack": "NodeOperationError: A Chat Model sub-node must be connected and enabled\n    at validateInputConfiguration (\/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1.30_08b575bec2313d5d8a4cc75358971443\/node_modules\/n8n-core\/src\/execution-engine\/node-execution-context\/utils\/get-input-connection-data.ts:219:11)\n    at ExecuteContext.getInputConnectionData (\/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1.30_08b575bec2313d5d8a4cc75358971443\/node_modules\/n8n-core\/src\/execution-engine\/node-execution-context\/utils\/get-input-connection-data.ts:259:2)\n    at ExecuteContext.getInputConnectionData (\/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1.30_08b575bec2313d5d8a4cc75358971443\/node_modules\/n8n-core\/src\/execution-engine\/node-execution-context\/execute-context.ts:180:39)\n    at getChatModel (\/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/@n8n+n8n-nodes-langchain@file+packages+@n8n+nodes-langchain_fc553bfe732254ec5207074cf9e2ceb7\/node_modules\/@n8n\/n8n-nodes-langchain\/nodes\/agents\/Agent\/agents\/ToolsAgent\/common.ts:281:36)\n    at ExecuteContext.toolsAgentExecute (\/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/@n8n+n8n-nodes-langchain@file+packages+@n8n+nodes-langchain_fc553bfe732254ec5207074cf9e2ceb7\/node_modules\/@n8n\/n8n-nodes-langchain\/nodes\/agents\/Agent\/agents\/ToolsAgent\/V2\/execute.ts:195:22)\n    at processTicksAndRejections (node:internal\/process\/task_queues:105:5)\n    at ExecuteContext.execute (\/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/@n8n+n8n-nodes-langchain@file+packages+@n8n+nodes-langchain_fc553bfe732254ec5207074cf9e2ceb7\/node_modules\/@n8n\/n8n-nodes-langchain\/nodes\/agents\/Agent\/V2\/AgentV2.node.ts:131:10)\n    at WorkflowExecute.executeNode (\/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1.30_08b575bec2313d5d8a4cc75358971443\/node_modules\/n8n-core\/src\/execution-engine\/workflow-execute.ts:1265:8)\n    at WorkflowExecute.runNode (\/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1.30_08b575bec2313d5d8a4cc75358971443\/node_modules\/n8n-core\/src\/execution-engine\/workflow-execute.ts:1446:11)\n    at \/usr\/local\/lib\/node_modules\/n8n\/node_modules\/.pnpm\/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1.30_08b575bec2313d5d8a4cc75358971443\/node_modules\/n8n-core\/src\/execution-engine\/workflow-execute.ts:1847:27",
            "context": [],
            "message": "A Chat Model sub-node must be connected and enabled",
            "messages": [],
            "timestamp": 1764692037501,
            "workflowId": "gJ6Pjcm2EmKJTNZZ",
            "executionId": "8135",
            "functionality": "regular"
        },
        "functionality": "regular"
    }
}