> For the complete documentation index, see [llms.txt](https://docs.funnelish.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.funnelish.com/automations/actions/tags.md).

# Tags

### Step 1: Create & Manage Tags

You can create and manage your tags inside the [**Orders**](https://v2.funnelish.com/orders) or [**Customers**](https://v2.funnelish.com/customers) tab:

1. Go to [**Orders**](mailto:undefined) or [**Customers**](https://v2.funnelish.com/customers) in your Funnelish dashboard.
2. Create a new tag (e.g. *VIP*, *Subscribed*, *Purchased-ProductA, from FunnelA*).
3. Tags can then be used across your automations.

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

### Step 2: Add Tags with Automations

Automations let you apply or remove tags automatically based on customer activity.

1. Go to **Automations** in Funnelish.
2. Create a new automation and choose a **trigger** (for example: *On purchase*, *On refund*, *On form submission*).
3. Add an **action** → choose **Add Tag** or **Remove Tag**.

<figure><img src="/files/gOGurWZbE5maDIYg2m3M" alt=""><figcaption><p>Adding a tag.</p></figcaption></figure>

5. You can follow the same process to **Remove Tag.**

<figure><img src="/files/t7W0TVthFVfeQGMU0xpC" alt=""><figcaption><p>Removing a tag.</p></figcaption></figure>

6. Save your automation changes.

### Example Use Cases

* Add the tag *Customer* when someone makes their first purchase.
* Add the tag *Upsell Accepted* when a buyer accepts an upsell offer.
* Remove the tag *Purchase Attempt* becomes a paying customer.

### ✅ Result

{% hint style="success" %}
From now on, Funnelish will automatically add or remove the right tags from your customers based on their actions in your funnels. This keeps your CRM clean, enables better segmentation, and allows for smarter follow-up campaigns.
{% 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.funnelish.com/automations/actions/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.