Durasi: 20 menit | Block: 3

---

🎯 Task

Build 1 integration pattern yang cocok dengan use case kamu.

---

📋 Quick Build Guide

Step 1: Pilih Pattern

Pattern A (Data Feed)     → Kalau use case kamu scheduled report
Pattern B (Draft-Approve) → Kalau use case kamu auto-reply
Pattern C (Detect-React)  → Kalau use case kamu monitoring

Step 2: Setup Hermes Endpoint

Pastikan Hermes bisa receive request dari n8n:

# Test Hermes API
curl -X POST http://[hermes-host]:[port]/api/chat \
  -H "Content-Type: application/json" \
  -d '{"message": "Test connection dari n8n"}'

Step 3: Build n8n Side

For Pattern A (Data Feed):

1. [Schedule Node] → Set cron
2. [Data Source Node] → Read data
3. [Code Node] → Format as context string
4. [HTTP Request Node] → POST to Hermes
   URL: [hermes-api-url]
   Body: {
     "message": "Data: \{{ $json.formatted }}. Buat brief."
   }
5. [Notification Node] → Send result

For Pattern B (Draft-Approve):

1. [Webhook Node] → Receive trigger
2. [HTTP Request Node] → POST to Hermes
   Body: {
     "message": "Customer inquiry: \{{ $json.pesan }}. Draft reply."
   }
3. [Slack/Email Node] → Send draft for approval
4. [Wait Node] → Wait for approval callback
5. [If Node] → Approved?
6. [HTTP Request Node] → Execute (send reply)

For Pattern C (Detect-React):

1. [Schedule Node] → Polling frequency
2. [Data Source Node] → Get current data
3. [Code Node] → Detect anomaly
4. [If Node] → Anomaly detected?
5. [HTTP Request Node] → POST to Hermes for analysis
6. [Alert Node] → Send to Slack/WhatsApp

---

🔧 Common Issues & Fixes

Issue	Fix
Hermes API timeout	Increase timeout di HTTP Request node
Connection refused	Check Hermes running + port + firewall
Response format mismatch	Check Hermes response format, adjust n8n parsing
Data too large for context	Truncate/format data di Code Node sebelum send
API key missing	Add Authorization header

---

✅ Build Checklist

• [ ] Pattern dipilih
• [ ] Hermes accessible dari n8n
• [ ] n8n workflow terbangun
• [ ] Data flow tested
• [ ] End-to-end tested