Skip to main content
Agents & Tasks

Tasks: run an agent job automatically

Save a repeatable job for an agent, choose when it runs, and post the result to a channel.

Written By Katja Danilina

Last updated About 1 month ago

A task is a repeatable job for an agent. It tells Mantle what the agent should do, when it should run, and which channel should receive the result. Examples include a morning email digest, a weekly customer-feedback summary, or a review that starts when a new issue is created in a connected app.

Create a task

  1. Select Tasks in the left rail, then the + beside Tasks. You can also open the Tasks section of an agent.

  2. Name the task after its result, such as “Post overnight email digest”.

  3. Add instructions: the time range, sources, rules, and output format. These are used together with the agent's own instructions.

  4. Choose the agent with the right model, knowledge, and tools.

  5. Under Trigger, choose Select a trigger and pick Manual, Schedule, On Complete, or an event from a connected app. See Task triggers.

  6. Pick the output channel where people should review the result. For tasks that run often, use a channel made for automated updates.

  7. Select Create Task, then Run now and review the first result. Turn the task Active only when it's ready to run on its own.

Write instructions that can run alone

An automated run can't ask you what you meant. Include:

  • the exact time period or event to process;

  • which connected account or source matters;

  • what to include and exclude;

  • the length and structure of the output;

  • what to post when there's nothing useful to report;

  • when to report an error instead of guessing.

For example: “Find email received between 18:00 yesterday and 08:00 today. Include only messages that need a reply or decision. Group them by urgency, give each a one-sentence summary, and include a link to the email. If none need action, post: No overnight email needs action.”

Run, pause, and review

  • Run now starts an immediate test or one-off run.

  • The Active switch lets automatic triggers start the task.

  • The task history shows recent runs and whether they completed or failed.

  • Pause a task while you change its agent, instructions, connected apps, or output channel.

A task can complete successfully and still produce an unhelpful summary, so read several real results after launch.

Credits and plans

Every run uses the task owner's AI credits, including runs started by a schedule or an app event. Manual tasks are available on every plan; scheduled and event-based tasks need a paid plan (Core, Plus, Max, or Enterprise).

When a task pauses or fails

A background task needs access to every connected app its agent uses. If a connection expires or is removed, the task can pause or fail instead of acting with incomplete access. Reconnect the app, review the task, and run it manually before turning automation back on. Events that happened while the connection was down may not run again automatically.

A task also pauses if its owner leaves the organization or no longer has a plan that supports its trigger. An admin can reassign it, check its connections, and test it before activating it again.

Start with read-only or low-risk work. Before you let an agent send messages, update records, or create work in another app, test its instructions and limit its tools to exactly what it needs.

Full guide: https://docs.mantle.chat/features/tasks