> 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/topicos/relacionar/fluxos-de-automacao/video-tutoriais/fluxo-de-automacao-arquivando-leads-antigos-em-massa.md).

# Fluxo de Automação - Arquivando Leads Antigos em massa

Neste vídeo, vou te mostrar como realizar o arquivamento em massa de leads antigos no SprintHub de forma rápida e organizada. Utilizando o Filtro de Segmento e o Fluxo de Automação, você poderá identificar e arquivar esses leads sem complicações.

O processo é simples: filtramos os leads de acordo com os critérios desejados, data de criação por exemplo, e em seguida, criamos um fluxo automatizado para arquivá-los de forma eficiente. Essa prática é essencial para manter a base de leads organizada e focada em contatos mais relevantes.

Vamos aprender juntos como otimizar sua gestão de leads? 🎥✨

Confira o tutorial abaixo:

{% embed url="<https://youtu.be/zfC3Hu61WuE>" %}


---

# 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/topicos/relacionar/fluxos-de-automacao/video-tutoriais/fluxo-de-automacao-arquivando-leads-antigos-em-massa.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.