mirror of
https://github.com/different-ai/openwork
synced 2026-05-11 01:32:04 +02:00
37 lines
942 B
Plaintext
37 lines
942 B
Plaintext
---
|
|
title: "Automations for repeatable jobs"
|
|
description: "Schedule daily and weekly workflows in OpenWork"
|
|
---
|
|
|
|
Use this when you need predictable recurring outputs.
|
|
|
|
## Why this pattern works
|
|
|
|
- Each automation maps to one business outcome.
|
|
- Outputs stay easy to inspect and debug.
|
|
- Team expectations stay predictable.
|
|
|
|
## Build the automation set
|
|
|
|
1. Open **Automations** (beta).
|
|
2. Create one job for each outcome, for example:
|
|
- Daily ops summary
|
|
- Weekly wins/blockers summary
|
|
- Recurring competitor scan
|
|
3. Keep each job single-purpose. Do not merge everything into one mega prompt.
|
|
4. Name jobs by outcome, not by implementation detail.
|
|
|
|
## Example split
|
|
|
|
- `daily-ops-summary`
|
|
- `weekly-team-brief`
|
|
- `competitor-scan-core`
|
|
|
|
## Debugging checklist
|
|
|
|
- Does each job write to a clear output path?
|
|
- Can you explain job success/failure in one sentence?
|
|
- Can one job fail without blocking the others?
|
|
|
|
If not, split further.
|