> For the complete documentation index, see [llms.txt](https://themochi-app.gitbook.io/mochi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://themochi-app.gitbook.io/mochi-docs/feature-and-settings/automations.md).

# Automations

Automations let you create rules that handle repetitive tasks automatically. Available to Creators and Managers only.

## What Automations Can Do

Set up workflows that trigger based on events in your pipeline. Automations handle things like:

* Follow-up reminders when leads go quiet
* Automatic lead assignment based on criteria
* Stage transitions based on actions
* Notification rules for your team

## Managing Automations

### Creating an Automation

{% stepper %}
{% step %}

### Go to Automations

Go to **Automations** from the sidebar.
{% endstep %}

{% step %}

### Create Automation

Click **Create Automation**.
{% endstep %}

{% step %}

### Define Trigger

Define your trigger (what starts the automation).
{% endstep %}

{% step %}

### Set Action

Set the action (what happens when triggered).
{% endstep %}

{% step %}

### Save and Activate

Save and activate.
{% endstep %}
{% endstepper %}

### Organizing with Folders

As you build more automations, organize them into folders to keep things manageable. Create folders for different workflow types — follow-ups, assignments, notifications, etc.

### Enabling/Disabling

Toggle automations on or off without deleting them. Useful for seasonal campaigns or testing new workflows.

## Follow-Ups

The follow-up system helps ensure no lead falls through the cracks. Schedule follow-ups for specific leads, and Mochi will remind the assigned team member when it's time to re-engage.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://themochi-app.gitbook.io/mochi-docs/feature-and-settings/automations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.