{ "edges": [ { "to": "36b601a1-63f6-46da-8a2c-c76c6c8fe217", "from": "c01781b4-9e5e-44ec-8213-67f5fa9097b7", "toPort": "0", "fromPort": "0" }, { "to": "1e69dea4-3cf0-4028-b8ce-8f9f54c72193", "from": "f0308c27-5a25-4308-97c6-8aa3c3d2af26", "toPort": "0", "fromPort": "ai_languageModel" }, { "to": "1e69dea4-3cf0-4028-b8ce-8f9f54c72193", "from": "36b601a1-63f6-46da-8a2c-c76c6c8fe217", "toPort": "0", "fromPort": "1" }, { "to": "e6974b0a-0837-4649-bba5-860e7a461ddb", "from": "7be06386-0800-4512-96a3-bcc01016d501", "toPort": "0", "fromPort": "0" }, { "to": "d3440c64-0774-4919-a5ef-6926ed597532", "from": "1e69dea4-3cf0-4028-b8ce-8f9f54c72193", "toPort": "0", "fromPort": "0" }, { "to": "c01781b4-9e5e-44ec-8213-67f5fa9097b7", "from": "6c9a14c0-b8bc-48d3-b70f-56b23901262b", "toPort": "0", "fromPort": "0" }, { "to": "457a5e8c-eefc-4872-8c3b-570829ae6822", "from": "e6974b0a-0837-4649-bba5-860e7a461ddb", "toPort": "0", "fromPort": "0" }, { "to": "6c9a14c0-b8bc-48d3-b70f-56b23901262b", "from": "36816dcf-f2d8-42fc-ba3d-f05875160e9a", "toPort": "0", "fromPort": "0" }, { "to": "e6974b0a-0837-4649-bba5-860e7a461ddb", "from": "0d4738ef-2c9a-4e18-839a-c0d64a91cd49", "toPort": "0", "fromPort": "0" }, { "to": "36816dcf-f2d8-42fc-ba3d-f05875160e9a", "from": "457a5e8c-eefc-4872-8c3b-570829ae6822", "toPort": "0", "fromPort": "0" } ], "nodes": [ { "id": "0d4738ef-2c9a-4e18-839a-c0d64a91cd49", "name": "⏰ Daily Schedule Trigger", "type": "trigger", "params": { "kind": "n8n-nodes-base.scheduleTrigger", "rule": { "interval": [ {} ] } }, "position": [ -240, 112 ] }, { "id": "7be06386-0800-4512-96a3-bcc01016d501", "name": "▶️ Manual Test Run", "type": "manualTrigger", "params": {}, "position": [ -240, 256 ] }, { "id": "c01781b4-9e5e-44ec-8213-67f5fa9097b7", "name": "Add Player Context", "type": "code", "params": { "jsCode": "// Enrich game data with player-perspective context\n// Determines color played, ratings, result, and opening code\n\nconst game = $input.item.json;\nconst reviewingUsername = game._username;\n\nconst playedWhite = game.white.username.toLowerCase() === reviewingUsername.toLowerCase();\n\nconst playerColor = playedWhite ? 'White' : 'Black';\nconst opponentColor = playedWhite ? 'Black' : 'White';\nconst playerData = playedWhite ? game.white : game.black;\nconst opponentData = playedWhite ? game.black : game.white;\n\n// Map result codes to human-readable outcomes\nconst WIN_CODES = ['win'];\nconst LOSS_CODES = ['resigned', 'checkmated', 'timeout', 'abandoned'];\nconst DRAW_CODES = ['agreed', 'stalemate', 'repetition', 'insufficient', '50move', 'timevsinsufficient'];\n\nlet gameResult = 'Unknown';\nlet resultEmoji = '❓';\n\nif (WIN_CODES.includes(playerData.result)) {\n gameResult = 'Win'; resultEmoji = '🏆';\n} else if (LOSS_CODES.includes(playerData.result)) {\n gameResult = 'Loss'; resultEmoji = '💔';\n} else if (DRAW_CODES.includes(playerData.result)) {\n gameResult = 'Draw'; resultEmoji = '🤝';\n}\n\n// Extract ECO opening code from the eco URL field\nlet ecoCode = 'Unknown';\nif (game.eco) {\n const ecoMatch = game.eco.match(/\\/([A-E]\\d{2})/);\n if (ecoMatch) ecoCode = ecoMatch[1];\n}\n\nreturn {\n json: {\n ...game,\n reviewingUsername,\n playerColor,\n opponentColor,\n playerRating: playerData.rating,\n opponentUsername: opponentData.username,\n opponentRating: opponentData.rating,\n gameResult,\n resultEmoji,\n playerResult: playerData.result,\n opponentResult: opponentData.result,\n ecoCode\n }\n};" }, "position": [ 768, 192 ] }, { "id": "6c9a14c0-b8bc-48d3-b70f-56b23901262b", "name": "Sort Games (Latest First)", "type": "code", "params": { "jsCode": "// Sort all games by end time, newest first\n// Then output as individual items for the batch processor\nconst games = $input.item.json.games;\nconst username = $(\"Config - Username - Email\").first().json.username;\n\nif (!games || games.length === 0) {\n throw new Error(`No games found this month for player: ${username}`);\n}\n\n// Sort descending by end_time (most recent game first)\ngames.sort((a, b) => b.end_time - a.end_time);\n\n// Attach the reviewing username to each game for downstream use\nreturn games.map(game => ({\n json: {\n ...game,\n _username: username\n }\n}));" }, "position": [ 576, 192 ] }, { "id": "36816dcf-f2d8-42fc-ba3d-f05875160e9a", "name": "Fetch Games from Chess.com", "type": "http", "params": { "url": "={{ $json.url }}", "options": { "lowercaseHeaders": false }, "jsonHeaders": "{\n \"User-Agent\": \"Mozilla/5.0 (compatible; n8n-chess-coach-bot/1.0)\",\n \"Accept\": \"application/json\",\n \"Accept-Language\": \"en-US,en;q=0.9\"\n}", "sendHeaders": true, "specifyHeaders": "json" }, "position": [ 400, 192 ] }, { "id": "457a5e8c-eefc-4872-8c3b-570829ae6822", "name": "Build API URL (Current Month)", "type": "code", "params": { "jsCode": "// Build the Chess.com API URL for the current month's games\nconst username = $input.item.json.username;\n\nconst now = new Date();\nconst year = now.getFullYear();\nconst month = String(now.getMonth() + 1).padStart(2, '0');\n\n// Chess.com public API endpoint for monthly games\nconst url = `https://api.chess.com/pub/player/${username}/games/${year}/${month}`;\n\nreturn [\n {\n json: {\n username: username,\n year: year,\n month: month,\n url: url\n }\n }\n];" }, "position": [ 192, 192 ] }, { "id": "36b601a1-63f6-46da-8a2c-c76c6c8fe217", "name": "Process Last Game Only", "type": "passthrough", "params": { "mode": "noOp", "options": {} }, "position": [ 944, 192 ] }, { "id": "e6974b0a-0837-4649-bba5-860e7a461ddb", "name": "Config - Username - Email", "type": "set", "params": { "options": {}, "assignments": { "assignments": [ { "id": "username-assignment", "name": "username", "type": "string", "value": "uer-name-here" }, { "id": "706913d1-70af-4459-aba8-ee8f4a0a95d2", "name": "email", "type": "string", "value": "user@example.com" } ] } }, "position": [ -16, 192 ] }, { "id": "1e69dea4-3cf0-4028-b8ce-8f9f54c72193", "name": "AI Chess Coach (Analysis)", "type": "llm", "params": { "text": "=# Chess Game Analysis Request\n\n## Player Info\n- **Reviewing Player**: {{ $json.reviewingUsername }} ({{ $json.playerColor }}, Rated {{ $json.playerRating }})\n- **Opponent**: {{ $json.opponentUsername }} ({{ $json.opponentColor }}, Rated {{ $json.opponentRating }})\n- **Result**: {{ $json.resultEmoji }} {{ $json.gameResult }}\n- **Time Control**: {{ $json.time_control }} ({{ $json.time_class }})\n- **Opening (ECO)**: {{ $json.ecoCode }}\n- **Game Link**: {{ $json.url }}\n- **Player Result Code**: {{ $json.playerResult }}\n- **Opponent Result Code**: {{ $json.opponentResult }}\n\n## Position & Game Record\n**Final FEN**: `{{ $json.fen }}`\n\n**PGN**:\n```\n{{ $json.pgn }}\n```\n\n---\n\n## Analysis Instructions\n\nAnalyze this game from {{ $json.playerColor }}'s perspective ({{ $json.reviewingUsername }}, ~{{ $json.playerRating }} rating).\n\nProduce a complete coaching report in **clean HTML** (ready for Gmail) using the exact structure below.\n\n---\n\n### 1. 📊 Game Summary\n\nInclude a header block with all player info, result, time control, opening code, and a [View Game] hyperlink.\n\nThen write **2–3 paragraphs** covering:\n- Opening phase evaluation\n- Middlegame key developments\n- Endgame progression (if applicable)\n- The decisive moment(s)\n\n---\n\n### 2. 🎯 Critical Moments (3–5 turning points)\n\nFor each moment:\n- Clearly describe the position and what move was played\n- Explain what should have been done instead\n- State the **underlying concept or pattern**\n\n---\n\n### 3. ❌ Mistake Categories\n\nGroup errors under these headings (only include relevant ones):\n- **Tactical Oversights** — Missing captures, checks, threats\n- **Positional Errors** — Weak squares, piece placement, pawn structure\n- **Opening Issues** — Principle violations or theory deviations\n- **Endgame Technique** — Conversion or defensive mistakes\n- **Time Management** — If it influenced the result\n\n---\n\n### 4. ✅ What Went Well (2–4 highlights)\n\nRecognize genuine strengths — good tactics, solid positional choices, fighting spirit.\n\n---\n\n### 5. 💡 Five Key Lessons\n\nExactly 5 specific, memorable takeaways with context tied to THIS game.\n\n---\n\n### 6. 📚 Training Plan\n\n- **Primary Focus**: Main weakness to address\n- **Drill 1**: Specific exercise\n- **Drill 2**: Specific exercise\n- **Drill 3**: Specific exercise\n- **Study Resources**: Concrete recommendations (videos, books, Chess.com tools)\n\n---\n\n### 7. 💪 Closing Motivation\n\n1–2 encouraging sentences with a clear, actionable next step.", "prompt": "=# Chess Game Analysis Request\n\n## Player Info\n- **Reviewing Player**: {{ $json.reviewingUsername }} ({{ $json.playerColor }}, Rated {{ $json.playerRating }})\n- **Opponent**: {{ $json.opponentUsername }} ({{ $json.opponentColor }}, Rated {{ $json.opponentRating }})\n- **Result**: {{ $json.resultEmoji }} {{ $json.gameResult }}\n- **Time Control**: {{ $json.time_control }} ({{ $json.time_class }})\n- **Opening (ECO)**: {{ $json.ecoCode }}\n- **Game Link**: {{ $json.url }}\n- **Player Result Code**: {{ $json.playerResult }}\n- **Opponent Result Code**: {{ $json.opponentResult }}\n\n## Position & Game Record\n**Final FEN**: `{{ $json.fen }}`\n\n**PGN**:\n```\n{{ $json.pgn }}\n```\n\n---\n\n## Analysis Instructions\n\nAnalyze this game from {{ $json.playerColor }}'s perspective ({{ $json.reviewingUsername }}, ~{{ $json.playerRating }} rating).\n\nProduce a complete coaching report in **clean HTML** (ready for Gmail) using the exact structure below.\n\n---\n\n### 1. 📊 Game Summary\n\nInclude a header block with all player info, result, time control, opening code, and a [View Game] hyperlink.\n\nThen write **2–3 paragraphs** covering:\n- Opening phase evaluation\n- Middlegame key developments\n- Endgame progression (if applicable)\n- The decisive moment(s)\n\n---\n\n### 2. 🎯 Critical Moments (3–5 turning points)\n\nFor each moment:\n- Clearly describe the position and what move was played\n- Explain what should have been done instead\n- State the **underlying concept or pattern**\n\n---\n\n### 3. ❌ Mistake Categories\n\nGroup errors under these headings (only include relevant ones):\n- **Tactical Oversights** — Missing captures, checks, threats\n- **Positional Errors** — Weak squares, piece placement, pawn structure\n- **Opening Issues** — Principle violations or theory deviations\n- **Endgame Technique** — Conversion or defensive mistakes\n- **Time Management** — If it influenced the result\n\n---\n\n### 4. ✅ What Went Well (2–4 highlights)\n\nRecognize genuine strengths — good tactics, solid positional choices, fighting spirit.\n\n---\n\n### 5. 💡 Five Key Lessons\n\nExactly 5 specific, memorable takeaways with context tied to THIS game.\n\n---\n\n### 6. 📚 Training Plan\n\n- **Primary Focus**: Main weakness to address\n- **Drill 1**: Specific exercise\n- **Drill 2**: Specific exercise\n- **Drill 3**: Specific exercise\n- **Study Resources**: Concrete recommendations (videos, books, Chess.com tools)\n\n---\n\n### 7. 💪 Closing Motivation\n\n1–2 encouraging sentences with a clear, actionable next step.", "options": { "systemMessage": "# Chess Coach AI — System Prompt\n\nYou are an experienced, encouraging chess coach who reviews games for club-level players rated 600–1400.\n\n## Your Voice\n- Warm, clear, and conversational English\n- Always constructive — never harsh or discouraging\n- Explain WHY moves work, not just that they do\n- Use simple language; briefly explain any chess jargon on first use\n\n## Analysis Philosophy\n- Prioritize **big-picture understanding** over engine-perfect lines\n- Focus on **recurring patterns and themes**, not isolated blunders\n- Emphasize **practical improvement** the player can apply next game\n- Balance every critique with genuine positive reinforcement\n\n## What to Avoid\n- Long engine variations (e.g., \"After 15...Nxe4 16.Bxf7+ Ke8 17.Bd5...\")\n- Heavy opening theory jargon\n- Nitpicking minor inaccuracies in winning positions\n- Discouraging or condescending language\n\n## Output Format — STRICT HTML for Gmail\nUse ONLY these HTML elements:\n- `

` and `

` for section headers\n- `
` for paragraphs\n- `
` and `
` for bullet lists\n- `
` and `
` for numbered lists\n- `` for bold emphasis\n- `` for italics\n- `` for links\n- `
` for line breaks\n- `
` for section dividers\n- `
` for key takeaways\n\nDO NOT use:\n- Markdown syntax (no **, ##, -, , ~)\n- Inline CSS styles\n- Tables (poor Gmail rendering)\n- Images or external assets\n\n## Philosophy\nEvery game, win or lose, is a lesson. Help the player understand what happened, why it happened, and exactly what to practice next. Leave them excited to play their next game." }, "provider": "openai", "promptType": "define", "approximated": true, "systemMessage": "# Chess Coach AI — System Prompt\n\nYou are an experienced, encouraging chess coach who reviews games for club-level players rated 600–1400.\n\n## Your Voice\n- Warm, clear, and conversational English\n- Always constructive — never harsh or discouraging\n- Explain WHY moves work, not just that they do\n- Use simple language; briefly explain any chess jargon on first use\n\n## Analysis Philosophy\n- Prioritize big-picture understanding over engine-perfect lines\n- Focus on recurring patterns and themes, not isolated blunders\n- Emphasize practical improvement the player can apply next game\n- Balance every critique with genuine positive reinforcement\n\n## What to Avoid\n- Long engine variations (e.g., \"After 15...Nxe4 16.Bxf7+ Ke8 17.Bd5...\")\n- Heavy opening theory jargon\n- Nitpicking minor inaccuracies in winning positions\n- Discouraging or condescending language\n\n## Output Format — STRICT HTML for Gmail\nUse ONLY these HTML elements:\n- `
` and `
` for section headers\n- `
` for paragraphs\n- `
` and `
` for bullet lists\n- `
` and `
` for numbered lists\n- `` for bold emphasis\n- `` for italics\n- `*` for links\n- `
` for line breaks\n- `
` for section dividers\n- `
` for key takeaways\n\nDO NOT use:\n- Markdown syntax (no **, ##, -, *, ~)\n- Inline CSS styles\n- Tables (poor Gmail rendering)\n- Images or external assets\n\n## Philosophy\nEvery game, win or lose, is a lesson. Help the player understand what happened, why it happened, and exactly what to practice next. Leave them excited to play their next game." }, "position": [ 1168, 208 ] }, { "id": "f0308c27-5a25-4308-97c6-8aa3c3d2af26", "name": "LLM — Google Gemini", "type": "llm", "params": { "options": {}, "provider": "google" }, "position": [ 1168, 416 ] }, { "id": "d3440c64-0774-4919-a5ef-6926ed597532", "name": "Email the Report", "type": "integration", "params": { "sendTo": "={{ $('Config - Username - Email').first().json.email }}\n", "message": "={{ $json.output }}", "options": { "appendAttribution": false }, "service": "gmail", "subject": "=♟️ Chess Game Review — {{ $('Process Last Game Only').item.json.reviewingUsername }}", "operation": "read" }, "position": [ 1584, 208 ] } ] }

` and `

` and `

` for section headers\n- `` for paragraphs\n- `

Get chess.com game reviews by email using Google Gemini or other LLMs