Business Operations Hub
Natural Language Commands to Automated Workflows via Discord
Pipeline at a glance
Channel-Based Routing
Zero-Code Architecture
Resilient Message Processing
Situation
A solo operator managing multiple projects needed a central command interface to handle daily operations: task management, meeting follow-ups, daily journaling, and information collection — spread across separate tools with no unified access point.
Task
Build a single Discord-based operations hub where natural language messages in specific channels automatically route to the correct service — without writing custom application code.
Actions
Channel-Based Routing
Each Discord channel maps to a specific business function with natural language command recognition.
- #tasks → Create, update, and manage tasks in Notion (status changes, batch completion, listing)
- #meeting-todo → Auto-generated tasks from meeting transcriptions
- #journaling → Write timestamped entries to both Notion and a local knowledge base
- #info-collect → Route research requests to external agents for information gathering
Zero-Code Architecture
Entire hub is declarative configuration — no custom handler code.
- All routing defined in markdown configuration, not code
- Notion operations via Model Context Protocol (MCP) server
- Runs as macOS background service via LaunchAgent
Resilient Message Processing
Automatic backlog handling ensures no messages are lost.
- Tracks last processed message ID across sessions
- Catches up on missed messages at startup
- Filters bot messages, routes user messages to handlers
Results
- Single interface for all daily operations — no context switching between tools
- Low-maintenance setup — changes are made through configuration updates, not code deployments
- Natural language interface eliminates command syntax learning curve
- Adding a new channel/workflow is a configuration change, not a code change