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

# Creating tasks

> Describe the work once, in plain language

Tasks are created by **talking to your assistant** — in Console chat, over
text, on a call, wherever. There's no form to fill in. Say what you want
done, when (or on what event), and how you'd like to hear back; your
assistant sets it up with sensible defaults for anything you didn't specify,
asking a short question only when something essential is missing.

> **You:** Every Monday morning, pull the open Jira tickets, sort by
> priority, and email me the top ten.
>
> **Assistant:** Done — scheduled for Mondays at 8am. You'll get the email at
> your usual address, and the task is listed in the Tasks tab.

## Schedules

Say times the way you naturally would — your assistant turns them into a
proper schedule:

* **One-off** — "tomorrow at 9", "in two hours", "on the 30th".
* **Recurring** — "every morning at 8", "every 30 minutes", "Mondays and
  Wednesdays at noon", "the first of each month".
* **With an end** — "every day until the launch", "for the next four weeks".

Times use your assistant's timezone unless you say otherwise ("8am UK
time"). If a request is genuinely ambiguous, it asks rather than guessing.

## Triggers

Triggered tasks fire on **incoming events** — a message or email arriving on
any connected channel. You can scope them precisely:

* **By channel** — "when I get an email…", "when someone messages me on
  Slack…", "when a WhatsApp comes in…"
* **By sender** — "when *Alice* emails about invoices…", or the reverse:
  "ignore anything from the newsletter address".
* **Once or every time** — a trigger can fire once and retire, or re-arm
  after each run and keep watching.

### Test it

You don't have to wait for a real event to know a trigger works. Armed
triggered tasks have a **Test it** control in the Console that fires the task
immediately so you can watch it run — and the trigger stays armed for the
real thing afterwards.

## Changing and removing tasks

Managing tasks works the same way as creating them — just tell your
assistant:

* *"Move the morning rundown to 7:30."*
* *"Skip the weekly recap this Friday."*
* *"Cancel the inbox-check task."*

The Tasks tab is where you *see* everything; chat is where you *change*
everything.

## During onboarding

The onboarding checklist walks you through both kinds: **Create a scheduled
task** and **Create a triggerable task**. Each row starts a short
back-and-forth with your assistant, and the example chips beneath them — like
*"In two minutes, check my inbox and text me anything urgent"* — set up that
exact task with one click. The scheduled step even shows a countdown until
your assistant reaches out, so you see the whole loop close in real time.

<Tip>
  A great first task mirrors something you already do manually every day or
  week. If you'd normally check it, chase it, or compile it — describe that
  to your assistant once, and take it off your plate.
</Tip>