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

# Task triggers

> Choose when a task runs: by hand, on a schedule, after a task, or after an app event.

A trigger starts a task. Choose the simplest trigger that fits the job, then use **Run now** to test the task before you
turn on automatic runs.

## Manual

A manual task runs only when someone selects **Run now**. Use this for:

* early testing;
* work that needs a human decision before it starts;
* repeat jobs that happen at irregular times.

Manual tasks are the safest place to begin because a person controls every run.

## Schedule

A scheduled task runs at a time you set. You can create one-time or repeating schedules, including hourly, daily,
weekly, monthly, yearly, and custom intervals.

<Steps>
  <Step title="Open the task trigger">Create or edit a task. Under **Trigger**, choose **Select a trigger**.</Step>
  <Step title="Choose Schedule">Select **Schedule** in the trigger picker.</Step>

  <Step title="Set when it runs">
    Choose the frequency, time, and time zone. For a repeating task, you can also choose a start date and when it should
    end.
  </Step>

  <Step title="Add the trigger">
    Review the next occurrence shown by Mantle, then add the trigger. Select **Run now** once before making the task
    active.
  </Step>
</Steps>

Check the selected time zone. A schedule that looks correct in one time zone may run on a different local date for
another teammate.

Good uses include morning digests, weekly summaries, and regular checks. Avoid a very frequent schedule unless the
result changes often enough to justify the extra activity and credit use.

## On Complete

An On Complete trigger starts after another task finishes. Use it to split a longer workflow into clear stages, such as:

1. collect recent feedback;
2. summarize the themes;
3. post a short leadership update.

Each task should have one clear job and a result the next task can understand. If an earlier step fails, check the run
history before restarting the chain.

## Connected-app event

An app trigger starts when a supported event happens in a connected app. Examples can include a new issue, email,
message, or payment event, depending on the integration.

<Steps>
  <Step title="Connect the app">Go to **Settings → Integrations** and complete the connection.</Step>
  <Step title="Choose the event">Select the integration and event while editing the task trigger.</Step>
  <Step title="Add filters when available">Limit the task to the team, project, account, or event that matters.</Step>

  <Step title="Test with a safe event">
    Confirm that the correct task starts once and posts to the expected channel.
  </Step>
</Steps>

Not every integration supports triggers. Its guide shows whether it offers agent tools, triggers, or both.

## Choose safely

| If the job... | Start with... |
| - | - |
| needs approval each time | Manual |
| should happen at a regular time | Schedule |
| is one step in a larger workflow | On Complete |
| should react to another app | Connected-app event |

<Note>
  Scheduled tasks and some automatic triggers require a paid plan. Trigger availability also depends on the connected
  app and the permissions granted to it. Automatic runs use the task owner's credits.
</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.