Core capabilities

Automations

Scheduled or condition-driven runs of a chosen agent on a fixed task.

What it is

Ottermind Automations are automated tasks that let a specified Agent run a fixed task at a scheduled time or under set conditions. Think of an Automation as a scheduled or recurring Agent task. By creating an Automation, you let an Agent run reports, workflows, or other tasks on a schedule, reduce repeated operations, and produce results at a consistent cadence.

With Automations, you can

Schedule tasks to run automatically at a specified time.
Reuse stable tasks as repeatable workflows.
Control the execution Agent, device, start rule, and end rule.
Manage status, last run, next run, and pause or troubleshoot tasks.

Automations are suitable for tasks with clear schedules, stable input sources, and clear output standards. They are not suitable for highly ad hoc tasks, tasks requiring human judgment, or tasks involving sensitive data with unclear permissions.

Manage your automations

In the left sidebar of Ottermind, select Automations to view automated tasks. Search tasks and filter by All, Active, Running, Paused, or Error.

Status	Meaning
Active	The task is enabled and will run on schedule.
Running	The task is currently running.
Paused	The task is paused and will not run automatically.
Error	The task failed and requires configuration or input checks.

Create an automation

Click New automation to create an automated task. Fill in the name, choose an Agent and Device, describe what the task should do, then set the run time and end rule.

Field	What goes here
Name	Task name used to identify it in the list.
Agent	The Agent that executes the task.
Device	The device or environment where the task runs.
What should this automation do?	Task instructions. Include the goal, input, output, and restrictions.
Choose when this automation should run	Run mode and time.
Starts	When the task becomes active.
When should this automation end?	When the task should stop.

Write clear task instructions

The task instructions determine what the Agent does each time it runs. Recommended details:

What needs to be completed.
Which data or sources to use.
What output format is expected.
Whether filtering, sorting, summarizing, or sending is needed.
What the task must not do.

Good

Summarize important updates from specified information sources every day, output in Markdown, keep source links, and list items that need human attention at the end.

Bad

Check what is new every day.

Set the run mode

Runs on a fixed cycle, such as daily or weekly.

When setting the time, confirm that the time zone, frequency, and business rhythm match your needs. After creation, you can view Runs, Last run, and Next run in the list.

Set start and end rules

Starts determines when the task becomes active:

Option	Effect
Default	The task waits for the next scheduled trigger.
Immediately	The task runs right after creation.
Next run at	The task starts from the next scheduled time.

End rule options:

Option	Effect
Never	Keeps running until manually paused or deleted.
After	Stops after a specified number of runs.
On	Stops after a specified date.

For temporary monitoring tasks, set an end rule to avoid unnecessary long-term cost or data access.

View results and status

After creation, the Automation appears in the list. The card shows the execution Agent, type, status, run rule, last run, and next run time. To stop the task temporarily, click Pause. If the task is abnormal, first check whether the status is Error, then check the Agent, Device, task instructions, time settings, and input sources.

Manage automation actions

On an Automation card, click Pause to pause the task. After pausing, the task will not run automatically on schedule. To continue running it, click Resume.

Click the more menu on the right for these actions:

Edit — change the task name, Agent, Device, task instructions, run time, and end rule.
Duplicate — create a copy of the current Automation. Review the copied configuration before enabling it.
View runs — view the run history of this Automation.
Delete — delete the Automation. After deletion, the task will no longer run.

Usage notes

Automations trigger tasks automatically

After an Automation is created, it runs automatically according to its settings. It does not require manual confirmation each time. Make sure the task instructions, permission scope, and output destination are clear.

Review time settings

Before creating a scheduled task, confirm the run time, frequency, start mode, and end rule. For tasks involving time zones, holidays, trading days, or workdays, write the rule clearly in the task instructions.

Permissions and data security

Automations may continuously read files, access external services, or generate results. Do not let automated tasks continuously process unauthorized data, sensitive files, passwords, keys, customer data, contracts, financial data, or personal identity information.

FAQ

Why didn't the Automation run immediately after creation?

It may be set to Default, which waits until the next scheduled time. If you need it to run right away, choose Immediately.

Why did the Automation fail?

The Agent configuration may be unsuitable, the Device may be unavailable, the input source may be inaccessible, the task instructions may be unclear, or the required Skill may not be bound.

When should I set an end rule?

Set an end rule for temporary monitoring, phase-based reports, event tracking, and tasks with budget limits.