> 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/system-settings/tags.md).

# Tags

Organize your leads in a practical and intelligent way with **Tags**. They help with contact segmentation, campaigns, filters, and automations, making it easier to manage your customers.

{% embed url="<https://youtu.be/Epm-rePFY4U>" %}

***

#### How to create a Tag

Follow the step-by-step guide:

📍 Access:\
**⚙️ System Settings → Tags**

1. Click on **New**
2. Enter the **Tag name** desired
3. Select the **Tag color** 🎨 *(optional)*
   * If no color is defined, the Tag will have **a white background**
4. Click on **Save**

✅ Done! Your new Tag has been created and can now be used.

***

#### 🔎 What you can do with Tags

When accessing a Tag, you can:

* View all leads linked to it
* View information about the associated contacts
* Organize and segment your customer base
* Create filters for campaigns and specific actions

***

#### ⚙️ Using Tags in features and automations

Tags can be used in various platform features, such as:

* **Automation Flows**
* **SAC**
* **CRM**
* **Chatbot**
* **AI Agents**
* **Extra Actions (Webhook) | Forms**

They can act as:

⚡ **Triggers** — starting automations or processes based on a Tag

🔎 **Conditions** — validating whether a lead has a certain Tag or not

🎯 **Actions** — automatically adding or removing Tags during workflows

💡 Example of use:\
When a lead receives the Tag **VIP Customer**, an automation can be triggered, a targeted customer support interaction can occur, or a specific opportunity can be handled in the CRM.

***

#### 🏷️ Adding Tags manually, by import, and via API

In addition to automations, Tags can also be added in different ways:

**✍️ Manual entry**

You can link Tags manually in:

* 💬 **SAC**
* 📊 **CRM**
* 👤 **Contacts**

This makes it possible to classify and organize leads quickly during support, negotiations, or contact management.

**📥 Contact import**

It is also possible to bring Tags at the time of **contact import**, using files:

* **CSV**
* **XLSX**

This way, leads can already be imported with their respective segmentations and classifications.

**🔗 Adding via API**

Tags can also be added via **API**, allowing external integrations and custom automations for lead classification and process triggering.

***

#### 🔍 Using Tags as filters

Tags can also be used as filters to make queries and segmentations easier in:

* **Contacts**
* **Opportunities**
* **Reports**

This makes it possible to find information more quickly and generate more strategic analyses.

***

#### 🗑️ Delete a Tag

{% hint style="warning" %}

### Attention:

A Tag can only be deleted when **there are no leads linked to it**.

If there are associated contacts, you must first remove them from the Tag to delete it
{% 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/system-settings/tags.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.