> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/general/crm/crm-automations/crm-automations-in-crm-with-the-condition-opportunity-value.md).

# CRM - Automations in CRM with the condition "Opportunity Value"

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FvXXYCMXp0lw5OMfihGtl%2Fcomposicao-isometrica-com-chatbot-no-laptop-pessoas-sorrisos-felizes_1284-63053.png?alt=media&amp;token=c503b8d4-e05b-44ab-9b52-06e98d4dd804" alt=""><figcaption></figcaption></figure>

Using the condition "The value in the opportunity field is..." in your CRM can significantly improve the efficiency of your sales operations, ensuring that opportunities are handled according to their revenue potential.

Go to the **CRM**, and click on **Automations**;

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FOIfwc72dGzjOrZPUFBiR%2Fimage.png?alt=media&amp;token=333e7681-ba21-4eb5-bfa5-4cc52e2bd6a2" alt=""><figcaption></figcaption></figure>

Define the **title** and the **condition**, which, in this case, will be '*The opportunity value is...*'.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FulILB2uxVWMAVuYLTqSo%2Fimage.png?alt=media&amp;token=56e85698-019e-4ca8-9be2-e3a0b15ff73c" alt=""><figcaption></figcaption></figure>

Define the values;

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FVbqkcvOfKTAV86lHm1o2%2Fimage.png?alt=media&amp;token=e8e3bdeb-3f1d-44a9-becf-46922c7bb4a5" alt=""><figcaption></figcaption></figure>

Configure the **condition** that must be met for the **automation to be triggered**.&#x20;

Determine what you want the CRM to do when the condition is met.

In the example, we will use '**Change opportunity owner**. This will cause the opportunity with the specified value to be routed to specific members of the sales team.

*But you can define other conditions, such as:*

**Change opportunity funnel / stage:** Automatically move sales opportunities to different funnel stages based on their value.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FvQPxt0Hxz5wUMOp38Z7W%2Fimage.png?alt=media&amp;token=8264a136-bed1-486f-b773-012473a3ae16" alt=""><figcaption></figcaption></figure>

Define the **owner type,** and then click Save.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FJsR48eQ14b3cPatjMslW%2Fimage.png?alt=media&amp;token=90596be7-b48c-4255-8be1-73bdd6f89054" alt=""><figcaption></figcaption></figure>

**Simple**: We will create the opportunity with the selected owner.&#x20;

**Random from the list**: We will create the opportunity with a random owner from the provided list.&#x20;

**With the fewest opportunities from the list**: We will create the opportunity with the owner from the provided list who has the fewest opportunities.&#x20;

**Random from the department**: We will create the opportunity with a random owner who is in one of the selected departments.&#x20;

**With the fewest attendances from the department**: We will create the opportunity with the owner who has the fewest attendances across all selected departments.

**Use the lead owner**: Creates the opportunity with the lead owner. If the lead does not have an owner, a random user will be selected based on the lead's access permissions.

After saving your automation, click on the '<mark style="color:green;">**Play**</mark>' icon to activate it.&#x20;

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FhCmHqfKt4bzjPzJWONXl%2Fimage.png?alt=media&amp;token=5215371a-1b84-4a7d-b524-223515704b97" alt=""><figcaption></figcaption></figure>

*With the automation configured, whenever the value of an opportunity reaches the specified threshold, the owner will be changed automatically. This allows specific salespeople to handle opportunities matching those values.*

<mark style="color:purple;">**See similar articles:**</mark>

{% content-ref url="/pages/80e6c8e4d3ddf5ed225a8e8dff4239bc17b5bde0" %}
[CRM - Automations](/en/topics/general/crm/crm-automations.md)
{% endcontent-ref %}

{% content-ref url="/pages/4a1c7e56fdf5b057a091070b52862d8b0cbe813f" %}
[CRM](/en/topics/general/crm.md)
{% endcontent-ref %}


---

# 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://docs.sprinthub.com/en/topics/general/crm/crm-automations/crm-automations-in-crm-with-the-condition-opportunity-value.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.
