> 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/tutorial-videos/automation-flow-bulk-archiving-old-leads.md).

# Automation Flow - Bulk Archiving Old Leads

In this video, I’ll show you how to perform bulk archiving of old leads in SprintHub quickly and in an organized way. Using the Segment Filter and the Automation Flow, you’ll be able to identify and archive these leads without any hassle.

The process is simple: we filter the leads according to the desired criteria, creation date for example, and then we create an automated flow to archive them efficiently. This practice is essential for keeping the lead database organized and focused on more relevant contacts.

Let’s learn together how to optimize your lead management? 🎥✨

Check out the tutorial below:

{% 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/en/topics/relate/automation-flows/tutorial-videos/automation-flow-bulk-archiving-old-leads.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.