Learn · Cloud automations
Recurring checks that run while your browser is closed
In deployments where the cloud task service is enabled, Echo Notes automations run on the server on a schedule you configure, checking approved public sources without keeping a browser tab open. Each task records its next run, run history, in-app delivery, and audit events, with pause, resume, run now, and versioned edits. Availability depends on the deployment operator, and the automation console is read-only offline.
01 · Definition
A task with a schedule and a paper trail
A cloud automation is a server-run task built from an approved draft: a name, a schedule with time zone, configured public sources, and conditions. Unlike a browser reminder, the server executes active tasks independently of whether your browser is open. Every execution leaves run, delivery, and audit records so you can see when the task ran, what it produced, and how its configuration changed over time.
Automation drafts follow the same approval rule as notes: the assistant prepares the draft, and creation happens only after you approve it. See Features for the full workflow.
02 · Steps
Set up your first recurring check
Start with one public source you already check manually every week.
- Your problem
- You need to check public information regularly without keeping a tab open or repeating the same steps.
- Product behavior
- Echo Notes shows the next run and supports pause, resume, run now, and versioned edits while recording run, in-app delivery, and audit events.
- Your result
- You can see when the task ran, what it produced, and how its configuration changed.
Approve the draft
Review the proposed task name, schedule, sources, and conditions before creating it.
Run and observe
Use run now for the first execution, then check the run history and delivered result.
Adjust with versions
Edit the schedule or sources as a new version; pause or resume whenever the need changes.
03 · Checklist
What a healthy automation shows
| Signal | What it means | What to do |
|---|---|---|
| Next run | The schedule is active and computed. | No action needed. |
| Run history | Past executions and their outputs are recorded. | Review outputs for accuracy. |
| Delivery record | Results reached your in-app inbox. | Read and file the result. |
| Audit events | Configuration changes are versioned. | Check who changed what, and when. |
| Paused | The task will not run until resumed. | Resume or delete if no longer needed. |
04 · Limitations
Availability boundaries to respect
This capability depends on the deployment operator enabling the task control plane; where it is not enabled, automations cannot be created or run. Current public claims cover in-app result tracking, not real email delivery. The automation console is read-only offline, so pausing, resuming, and editing require a connection. Undo promises for classifications do not extend to every automation operation. Billing and plan availability are listed on Pricing.
05 · Echo Notes practice
Automate one weekly check
Pick a single public page you check every week and create one automation for it with a weekly schedule. After the first run, read the delivered result and the audit entry, then decide whether the schedule needs tuning. Keep daily writing in offline Markdown notes and periodic tidying in AI organization so automations handle only the recurring part.
FAQ
Cloud automation questions
Do automations run when my browser is closed?
Yes, in enabled deployments the server runs active tasks independently of the open browser.
Are automations available everywhere?
No. They depend on the deployment operator enabling the task control plane.
Can I manage automations offline?
No. The automation console is read-only offline; pause, resume, and edits need a connection.
How do I know what a task did?
Each task records run history, in-app delivery, and audit events with versioned configuration changes.
Do automations send email?
Current public claims cover in-app result tracking, not real email delivery.