> ## Documentation Index
> Fetch the complete documentation index at: https://prakan-saengjan-ep18.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Automate repetitive tasks with Automations

> Build trigger-action rules to automate status changes, notifications, and handoffs in Mintlify Starter Kit. Save time and reduce manual errors.

Automations let you define rules that run automatically when specific events occur. Each automation has a trigger, such as a status change or due date approaching, and one or more actions, such as moving a task, notifying a channel, or assigning a member. By removing manual steps, you keep workflows consistent and free your team to focus on higher-value work.

Common use cases include escalating overdue tasks to a manager, assigning new requests to the on-call teammate, posting project updates to a Slack channel, and archiving completed work after a set number of days.

<Steps>
  <Step title="Open the Automations panel">
    Navigate to your workspace and click **Automations** in the left sidebar.
  </Step>

  <Step title="Choose a trigger">
    Click **New Automation** and select a trigger event, such as **Task status changed to Done** or **Due date is tomorrow**.
  </Step>

  <Step title="Add conditions (optional)">
    Refine when the rule runs by adding conditions. For example, only trigger if the task is in the **Engineering** project or has the **Urgent** label.
  </Step>

  <Step title="Define actions">
    Pick one or more actions to perform. You can move the task to another stage, assign it to a specific user, send an in-app notification, or post to an integrated channel.
  </Step>

  <Step title="Save and enable">
    Name your automation, toggle it on, and click **Save**. The rule begins monitoring events immediately.
  </Step>
</Steps>

<Note>
  Automations are available on the Team plan and above. Free plans can preview and create one automation in test mode. Upgrade to enable unlimited live automations.
</Note>

Once enabled, you can review automation runs in the **History** tab to see which rules fired, when they ran, and whether any actions failed.