> 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-flows-inserted-tag-based-on-the-leads-date-of-birth.md).
# Automation Flows - Inserted Tag, based on the Lead's Date of Birth
#### In SprintHub, it is possible to insert tag(s) based on the date of birth (including day, month, and year) and use them in various other automations and applications.
To create a segment based on this same rule, see the article below:
{% content-ref url="/pages/e5067e83ea03edef67dc49e26a6ce73dc96e3882" %}
[Segments - Creating according to the Lead's Date of Birth](/en/topics/relate/segments/segments-creating-according-to-the-leads-date-of-birth.md)
{% endcontent-ref %}
### To create and run your flow, follow these steps:
1. **Create the Automation Flow:**
* Go to Automation Flows via “Find Services”. Or just type the name, and the feature appears.
* To create, click “+ New”.
2. **Configure and Create:**
* **Enter a Name:** Give your flow a descriptive name.
* **Enter a Description:** detail of what will happen in the flow.
* **Set up a Segment:** Choose one you prefer.
* **Category:** Choose one you prefer. This is optional
* **Allow leads to restart the flow?:** It depends on your strategy. If you leave it as “YES,” it will go through the flow more than once.
* Click on **“Open Builder”**, to create the flow with your actions and conditions.
3. **Building the Flow:**
It is possible to create several blocks with actions and conditions.
{% embed url="" %}
4. **Save:**
After creating and making the necessary changes, save your Flow and publish it.
* **Published:** When selecting "YES", the flow will start working immediately.
*Done, your flow will now be inserting the tag into your Leads!*
---
# 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-flows-inserted-tag-based-on-the-leads-date-of-birth.md?ask=&goal=
```
`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.
