Tasks & triggers

An automation in Aplite is a task: a small markdown file in your workspace holding plain-language instructions and a few fields — when to run, where to deliver. The agent reads the file and does the work. Changing the automation is editing a sentence, not re-wiring a graph, and every run leaves a transcript you can open.

Schedules

A task with a schedule field runs on its own — daily 08:00, every Monday, once an hour. The schedule is a plain property on the task, visible and editable like everything else on it.

Triggers

A trigger starts a task from outside: it gives you a webhook URL, and a call to that URL fires the run. Payloads are signature-checked, so a form service, a payment provider or your own script can start work in your workspace without being able to fake it.

Chains

Several tasks can be linked into a chain — steps run in sequence or in parallel, and each next step can depend on how the previous one ended: continue on success, branch on failure.

Armed and disarmed

Routines installed from Skills arrive as a draft: the schedule is seeded, the trigger is off, and nothing runs until you arm it. Disarm it later and it is a draft again — no cancellation flow, nothing to uninstall.

Where results land

Every task carries a delivery field: Telegram, email, chat, or a document in your workspace. It is a property on the task, not a plan tier — switch it whenever.

Anything a run wants to change on your behalf — a file edit, a draft that would leave the workspace — goes through Approvals first.