> For AI agents: the complete documentation index is available at /en/llms.txt, the full documentation bundle is available at /en/llms-full.txt.

# Have an expert remind you or push an update

A scheduled task runs without you opening the composer. A daily news push, a water reminder, or a Friday status report is one row on the same page.

Open **Automation** in the sidebar. The page title is **Cron Jobs**. Pick the expert in the top-right before you add a task. The task belongs to that expert.


![Automation](/images/en/ui-tasks.png "Automation")


![Create a scheduled task](/images/en/ui-task-create.png "Create scheduled task")

## Start from one of these

An empty list already offers three prompts. Open one and change the time or the wording:

- Every day at 14:00, write today’s action notes for your zodiac sign and send them to you.
- Every day at 14:00, remind you to drink water, starting today, and enable the task as soon as you create it.
- Every day, push the latest 10 tech stories, each with a short summary.

After a [channel](/en/guide/guides/im-channels.md) and a [connector](/en/guide/concepts/connectors.md) are working, swap in a work task. For example: every weekday at 9:00, check tomorrow’s Tencent Meeting schedule and send it to Feishu. Say who receives it and which chat it should land in.

## Create one


### Select the expert

Choose the expert in the top-right. The task belongs to that expert only.

### Create the job

Click **Create Job**. The name is required.

### Say when it runs and what it should do

The schedule can run once, on an interval, or on a cron expression. The prompt is the message sent to the expert, up to 2,000 characters.

### Choose the task type

**Agent (AI processes request)** lets the model read the prompt and reply. It can use that expert’s skills and connectors. **Text (send fixed message)** sends the text as written and does not call the model.

### Execute it once now

After you save, click **Execute Now** on that row. You see the result without waiting for the next scheduled time.

## Three ways to write the time

| Format          | Example                    | When to use it                                                                                                                                                                                                              |
| --------------- | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Cron expression | `0 9 * * *`                | A fixed clock time, for example 9:00 every day                                                                                                                                                                              |
| Interval        | `interval:30`              | Every 30 minutes from the moment you save                                                                                                                                                                                   |
| One-time        | `date:2025-01-15T09:00:00` | Runs once, then turns itself off. Success or failure both disable it. The row stays in the list. If Octop was down for more than 24 hours past that time and never ran, the status becomes `missed` and the job is disabled |

The list shows the schedule, type, prompt, last run time, and last status.

Turn on **Also notify me in the background** when a reminder should use a system notification after you leave this tab. The page then says reminders use system notifications while the tab is in the background. If the browser blocked notifications, allow them from the site settings in the address bar.


> **TIP**
> 
> To create, list, and run a job from the terminal, see [Channel and cron commands](/en/cli/channel-cron-commands.md#octop-cron).
> 



> **TIP**
> 
> Set `OCTOP_DEFAULT_TIMEZONE`, or add `"default_timezone"` to `config.json`, to choose the timezone used for cron expressions. Otherwise Octop uses the server’s system timezone.
> 

