Jobs vs triggers — which one you want

Knowing in one sentence whether the automation you're imagining is a schedule or a reaction.

The steps

If it starts with "every…", it's a job — Every Monday, every morning, every end of month — a **job** runs on a clock. Reports, digests, recurring drafts. You create one by asking in chat ("do this every Friday") and manage it on the employee's **Agenda** tab.
If it starts with "when…", it's a trigger — When a form is submitted, when a webhook fires, when a payment fails — a **trigger** runs on an event. You create and manage them at **Triggers**, and each one gives you a URL the outside world can call.
Chain them instead of enlarging them — The reliable pattern is small pieces: a trigger that captures and qualifies, a job that summarizes the week's captures. One giant automation that does everything is the fragile version of two small ones that each do one thing.

You can classify any "could this be automatic?" idea in five seconds.