Skip to main content
A tag is a label your workspace puts on a record. Each record type has exactly one tag field, and a record can carry any number of that field’s tags. You name the tags and pick their colours. Nothing in Clustr invents them.

Intro tags

Intro tags are how you track where an intro stands, for example Contacted, Meeting booked or Not interested. A tag marked closes says the conversation on that intro is over: any intro carrying it is closed.
Closed does not mean hidden. A record carrying a closing tag sorts last and draws with a neutral pill; it stays visible and filterable. The one control that removes a row from a table is dismiss. See Account States.

Columns

Each field is one column on every table that shows that record. Each column filters by its tags, so a saved view can be built on any of them.

Managing the tags

Open Settings > Tags to see the values of each field. There you add, edit, recolour, reorder and delete tags. There are no fields to create, rename or delete.

Reading and writing tags

The API calls the fields “tag groups”, so the paths say tag-groups. Every write takes a mode: add keeps what is already there, remove takes tags off, and replace leaves exactly what you send.

Tagging target accounts as you add them

A target account can be tagged when you add it, before it shows in Accounts: the tag goes on the company straight away and is there when the account appears. The value is the name of one of your account tags, ignoring case. An import never creates a tag: a name that is not one of your account tags stops the whole import, and so does a name used in two fields. A company already on your list still gets the tag.

Filtering on tags

Search Opportunities takes tag, a list of tag ids. A record matches when it carries any of them. Every table also filters on the tags of the records it is related to, so a saved view can be built on any of them: On the API, the same filters are account_tag on Search Opportunities and List Connectors, and path_tag on List Accounts, List Connectors and the Raw signals list.

Tags and your CRM

A tag field can be mapped to a CRM multi-select property, per provider, so the field’s tags and the property’s options stay in step. The direction is the same vocabulary the owner and tier mappings use: Clustr sets the value, your CRM sets the value, or paused. It is edited in Settings > Tags in the app, or over the API with Get and Set Tag Field CRM Mappings. The related mappings are documented on each provider’s page: HubSpot, Salesforce, Attio, alongside owner sync and tier sync.

Every write is traced

Setting tags logs a tags_set entry on the record’s activity timeline, whether a person, a Workflow, an API key or an assistant did it.