> 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-sending-tracked-files.md).

# Automation Flow - Sending Tracked Files

Automation Flow - Sending Tracked Files

You can send tracked files in a message via an Automation Flow, and thus monitor who is accessing your content and how they are interacting with it, through Tracked Files.

* [**To learn about Tracked Files, click here**](https://docs.sprinthub.com/topicos/converter/arquivos-rastreados/arquivos-rastreados-como-criar-e-editar)

Now let's set up an Automation Flow.

1- Click on Automation Flow, click +New

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FZQoQEHVp34JNJPp6SSHs%2Fras1.png?alt=media&amp;token=8fd461d0-8c13-4ece-ada3-92b557f865ed" alt=""><figcaption></figcaption></figure>

2- Enter the Name, add the Segment in which it will be triggered, and leave it Published to activate it, then click "Open Builder"

* [**Learn how to create segments here**](https://docs.sprinthub.com/topicos/relacionar/segmentos)

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FaA787ssJRb0M5W8XwxLj%2Fras2.png?alt=media&amp;token=0983b987-62e8-4360-be3c-4f430f58eb5b" alt=""><figcaption></figcaption></figure>

3 - In the builder, add the first message block. In it, send a greeting message initially, WITHOUT the tracked file.&#x20;

\
**NOTE:** we adopt this strategy because WhatsApp may make your link non-clickable in the first message sent; this happens as a security measure by WhatsApp itself. To learn more, click here.

In the second message block, add the link to the tracked file ALONG WITH THE MESSAGE that will be sent, followed by:

* ?lid={contactfield=id} ➡️ in case the link does NOT end with a ?

OR

* \&lid={contactfield=id} ➡️ in case the link ends with a ?

**NOTE:** {contactfield=id} will be added through the token button, choose the Lead (ID) token\
\
Click Apply, save the Flow.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2F0DX5T1R6WRErN5MPugHp%2Fras3.png?alt=media&amp;token=786831f3-b966-418d-98e6-8b923a42faf1" alt=""><figcaption></figcaption></figure>

In this way, the leads who click on this file and have already been identified in SprintHub (whether because they have already filled out a form, for example) will appear in the Tracked Files list, as shown in the screenshot below:

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FYKVPi6gCmC5YMnGOoM6K%2Farq.png?alt=media&amp;token=2e869582-b8fb-40a4-9291-dae4df6bc50e" alt=""><figcaption></figcaption></figure>

<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-sending-tracked-files.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.