> 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/common-questions/automation-flow-action-change-automation-flow-option-remove-from-flows.md).

# Automation Flow - Action “Change automation flow” — Option “Remove from flows”

The “Change automation flow” action allows you to control contact participation in existing flows within the system. Among the available options is “Remove from flows,” which has an important behavior to understand.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FKHp8PQPDY33LpjlT9rPD%2Funknown.png?alt=media&amp;token=ac577618-8369-4fce-85ba-f76bf301378d" alt=""><figcaption></figcaption></figure>

#### What happens when you choose “Remove from flows”

When this option is selected, the chosen automation flow that the contact is currently taking part in is stopped immediately.\
This means that:

* Future scheduled actions within that flow will not be executed.
* The contact is automatically removed from the flow they were in.
* If the contact is in more than one active flow, you can choose which flow you want to remove the contact from.

#### Practical example

Imagine that a contact is participating in a nurturing flow with emails scheduled for the next few days. If an automation performs the action “Change automation flow → Remove from flows,” the sending of the upcoming emails is canceled immediately, and the contact stops being part of that flow.

#### Tip

This action is useful when you want to:

* End automated interactions with contacts who have already reached a certain stage in the funnel.
* Avoid duplicate communications between different flows.

Redirect the contact to another flow that is more suitable for their journey.<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/relate/automation-flows/common-questions/automation-flow-action-change-automation-flow-option-remove-from-flows.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.
