Automations and System Packs sound similar at a glance, but they solve different problems. This page makes the difference explicit.
Operations
How automations and System Packs fit together
Automations are about running work
MoodLens automations can run on schedules, workspace events, or incoming webhooks. That makes them useful once a team already knows a flow is stable enough to operationalize.
- Scheduled runs
- Event-driven runs
- Webhook-triggered runs
- Logs, dry runs, and manual runs
System Packs are about reusing setup
System Packs package the reusable operating blueprint: employee roster, prompts, knowledge setup, compatible automations, and shared playbook. They are for rollout and reuse, not for storing runtime secrets or conversation history.
The practical sequence is prove, repeat, then scale
The most honest product story is simple: start with direct assistance, convert proven patterns into automations, then package the reusable setup as a System Pack when the team wants to repeat it elsewhere.