> 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/relate/automation-flows/automatic-selectors.md).

# Automatic Selectors

How to automatically detect support cases, tasks, and opportunities using Automatic Selectors.

## What are they?

Automatic Selectors are identifiers that allow the flow to recognize entities linked to the contact, such as Tasks, Opportunities, and Support Cases.

When you activate one of these selectors within an Automation Flow, specific triggers, conditions, and actions for that category become available. Normally, the flow operates only at the contact level, but that changes when a selector is enabled.

For example, when you activate the Support Case Automatic Selector and choose the option “use the contact's most recent case”, you are defining exactly which case the flow should consider. This is important to avoid ambiguity in situations where the same contact has more than one case at the same time, such as two cases in different WhatsApp accounts.

From there, actions such as “Transfer the case” start working within the flow. This makes it possible to automatically assign the case to SAC 360º users or even change its stage through the Automation Flow.

<div data-with-frame="true"><figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FP9sO6jBT7WWjoiqNPqN4%2Fimage.png?alt=media&amp;token=a6c3f168-1655-4b13-b581-5cbde49b96a8" alt=""><figcaption><p><em>Automatic Selectors, on the 'Edit' screen of the Automation Flow.</em></p></figcaption></figure></div>

<div data-with-frame="true"><figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FQdTMNgEmnA3uxsqEREFf%2FSem%20t%C3%ADtulo.png?alt=media&amp;token=285049fb-d4e8-4de2-bf0b-e4355cfbd048" alt=""><figcaption><p><em>Example of various actions within the Automation Flow.</em></p></figcaption></figure></div>

## Practical example: Checking Old Opportunities

An automation flow can be triggered from any point in SprintHub, such as form actions, extra actions via Webhook, or internal CRM automations.

In the example below, the flow performs a sequence of checks using the condition “**Opportunity lifetime**” for the funnel of *Orders* to identify customers who placed their last order more than three months ago. If this condition is met, the system automatically sends a message with an exclusive discount coupon for recurring customers and, shortly after, creates a new opportunity in the funnel of *Remarketing*.

It is triggered through a Webhook, checking the moment a new order is created on an external platform and starting the automation from that event.

<div data-with-frame="true"><figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FjFOKUPv49nqOyITVb15e%2Fimage.png?alt=media&amp;token=7d3de695-e235-4af9-abc6-0281ae87fa4f" alt=""><figcaption><p><em>Extra action to 'Change automation flow'.</em></p></figcaption></figure></div>

<div data-with-frame="true"><figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FbErNcBcXYL9H6GP2VsRW%2Fimage.png?alt=media&amp;token=6a710a5c-1735-46b4-a58c-68fb3cefcd9a" alt=""><figcaption><p><em>Within the 'Coupon and Remarketing' Automation Flow.</em></p></figcaption></figure></div>


---

# 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/relate/automation-flows/automatic-selectors.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.