Create a scheduled task

A scheduled task is a job you describe once and Titan AI runs on a schedule. It reads your store, does the work, and reports what it found. If you let it, it can also act on what it finds.

Open Scheduled Tasks from the sidebar.

Start a task

Press New Task at the top of the Scheduled Tasks page. The form opens empty, and you fill it in as described below.

To start from one of the 11 templates instead, press Browse templates next to New Task. It is there whether or not you already have tasks. Type in the search box at the top to narrow the list by name. Press Add on the template you want, and the form opens with its title, brief and schedule filled in. Choose the store, then create it. A template one of your tasks already uses is marked In use, including when that task is paused, and you can still add it again.

Until you have a task, the page also offers two quicker ways in. Both end at the same form.

1. 1

   Describe it in plain English

   Type what you want into the box, for example "every Monday at 7, clean up my wasted search-term spend", then press Draft or Enter. Titan AI fills the form in for you and you correct anything it got wrong.

2. 2

   Start from a template

   Press one of the six starters under the box. The form opens filled in from it.

Screenshot pending

The 11 templates

These are the 11 templates in Browse templates, in the order it lists them.

The six starters under the box are a separate, shorter set: Morning Store Pulse, Biweekly Store Operating Review, Margin & Fee Leak Audit, Inventory Cover Guard, PPC Efficiency Trim, and Returns & Quality Signal.

A template is a starting point, not a fixed thing. Everything in it is editable before you schedule it, and afterwards.

Fill in the form

1. 1

   Title

   What this task is called. The field prompts you to Name this scheduled task.

2. 2

   Task Details

   The brief. Everything lives here: the workflow step by step and what to produce. The result reaches you in the app, on the task itself. If you ask for a file, such as a PDF report or a spreadsheet, it appears on the run as a download. A scheduled task cannot email it to you or post it anywhere else, so asking it to does not change where it goes. Be specific. This is the difference between a useful report and a vague one.

   In the task form, typing / shows your skills to pick from.

3. 3

   Attachments

   Optional. The file itself is not uploaded, so Titan AI cannot read it while the task runs. Put anything it should work against, such as a cost sheet or a target list, into Task Details instead.

4. 4

   Store

   Which Amazon store the task runs against. Titan AI's data tools are pinned to that seller, so a task cannot wander into another store.

5. 5

   Frequency and Time

   How often it fires, and at what local time. See below.

6. 6

   Actions

   Whether the task may change your account on its own. Read the next section before you leave this alone.

Press Schedule Task to save it.

Frequency options

Time is the local time of day the task is due, in your account timezone, which is set in Settings. If you have not set it, set it before you rely on a morning task arriving in the morning.

A task starts at that time or up to five minutes after it. Each task keeps its own delay, so it starts at the same minute every time. Pressing Run on a task starts it straight away.

Decide what the task may change

This is the setting that matters most, so it gets its own section.

The Actions row has a toggle labelled auto-approve actions.

Note what "off" does and does not mean. It does not queue the actions for you to approve later, and it does not hold them anywhere. It reports them and discards them. If you want a change applied after reading a report, you make it yourself or you ask for it in chat. The Needs approval card on the Scheduled Tasks page counts the changes your runs held back this way in the last 30 days, and lists those runs so you can open them. It has no button that applies them, and opening a run does not take it off the card: a run leaves it after 30 days.

A sensible way to start on any task that can write: leave auto-approve off for the first few runs, read what it says it would have done, and only turn it on once you agree with its judgement.

Off is not a full dry run, though. It holds back the changes the task proposes, which is nearly all of them, but one thing never goes through the approval step at all and so still happens on an off run: marking alerts as read. What does not stop to ask covers it.

Find your way around the page

The top of the Scheduled Tasks page counts your runs in the last 30 days, and how many actions those runs applied to your account.

Today is a line from 06:00 to 06:00, in your account timezone, with a dot for each task that runs today. A task that runs between 00:00 and 06:00 sits at the right-hand end, and its dot shows this morning's run. A dot fills in with the result once the task has run: Success, Needs review or Failed. A hollow dot has not run yet. Point at a dot to see the task and its time, and press it to open the task. Under the line, the page says how many of today's runs are done and when the next one is. A run you start yourself does not fill a dot.

Four cards sit under it:

Press a run in any card to open its task.

My Tasks lists every task: active ones in the order they run next, then inactive ones, then finished one-time tasks, last. A one-time task that has run reads Inactive, with the date it ran. Each row shows the task's schedule, its store if it has one, and its project if it is in one. If your tasks are split between projects, or between a project and no project, use Filter to show one project's tasks; Scheduled tasks shows the ones in no project. Two buttons beside it switch between the list and the calendar, and the calendar has a week and a month view.

Run, edit and manage

Each row in My Tasks has a toggle that activates or deactivates the task. A deactivated task stays as you wrote it and stops firing.

Open a task to read what it actually did. Every run is listed down the side with how long it took, and opening one shows the same step-by-step working you get in chat, ending in Continue in Chat if you want to pick the run up and dig in. Any file the run made is shown there as a download, and only you can download it.

The step-by-step working is kept for each task's five most recent runs, and for any run in its first 30 days. After that, an older run's working can be cleared. The run keeps its place in the list, its status and its summary, and its summary is shown where the working was, but Continue in Chat is no longer available for it, and the files that run made are no longer offered for download. Save a file you want to keep. A run that needs your review keeps its working for 90 days, and a run you have already continued in chat keeps it for good.

From there you can also Run it immediately, Edit it, or Delete it. Deleting removes the task and its run history, and cannot be undone.

Change the instructions from chat, and bring an earlier version back

You can change a task's instructions from any chat. Ask Titan AI to change one rule in a task, and it reads the task's current instructions first, then proposes only that change: the approval card shows the lines it removes and the lines it adds, and every other rule stays as it was. If the instructions changed somewhere else after Titan AI read them, in another tab or from another chat, your approval does not save the edit. Titan AI tells you so and asks before it tries again. The Edit panel on the task page has the same check: a save over instructions that changed since you opened the panel is refused, with a prompt to reload and make your change again.

Every version of the instructions is kept. On the task page, Instructions history lists each saved version, with when it was saved and whether it came from the task page, a chat or a restore. Open one to see what changed against the current instructions, and press Restore this version to bring it back; the restore itself becomes the newest version, so nothing is lost. If the instructions changed while the dialog was open, the restore is refused the same way as a save. In chat, ask Titan AI to show a task's earlier versions or to restore one; the restore goes through the usual approval card. The first change you make to a task that existed before history was kept also records its instructions as they were, as an Earlier entry, so that version can be restored too.

The instructions and the schedule must agree on how often the task runs. A change that would make them disagree, for example instructions that say "every two weeks" on a weekly task, is refused, and Titan AI offers to change nothing. A change that keeps a mismatch the task already had saves, and Titan AI tells you that the two still disagree, so you can fix it when you want.