Use Tags to Organize Workflows by Domain and Status

n8n's tagging system lets you categorize workflows along multiple dimensions. Use two tag categories consistently: domain (what business area the workflow serves) and status (what lifecycle stage it is in). This turns the workflow list into a filterable, searchable inventory.

Real-world example: A company with 80 workflows implements a tagging taxonomy.

Domain tags (business area):

domain:sales
domain:operations
domain:marketing
domain:engineering
domain:finance
domain:hr
domain:support
```text
Status tags (lifecycle):

```text
status:active
status:development
status:testing
status:deprecated
status:paused
```text
Type tags (structural role):

```text
type:sub-workflow
type:utility
type:scheduled
type:triggered
type:error-handler
```text
Applied to real workflows:

```text
"Orders - Sync to Warehouse - v2"
  Tags: [domain:operations, status:active, type:triggered]

"Leads - Score from Website - v1"
  Tags: [domain:marketing, status:active, type:triggered]

"Slack - Send Formatted Alert - v2"
  Tags: [domain:engineering, type:utility, type:sub-workflow, status:active]

"Reports - Weekly Sales Summary - v1"
  Tags: [domain:sales, status:development, type:scheduled]

"Orders - Sync to Warehouse - v1"
  Tags: [domain:operations, status:deprecated]
```text
Filtering in practice:

```text
Find all active marketing workflows:
  Filter: tags include "domain:marketing" AND "status:active"

Find all sub-workflows (for dependency mapping):
  Filter: tags include "type:sub-workflow"

Find all deprecated workflows (candidates for deletion):
  Filter: tags include "status:deprecated"

Find all workflows in development (for the team standup):
  Filter: tags include "status:development"
```text
> **Note: Tag Governance**
>
> Establish the tag list upfront and document it. Do not let team members create ad-hoc tags like "johns-test" or "important" -- these become noise. Review tags monthly and consolidate duplicates.

Tags cost nothing to maintain and provide enormous value when you need to find, audit, or report on your workflow inventory.

**Related:** [Always Set an Error Workflow on Every Production Workflow](../error-handling-and-reliability/01-always-set-an-error-workflow-on-every-production-workflow.md) | [Use "Pin Data" to Freeze Node Output](../testing-and-debugging/01-use-pin-data-to-freeze-node-output.md)