> For the complete documentation index, see [llms.txt](https://docs.zerowork.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerowork.io/using-zerowork/using-building-blocks/after-repeat.md).

# After Repeat

Lets you do actions **after** loop iterations completed. 

*After Repeat* building block must always be placed after *Start Repeat* building block. Below are some examples.

#### **Example 1**: Send yourself an email notification after your TaskBot finished its run

This is the workflow set-up where *Start Repeat* building block is set to loop through some actions. *After Repeat* is placed right after *Start Repeat* building block and ensures that TaskBot will send you an email once all loop iterations are completed.

<figure><img src="/files/Cqn2KsebKO6wal5b4Nsb" alt=""><figcaption></figcaption></figure>

#### **Example 2**: Chain multiple loops - first collect leads, then engage with them in the same run

*After Repeat* can produce 'workflow in workflow' effect since it lets you chain multiple independent loops within the same workflow.&#x20;

Imagine that you set up a loop to collect leads, as described here: [Save Lists](/using-zerowork/using-building-blocks/save-web-element/save-lists.md), and you set up another loop to iterate over collected leads and visit each profile, as described here: [Enrich Existing Data](/using-zerowork/using-building-blocks/save-web-element/enrich-existing-data.md). You can create two separate TaskBots for these two scenarios. Or, you can use *After Repeat* to unite both in the same workflow, as shown below.

<figure><img src="/files/38Bu1a2MrYykiPMfXRBa" alt=""><figcaption></figcaption></figure>

### Video Tutorial

{% embed url="<https://youtu.be/zUDBdcjxwoc?si=2y9DWsJbdF7Jcb27>" %}