Docs › Duties & Automation

Duties & Scheduling

A duty is a recurring job you assign to one of your CloudAxis specialists — it runs on a schedule you set, and the results land wherever you choose: a chat thread, workspace files, a notification, email, or WhatsApp.

What a duty is

Every specialist on your team can hold one or more duties. A duty bundles three things: the instructions for what to do, the specialist that does it, and when it runs. Once saved, the duty runs unattended — you don't have to open a chat and ask again each time.

Typical duties: check a shared inbox every morning and summarize new orders, watch a competitor's pricing page daily, post a weekly report into a thread, or refresh a spreadsheet every few hours during business hours.

Schedules, in plain words

You set the schedule in plain language or a specific time — "every weekday at 9am," "every 2 hours," "every 15 minutes." CloudAxis turns this into the underlying timing for you.

  • Minimum interval — a duty can run at most once every 15 minutes. Nothing can be scheduled faster than that, even for urgent-sounding work — use an email trigger or webhook instead if you need a faster reaction.
  • Time zone — schedules run in the time zone you set for the duty, so "9am" means your 9am, not a server's.
  • No schedule at all — a duty doesn't have to recur; see manual duties for ones that only run when something explicitly starts them.

Run now

Every duty has a Run now button. Use it to test a new duty right after creating it, to re-run after fixing a mistake, or to get a result on demand without waiting for the next scheduled time. Run now doesn't change the duty's regular schedule.

Pausing and editing

Pause a duty to stop it firing without deleting it — useful while you're traveling, waiting on a credential to reconnect, or debugging a run that keeps failing. A paused duty keeps its instructions, schedule, and history; resume it and it picks back up on the same schedule.

Editing a duty lets you change its instructions, schedule, delivery destination, or autonomy setting at any time. Changes apply from the next run onward — nothing about its history is lost.

Where results are delivered

You choose where each duty's output goes, and can combine more than one destination:

  • Chat thread — the run posts into a specific conversation, alongside the rest of that work.
  • Workspace files — the specialist writes or updates a file in its cloud desktop, useful for logs, reports, or anything you want to open later.
  • Notifications — a short summary lands in your notification inbox even if you don't have a thread open.
  • Email or WhatsApp — once connected in the Launchpad, results can also be sent straight to your inbox or phone.

Duty slots are account-wide

The number of duties you can run is set by your plan, not per specialist — every duty across your whole team counts against the same pool. The Free plan includes 2 scheduled duties; higher plans include more. See pricing for current limits, or delete an old duty to free up a slot before adding a new one.

Tip: if a duty needs to react faster than every 15 minutes, pair a light backstop schedule with an email trigger or webhook so nothing depends on a single trigger path.