Skip to main content
This guide covers the more advanced patterns for scheduled tasks: conditional triggers that only fire when something is true, and multi-step tasks that chain several actions together. Once you are comfortable with basic briefings and monitors, these patterns let you automate more of your process. The concept behind this is Scheduled Tasks.

​
Conditional tasks

A conditional task does work only when a condition is met, which keeps output relevant and reduces noise: 
Every trading day, check my watchlist. If any name is down more than 8% from where I flagged it, run a quick analysis on what changed and whether the thesis still holds. If nothing crosses that line, don't send anything.
The pattern is: check a condition, and act only if it is true. This is more useful than a task that runs the full analysis every day regardless.

​
Multi-step tasks

A multi-step task does several things in sequence, producing a more complete output: 
Every Monday morning: first, summarize how my portfolio performed last week. Then, check whether any holdings hit risk thresholds. Then, flag which holdings report earnings this week. Deliver as one combined briefing.
Each step builds on the last, and you get one coherent report instead of three separate alerts.

​
Combining conditions and steps

The most powerful tasks combine both: 
Each morning, scan my watchlist. For any name with unusual volume or a move over 5%, pull the likely cause and check whether institutions are accumulating or distributing. Summarize only the names that triggered, with a recommended next step for each.

​
Tips for advanced tasks

  • State the condition precisely. “If a name moves a lot” is vague; “if a name moves more than 5%” is actionable.
  • Order the steps logically. Put the gating check first so the task does not do unnecessary work.
  • Keep output consolidated. A single combined briefing is easier to act on than several fragmented alerts.
  • Test before relying. Run the task a few times and refine the logic before trusting it for anything important.

​
When to split into multiple tasks instead

Not everything belongs in one complex task. Split when:
  • The pieces run on different schedules (hourly monitor vs weekly review)
  • The pieces should go to different channels (urgent alerts to Telegram, deep reviews to web)
  • One task is becoming hard to reason about

​
Common mistakes

  • Over-engineering. A task with too many branches is hard to debug. Start simple and add complexity only as needed.
  • Vague conditions. Conditional logic needs concrete thresholds to work reliably.
  • Silent failures going unnoticed. Review logs periodically so you know your tasks are running as intended.