Use Naming Conventions for Workflows

Without naming conventions, a workspace with 50+ workflows becomes an unnavigable mess. A consistent naming pattern lets team members find, understand, and organize workflows at a glance. The pattern [Domain] - [Action] - [Version] strikes a balance between detail and brevity.

Real-world example: A company's n8n workspace before and after adopting naming conventions.

Before (actual workflow names from a real workspace):

New workflow
new workflow (2)
order sync
test order thing
Slack alert
fix for slack
PRODUCTION order sync v2 FINAL
order sync v2 FINAL (copy)
```text
After applying the convention `[Domain] - [Action] - [Version]`:

```text
Orders - Sync to Warehouse - v2
Orders - Validate and Enrich - v1
Orders - Send Confirmation Email - v1
Inventory - Check Stock Levels - v1
Inventory - Reorder Alert - v2
Slack - Send Formatted Alert - v1         (utility sub-workflow)
Slack - Send Formatted Alert - v2         (utility sub-workflow)
Monitoring - Workflow Error Handler - v1  (system workflow)
Monitoring - Daily Health Check - v1      (system workflow)
```text
Extended conventions for common patterns:

```text
Sub-workflows:     [Domain] - [Action] - v[N]  (same convention, tagged with "sub-workflow")
Scheduled:         [Domain] - [Action] (Hourly|Daily|Weekly) - v[N]
Triggered:         [Domain] - On [Event] - v[N]
Test/Dev:          [DEV] [Domain] - [Action] - v[N]
Deprecated:        [DEPRECATED] [Domain] - [Action] - v[N]
```text
> **Tip: Enforce at the Team Level**
>
> Create a Sticky Note template that new workflows must include. Document the naming convention in your team's runbook. In n8n Enterprise, use workflow tags to enforce domain categorization.

Consistent naming transforms a workflow list from a chaos of inscrutable titles into a self-documenting inventory of your automation capabilities.

**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)