> 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-archiving-leads-in-bulk.md).

# Automation Flow - Archiving Leads in bulk

This automation makes it easy to archive leads in bulk, allowing you to keep records of leads that are not currently active, without needing to delete them. Ideal for efficiently managing cold leads.

\
**It is important that these leads are in a segment.**\
To do this, you need to create a segment and add them either through the segment filter or through some automation.

* To learn how to create segments, [see this article.](https://docs.sprinthub.com/topicos/relacionar/segmentos)
* To learn how to add leads to a segment through the filter, [see this article.](https://docs.sprinthub.com/topicos/relacionar/segmentos/segmentos-filtro-de-segmento-data-de-criacao-do-lead)

In this example, our leads entered the segment through a CRM automation, [check out this step-by-step guide here.](https://docs.sprinthub.com/topicos/geral/crm/crm-duvidas-comuns/crm-excluindo-oportunidades-em-massa)

Now let's create our Automation Flow.

1 - Go to Automation Flow

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXch0vaVJrR1biP3UQd0iLJVGQLlDQ9x_6eeaN6zKsgec9hhV-4l583NfpQRYHBD1Rrr83isWJU81eTbEWJ23ckwwfhBzuIzzVzcDt2LbV4LlbfZjzf8PhABZOIebW4h1hxmZXOltNhNQ3xn6MKIVW1IhPA?key=QKGXURHB2EHK9NLBT8AnWw" alt=""><figcaption></figcaption></figure>

2 - Click +New, add:

* **Title:** give the automation a name
* **Segment:** specify the segment to which the leads were previously added
* YES for Published, and Allow leads to automatically restart the flow
* Click Open Builder

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXctQcvCNRG7z55QIrMwo20rIyJQrX5Mct_cAdqcq1ML6bKCtp2gsD2Uu63nBq_QJy2CAmqJmN3BcJYxPXPhUtkreHDsyYZEoTENg8xTahsyTtPs3FOofulAXggNanjGSHmqO9LbQNTDB4HDF4qBfC6ydKc?key=QKGXURHB2EHK9NLBT8AnWw" alt=""><figcaption></figcaption></figure>

3 - In the builder, click the orange dot on the Start block, select Actions, and search for the Archive Leads action

Read the warning message - Attention: Archiving a lead will not delete it, however it will no longer be able to participate in any automated system in SprintHub.

Click Apply, Save, and Close.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeILZjQ1H6lCdCwaGo9ibcpYk6_eJqcw0eqbwkK2upo3K5FKV5ahpSMdC-_wI__Dn-EgmqgtaVST1koakTD_KTeuu1LecCgKXNnx0eY1TjS-RRjwXpBzK3r6f79GIwGKxWB41Ks0ghg0wMByrE1b0rBg8Ml?key=QKGXURHB2EHK9NLBT8AnWw" alt=""><figcaption></figcaption></figure>

<br>

{% hint style="info" %}
Automation flows triggered by the segment, **only run once per lead.** If you remove the lead from the segment and add it again, **the Flow WILL NOT be executed on the lead again.**
{% endhint %}


---

# 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-archiving-leads-in-bulk.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.