> 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-difference-between-stage-automation-and-funnel-automation.md).

# CRM - Difference between stage automation and funnel automation

Within a CRM, automations are essential features for optimizing the sales process, reducing manual tasks, and ensuring that no opportunity is forgotten. However, there are different types of automations that can be applied according to your operation's needs. Among the main ones, stage automations and funnel automations stand out.

## What are stage automations?

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2F7wn74rUjdWESKy8cxxPq%2Fetapa.jpg?alt=media&amp;token=e7da911a-a729-4dd9-a3b8-8cf2d50d12e0" alt=""><figcaption></figcaption></figure>

Stage automations are configured to run at specific moments in the sales funnel. That is, whenever an opportunity enters, advances, or falls back in a certain stage, the automation will be triggered.

They can be applied to opportunities with Open, Won, or Lost status. Usage examples:

* Trigger a welcome email when the opportunity enters an initial stage.
* Create a follow-up task when the opportunity moves to a negotiation stage.
* Send a satisfaction survey when the opportunity is marked as “won”.

## What are funnel automations?

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FjHWDlOLeKwPQVs2mdFIm%2Ffunil.jpg?alt=media&amp;token=aa5a0730-427b-4b73-b4e6-7ec7be13d0ac" alt=""><figcaption></figcaption></figure>

Funnel automations have a broader function and are applied at the funnel level as a whole, not just in a specific stage.

They are executed only on opportunities with “Open” status. Usage examples:

* Trigger a sequence of automatic emails for leads that enter the funnel.
* Add segmentation tags when creating a new opportunity.
* Notify the person responsible whenever a new opportunity is registered.

### Practical difference

The main difference between the two types of automation lies in the moment when each one acts:

* Stage automation → linked to the advancement or status change of the opportunity in a specific funnel stage (works for Open, Won, and Lost).
* Funnel automation → linked to the opportunity entering the funnel or to general process events (works only for opportunities in Open).

### Conclusion

Choosing between stage automation and funnel automation depends on the type of process you want to automate. While stage automations give more control over specific actions in each phase, funnel automations are useful for standardizing broader workflows.
\
The ideal is to combine both strategies to create a relationship cadence that follows the lead from the first contact until the sale is closed.

<br>


---

# 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-difference-between-stage-automation-and-funnel-automation.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.