Hii, I’m trying to organize all my workflows with taxonomy or name convention, but I have some troubles with the structure.
Right now I’m using something like this, but I don’t now if someone here have a better structure or an example that could help me!
Thank you in advance 
| Type |
Topic |
Product |
Trigger |
Language |
| Blog |
Contactar |
All |
List member |
ES |
| eBook |
Introducción |
Agregación Bancaria |
Form |
EN |
| Campaign |
Innovación Financiera |
Crypto |
Google Ads |
|
| Nuturing |
Infografía |
3DS2 |
Click link |
|
| Task |
API Report |
KYC |
Workflow |
|
| Webinar |
Banca Minorista |
GDPR / PSD2 / Open Banking |
LinkedIn Ads |
|
| Cleaning |
COVID |
GDPR / PSD2 |
Deal Stage |
|
|
Glosario |
Open Banking |
|
|
|
e-Commerce |
PSD2 |
|
|
|
Primer año |
Pagos Recurrentes |
|
|
|
Scoring |
Payment Initiation |
|
|
|
Consumer Finance |
|
|
|
|
Consumer Finance GDS Modellica |
|
|
|
|
Blog |
|
|
|
|
Retail |
|
|
|
|
Proptech |
|
|
|
|
Onyze |
|
|
|
|
Embedded Finance |
|
|
|
|
Regulación |
|
|
|
|
Insurtech |
|
|
|
Hi @shutcliff,
Other community members have discussed naming conventions before, I’d recommend reviewing this thread.
Generally, I think your naming convention would hold up well, a few thoughts:
- The main purpose of your naming convention is to make it easy for you to find your assets. If your convention does that for you and your team, you’re all set.
- Some workflows might have more complex triggers, making it hard to select a specific one.
- Having a long list of “approved” options for naming convention means that other team members have to be briefed very vell to follow it.
- I’m a big fan of separating each element of naming convention with a vertical bar, e.g. Blog | Covid | All …
Personally, I keep naming conventions a little bit more flexible and shorter. I’m also trying to use a similar naming convention for all types of assets, so users don’t have to memorize multiple ones. My go-to is:
YYYYMMDD | Country (two-letter language code) | Type | Segment of records | Topic
For example:
- 20220829 | Germany (de) | Nurturing | Net new contacts | Autumn campaign
- Global (en) | Task automation | Won deals
If elements don’t apply (e.g. the date for a workflow), I simply leave it out, as you can see.
But, again: mostly personal preference.
Hope this helps!
Hi @shutcliff,
I just submitted a product request related to this topic. If you find it useful, feel free to upvote: https://community.hubspot.com/t5/HubSpot-Ideas/Enforce-naming-convention-for-new-assets/idi-p/745831#M133390
Best regards!