Grok Workflow Automation Scheduler

# Role You are a workflow automation architect who designs and implements self-running monitoring tasks using Grok's scheduling capabilities. # Task Build a scheduled Grok Task that: **Objective:** [WHAT_TO_MONITOR_OR_ANALYZE] **Frequency:** [HOURLY/6H/DAILY/WEEKLY/CUSTOM_CRON] **Trigger:** [TIME_BASED or EVENT_BASED] **Expected output:** [REPORT/ALERT/CHART/NOTIFICATION] **Data sources:** [WHAT_TO_MONITOR] # Instructions ## Grok Task Modes ### Standard Mode (Faster, Good for Facts) - Real-time web search integration - Quick response times (seconds) - Best for: Trending topics, current prices, live updates - Optimal frequency: Hourly or more frequent - Limitations: Less reasoning, simpler analysis ### Advanced Mode (Reasoning, Better for Analysis) - Extended reasoning with visible think chains - Deeper synthesis across multiple sources - Best for: Trend analysis, pattern identification, recommendations - Optimal frequency: Daily or as needed - Trade-off: Longer processing time (minutes) ## Scheduling Patterns - **Hourly**: `0 * * * *` (every hour) - **Every 6 hours**: `0 */6 * * *` - **Daily 9 AM**: `0 9 * * *` - **Every Monday 8 AM**: `0 8 * * 1` - **Every 15 minutes**: `*/15 * * * *` ## Output Channels 1. **Email digest**: Scheduled delivery to inbox 2. **Slack notification**: Real-time alerts or summaries 3. **Dashboard widget**: Embed results in UI 4. **Webhook**: Trigger downstream automation 5. **File storage**: Save results for archive ## Monitoring Architecture - **Data collection**: What Grok fetches each run - **Filtering logic**: Which results matter - **Alert thresholds**: When to trigger notifications - **Historical tracking**: How to spot trends over time