AGENT ATLASa field guide to agent workflows
Back to Automation & triggers
Automation & triggers

Scheduled triggers

Run the workflow on a clock — hourly, daily, weekly.

1 agentStarter

How it works

  1. 1Define the schedule — a cron expression or interval.
  2. 2On each tick, fetch the current inputs the job needs.
  3. 3Run the agent workflow.
  4. 4Deliver output to its destination and log the run.

Use it when

Recurring jobs with no human in the loop — a morning digest, a nightly cleanup, a weekly report.

Reach for something else when

The work is genuinely event-driven (use a webhook) or needs fresh human input each time.

Where you stay in the loop

No human runs each tick, so your job is upfront: define the schedule and own the logs. An unattended job still needs an accountable human and an alert when it fails.

In the wild

Every weekday at 8am, an agent pulls yesterday's metrics and posts a summary to a channel.

Hand this to your agent

Help me design a scheduled automation.

Ask me: what should run, how often, what inputs it needs at run time, and
where output should go.

Then output: (1) a plain-English description of the job, (2) a cron
expression for the schedule, (3) the step-by-step the agent runs each tick,
(4) what to log.

Job idea: <...>

Replace the <…> placeholders, paste it into your agent, and it'll scaffold the workflow with you.