Academy
6. Wake-ups: Schedules and Watchers
Set up recurring tasks and event-driven watchers so @oupi works on your behalf without manual triggers, and manage them with pause, arm, try-once and history.
Wake-ups let @oupi work on your behalf without you pressing a button. There are two kinds:
• Scheduled tasks — run at a time you set: every morning at 8, every Monday, the first of each month. Think of them as recurring missions: same goal, executed automatically on a cadence.
• Watchers — react to an event instead of a clock: a new email matching a rule, a change detected in a connected tool, or any trigger from your integrations. When the event fires, @oupi launches the mission you defined.
Both types live in the Wake-ups section of the Assistant and produce deliverables just like any other mission — files land in a durable Studio folder that fills up with each run, and you can optionally receive them by email.
Every wake-up has four controls you should know:
• Arm — activates the wake-up so it will fire on its next schedule or event. • Pause — suspends it without deleting it. The configuration stays intact; nothing runs until you arm it again. • Try once — runs the wake-up immediately, right now, regardless of its schedule or trigger. Use this to test a new wake-up before relying on it. • History — shows every past run with its result, verification verdict and cost. Review it to confirm the wake-up is producing what you expect.
These controls mean you can iterate safely: create a wake-up, try it once, check the result, adjust the mission wording, try again, then arm it for real.
Write your wake-up mission the same way you write any good mission: state the outcome, who it's for, and the format you want. @oupi plans the steps itself. A clear goal keeps each automated run fast and cost-effective — remember, every run costs credits proportional to the work done.
After creating a wake-up, always use Try once before arming it. Check the result and the verification verdict on the mission page. If the output isn't right, adjust the mission description and try again. This avoids wasting credits on a recurring task that misses the mark.
Watchers are especially powerful when combined with your connected integrations — Microsoft 365, Google Workspace, Slack, Teams, MCP servers, and more. For example, you could set a watcher that triggers whenever a specific mailbox receives an email with "invoice" in the subject, and have @oupi extract the key data into a spreadsheet.
@oupi picks the right tools for each run automatically. If a useful integration isn't connected yet, it will tell you — so watchers can also surface gaps in your setup.
Open the Wake-ups section in your Assistant. Create a simple scheduled wake-up — for example, "Every Monday at 9 AM, summarize the latest items in my inbox and list action items." Use Try once to run it immediately, then check the result and its verification verdict in the history.
Wake-ups make @oupi proactive: scheduled tasks run on a cadence, watchers react to events from your integrations. Both produce deliverables in a durable Studio folder (with optional email). Use Arm to activate, Pause to suspend, Try once to test, and History to review past runs. Always test before arming, write clear outcome-focused goals, and check verification verdicts to keep quality high and costs under control.