cleanup

bitbylaw/steps/advoware_cal_sync/calendar_sync_cron_step.md

@@ -0,0 +1,51 @@
+---
+type: step
+category: cron
+name: Calendar Sync Cron
+version: 1.0.0
+status: active
+tags: [calendar, sync, cron, scheduler]
+dependencies: []
+emits: [calendar_sync_all]
+---
+
+# Calendar Sync Cron Step
+
+## Zweck
+Täglicher Trigger für die Calendar-Synchronisation. Startet die Sync-Pipeline um 2 Uhr morgens.
+
+## Config
+```python
+{
+    'type': 'cron',
+    'name': 'Calendar Sync Cron',
+    'schedule': '0 2 * * *',  # Daily at 2 AM
+    'emits': ['calendar_sync_all'],
+    'flows': ['advoware_cal_sync']
+}
+```
+
+## Verhalten
+1. Cron triggert täglich um 02:00 Uhr
+2. Emittiert Event `calendar_sync_all`
+3. Event wird von `calendar_sync_all_step` empfangen
+4. Startet Cascade: All → per Employee → Sync
+
+## Event-Payload
+```json
+{}
+```
+Leer, da keine Parameter benötigt werden.
+
+## Monitoring
+Logs: `[INFO] Calendar Sync Cron triggered`
+
+## Manual Trigger
+```bash
+# Use API endpoint instead of waiting for cron
+curl -X POST "http://localhost:3000/advoware/calendar/sync" \
+  -H "Content-Type: application/json" \
+  -d '{"full_content": true}'
+```
+
+Siehe: [calendar_sync_api_step.md](calendar_sync_api_step.md)