Platform
Automation
Create, validate, test, publish, and observe rules attached to task boards.
Task boards
Understand the tasks and lifecycle rules evaluate.
Notifications
Understand in-app and email outcomes.
Supported rules
| Rule | Purpose |
|---|---|
| Due before | Notify before a due date. |
| Overdue | Notify for incomplete overdue work. |
| Stale task follow-up | Notify after a period without activity. |
| Checklist incomplete before due | Notify when checklist work remains near the due date. |
| Overdue escalation | Escalate after a configured grace period. |
| Auto-complete checklist | Move eligible tasks to Done when all checklist items are complete. |
| Flag unassigned | Surface tasks without an active assignee. |
Rule lifecycle
Rules have a published configuration, optional draft, enabled state, immutable version history, and optional archive state. Draft editing does not affect live execution until published. Authorized users can validate, test, archive, restore, and roll back supported versions.
Conditions, recipients, and actions
A rule combines its trigger type with timing or state configuration, recipient choices, and delivery channels. Notifications can target task assignees and eligible administrators. In-app and email channels are evaluated independently, and email requires an eligible address and available email configuration.
Validation and testing
- Validation reports missing recipients, unsupported delivery, invalid timing, duplicate rules, and whether work currently matches.
- A dry run evaluates current matching without replacing scheduled execution.
- A test notification targets the requesting authorized administrator and records its own test result.
Run history
Run history distinguishes Live, Dry run, and Test notification modes. Each run records start and finish times, rule and optional task context, delivery summaries, safe failure information, and one of Success, Skipped, or Failed.
What Skipped means
Skipped means the rule was evaluated but intentionally produced no action. Common reasons include a paused, completed, or archived board; a reached event cutoff; a disabled or archived rule; a completed or archived task; no longer matching conditions; duplicate prevention; or no supported delivery result.
Lifecycle safety
Automation executes only while the board is Active, the rule is enabled and not archived, and the relevant task is neither Done nor archived. For an event-linked board, the event’s scheduled time is an additional cutoff. Retrying an old run reevaluates current state and records Skipped instead of replaying stale work when the original conditions no longer apply.
Presets and templates
Automation presets package reusable rule configurations. Applying a preset previews validation and creates the eligible rules without changing the meaning of existing rules or task templates.