> ## Documentation Index
> Fetch the complete documentation index at: https://help.autoady.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Create a scheduled task

> Draft a recurring check, review a validated preview, then approve activation.

**Scheduled tasks** runs recurring work with a chosen account scope, schedule, and delivery destination. A draft does not run until you approve its validated preview.

<Note>Scheduled ad tasks read and report; they do not propose or automatically apply ad changes. Review an ad change through its normal approval workflow. Some task templates can create separately scoped repository or project artifacts.</Note>

## Prepare the task

You need access to the intended accounts and a supported delivery destination. Decide what the task should read or produce, how often it should run, and which results the recipient needs. Review any credit requirement and destination limits shown in the preview.

## Draft, preview, approve

1. Open [Scheduled tasks](https://www.autoady.io/automations/routines).
2. Choose **Create task**, or **Browse templates** for a starting point. A template still needs your account context and review.
3. Give the task a clear name and instructions. Specify the accounts, objective, and evidence you expect; avoid a broad instruction such as “optimize everything.”
4. Set the supported schedule and timezone. Check the chosen delivery destination and its connection state. Use the provided connection settings if it needs setup.
5. Choose **Save draft** if you need to finish later, or **Preview task** to validate it.
6. Inspect the preview's scope, next runs, delivery, permissions, costs, and blockers. Approve the reviewed revision only when these agree with your intent.

## Confirm activation and delivery

Return to the task list and check **Schedule**, **Next run**, and **Last result**. After a run, open its result and delivery information. A successful task computation does not alone prove that its recipient received the report.

Use the available pause control to stop future runs. Before resuming, confirm that accounts, instructions, and destination still match the task you approved. Use a manual run only where the product enables it, and inspect its result before repeating it.

## Resolve blockers

If validation finds a missing account, expired connection, destination issue, or unsupported work, correct the blocker and generate a new preview. Changed instructions or scope need a reviewed revision; an old approval is not blanket permission for later edits.

If a provider outcome is unknown, inspect the run and recovery action first. A delivery retry is different from rerunning the entire task and should be chosen accordingly.

For permissions governing eligible automatic Meta ad changes, see [Autopilot](/automation/autopilot). Connecting Slack or Telegram for delivery is also separate from [connecting an external tool-using agent](/agent/connect).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.