---
title: n8n Nightly Vault Sync
area: infrastructure
tags: [n8n, obsidian, llm, automation, nightly]
created: 2026-03-27
updated: 2026-05-27
status: active
related: [[Infrastructure/Automation/n8n Workflows]], [[Infrastructure/Architecture]], [[Infrastructure/Automation/Cron Jobs]], [[Infrastructure/Services/Docker Services]]
---

# n8n Nightly Vault Sync

## Overview

- **Workflow:** `Nightly Obsidian Vault Sync`
- **Workflow ID:** `75JCevkdgkyCr2qH`
- **Status:** active
- **Trigger:** nightly cron expression `45 23 * * *`
- **Local LLM:** `gemma-4-26B-A4B-it-UD-IQ2_M.gguf`

## Purpose

Create a concise nightly sync note in the shared Obsidian vault so there is a low-noise daily operational breadcrumb without manually editing the canonical architecture/automation notes every single night.

## What it does

Each run:
1. reads these shared vault notes:
   - `Infrastructure/Architecture.md`
   - `Infrastructure/Automation/n8n Workflows.md`
   - `Infrastructure/Automation/Cron Jobs.md`
   - `Infrastructure/Services/Docker Services.md`
2. checks live health from:
   - `http://127.0.0.1:18808/healthz`
   - `http://127.0.0.1:18806/v1/models`
3. sends that context to the local Gemma 4 model
4. writes a nightly note to:
   - `Notes/YYYY-MM-DD Nightly Vault Sync.md`

## Output style

The nightly note is intended to stay compact:
- short summary
- current state
- follow-ups / drift worth checking

## Design note

This workflow writes a **nightly snapshot note** rather than trying to auto-rewrite all canonical architecture docs. That keeps the automation lower-risk while still keeping the vault alive and current every night.

## Test note

- On 2026-03-27, the schedule was temporarily advanced for a near-term test run and an automatic revert to the normal nightly cron was scheduled immediately afterward.
- At `2026-03-27 23:39 UTC`, the revert completed successfully. Verified via n8n API that the workflow is active and the `Schedule Trigger` node is back on cron `45 23 * * *` UTC.
