The Vertex telemetry stack
n8n takes the log burst, Vertex scores multimodal anomalies, Julius is the workbook. BigQuery stays a write inside n8n.
Who owns what
n8n
The hop — logs in, Julius out. BigQuery is infra, not a slot.
Try n8n (opens in a new tab)Vertex AI
The score — image+text log anomalies. Not the sheet.
Try Vertex AI (opens in a new tab)Julius AI
The workbook — charts the on-call defends. Not Vertex training.
Try Julius AI (opens in a new tab)
How to use this stack
- Alert payload hits n8n. Warehouse inserts stay in the node, not a fourth tool.
- Vertex scores the burst (screenshot plus log text). Do not also run Groq on the same dump.
- n8n appends the scored rows into Julius. One orchestrator.
- This is not spreadsheet-to-brief (that one starts from a CSV, not telemetry). Not OpenRouter RCA.