> For the complete documentation index, see [llms.txt](https://help.paintscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.paintscout.com/support/operations/automations.md).

# Automations

Set up workflow automations that move deals through pipeline stages after lead form, estimate, or invoice events.

Automations streamline your workflow by moving deals after real events. For example, move a deal when a lead form is submitted, an estimate is accepted, or an invoice is paid.

{% hint style="danger" %}
**Important:** this feature requires the paid **Operations add-on.**
{% endhint %}

***

## How to Create an Automation

1. Click the **person icon** in the top right and choose **Account Settings**
2. Go to the **Automations** section
3. Click the **+New Automation** button

   <figure><img src="https://231248629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPyUbJF1GXLjxdJqm89IQ%2Fuploads%2Fgit-blob-a799a2afc1942df0495d33dff0072597377bcf7c%2Fautomations-new-button.png?alt=media" alt=""><figcaption></figcaption></figure>
4. Select your trigger and action criteria.

   <figure><img src="https://231248629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPyUbJF1GXLjxdJqm89IQ%2Fuploads%2Fgit-blob-4c4548d19242f2003734b19bdb2f3dbd2afd3458%2FScreenshot%202026-04-29%20at%2010.51.02%E2%80%AFAM.png?alt=media" alt=""><figcaption></figcaption></figure>
5. Once saved, your automation will be enabled and you can rename it if you would like.

<figure><img src="https://231248629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPyUbJF1GXLjxdJqm89IQ%2Fuploads%2Fgit-blob-12e8dfb1ec67a54432d0cbe08ce8b404fd52c822%2F1645651555_a53db4d7ba92bc6ca2d1376bcdb7?alt=media" alt=""><figcaption></figcaption></figure>

***

## ⚠️ Troubleshooting

* **Deleting a deal stage used in an automation will break it.**\
  If an automation points to a stage that no longer exists, it won't run—and you'll need to update or remove it.

<figure><img src="https://231248629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPyUbJF1GXLjxdJqm89IQ%2Fuploads%2Fgit-blob-aa4a014744b350f921546e37a5b935063ee4e2d9%2F1645655978_8892ae3b7026c5abec8e38f04096?alt=media" alt=""><figcaption></figcaption></figure>

* **If a deal isn't moving:**
  * Make sure the automation is still active
  * Double-check that the trigger event occurred, such as a lead form submission
  * Confirm the destination stage still exists

&#x20;&#x20;

## Related articles

* [Operations Guide](/support/operations/crm/paintscout-operations-guide.md) — See how automations fit into the full Operations workflow
* [Operations FAQ](/support/operations/crm/crm-faq.md) — Find answers to common questions about deals, jobs, and calendars

## Related articles

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>PaintScout Operations Guide</strong></td><td>Overview of PaintScout Operations features including deals, sales events, jobs, tasks, contacts, companies, notes, tags, and automations.</td><td><a href="/support/operations/crm/paintscout-operations-guide.md">PaintScout Operations Guide</a></td></tr><tr><td><strong>Operations FAQ</strong></td><td>Answers to common Operations questions about deals, jobs, estimates, notes, tags, deal stages, and calendar management in PaintScout.</td><td><a href="/support/operations/crm/crm-faq.md">Operations FAQ</a></td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.paintscout.com/support/operations/automations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.