Scheduled tasks

“Scheduled tasks” (internally called cron jobs) are how your agent does things automatically without you asking. If your agent can do something in a one-off conversation, it can do it on a schedule.

Examples

• Daily: morning briefings, inbox triage, competitor monitoring, news digests
• Weekly: weekly report to your team, LinkedIn content, metrics review
• Hourly: check for specific urgent emails, monitor a rapidly-changing situation
• Custom: “every first of the month,” “every Friday at 4pm,” “every 15 minutes during business hours”

Creating a scheduled task

The easy way — plain English

Just describe what you want to your agent:

“Every weekday at 7am, send me a morning briefing. Every Monday at 5pm, draft a weekly update for LinkedIn. Every 1st of the month, calculate my credit usage and warn me if I’m trending over budget.”

Your agent creates the cron jobs automatically, confirms the schedules, and previews the first run.

The explicit way — Scheduler tab

From the dashboard, go to Scheduler in the sidebar. Click New scheduled task. Fill in:

• Name — short description
• Schedule — pick from presets (daily, weekly, hourly) or enter a cron expression
• Timezone — defaults to your account timezone
• Prompt — what you want your agent to do each run
• Delivery — how the result reaches you (push, email, Telegram, Discord, Slack, save to workspace)
• Trust level — does the result need your approval before it acts on anything?

Cron expressions

If the presets don’t cover what you need, you can enter a raw cron expression. The format is minute hour day-of-month month day-of-week. Examples:

Expression	What it means
0 7 * * 1-5	7:00 AM weekdays
30 9 * * 1	9:30 AM Mondays only
*/30 9-17 * * 1-5	Every 30 min, 9am-5pm, weekdays
0 0 1 * *	Midnight on the 1st of every month
0 */2 * * *	Every 2 hours, on the hour

Your agent also understands plain English and converts it. “Every weekday at 7am” → 0 7 * * 1-5. You don’t have to memorize the syntax.

Plan limits

Tier	Max scheduled tasks
Trial	5
Standard	10
Pro	25

Each scheduled task counts as one slot regardless of how often it runs. “Every 30 minutes” is still one cron job.

Paused jobs still count against your limit until you delete them.

Output and delivery

Every cron run produces output. What happens to that output depends on the job:

• Silent runs — task completes, result stored in workspace, no interruption to you. Example: daily backup of your metrics file.
• Delivered runs — result pushed to your chosen channel. Example: morning briefing to Telegram.
• Approval-requiring runs — result goes into your Approvals queue. Example: scheduled social post that needs your approval before publishing.

You configure this per-job.

Managing runs and history

From Scheduler → [your task] → History, you can see:

• Every past run (success, failure, or skipped)
• The full output of each run
• The time the run took
• The tokens and credits it consumed

If something went wrong, you can drill into the specific run and see the error.

Pausing and editing

Scheduled tasks can be:

• Paused (temporarily stop running, resume later)
• Edited (change the schedule, the prompt, the delivery)
• Duplicated (create a variant without re-typing everything)
• Deleted (gone forever — also removes history)

When things fail

Your agent doesn’t panic over failures. If a cron run fails:

1. It’s logged in the task history with the error
2. You get a notification (unless you’ve turned that off for this task)
3. The next scheduled run tries again — no exponential backoff, just the next slot
4. If 3 runs fail in a row, your agent will pause the task and flag it for you to look at

Common failure causes: network issues, provider outages (IMAP down, etc.), token limits, a tool change breaking something.

Credit and token usage

Scheduled tasks use:

• Token credits for the LLM calls during the run
• Search credits if the run includes web search
• Social post quota if it posts to social media

Browsing the web inside a scheduled task is free — both the sandbox browser and the Browser Control extension are no-cost. Heavy cron jobs (daily deep research, hourly monitoring, etc.) can still eat token credits quickly. Your agent will warn you in your morning briefing if your credit burn is trending over budget for your plan.

Stopping everything temporarily

If you want to pause all scheduled tasks at once (going on vacation, for example), go to Scheduler → Global pause. Everything stops until you unpause. No data is lost — runs you missed are simply skipped.

Don’t build 50 cron jobs on day one

Start with 2-3 scheduled tasks and see what actually adds value. Most users find that morning briefings + weekly reports + one competitor monitor covers 80% of their needs. You can always add more.