How techinpark/appstore-status-bot works
External Services Layer
• App Store Connect API (Primary data source)
• Slack Webhook API (Notification endpoint)
• Discord Webhook API (Optional notification endpoint)
• GitHub Gist API (State storage)
Core Application Components
• Status Checker Module (check_status.js)
• Data Fetcher Module (fetch_app_status.rb)
• Notification Dispatchers:
• Slack Module (slack.js)
• Discord Module (discord.js)
Configuration & Support Components
• Localization System (locales directory)
• GitHub Actions Workflow (fetch.yml)
• Authentication & Secrets Management
Component Representation
• Use rectangles for main services (App Store Connect, Slack, Discord)
• Use hexagons for processing modules (Status Checker, Data Fetcher)
• Use rounded rectangles for support systems (Localization)
Connection Flows
• [GitHub Actions Environment]
• Scheduler (15-min intervals)
• Authentication Manager
• Core Processing Pipeline
Data flow
• App Store Connect API → fetch_app_status.rb → check_status.js
• → [Notification Dispatchers] → Slack/Discord
Localization system
• Localization Store (en/ja/ko)
• ↓
• Message Formatter
• ↓
• Notification Dispatchers
Key Elements to Label:
• API endpoints
• Authentication points (KEY_ID, ISSUER_ID, WEBHOOK URLs)
• Data transformation steps
• State management (GitHub Gist)
• Scheduled triggers
Remember to:
• Version/date information
• Critical dependencies or failure points
• Document the periodic nature of the system