# Set validation rules for postal code for HubSpot default property

**URL:** <https://community.hubspot.com/t/set-validation-rules-for-postal-code-for-hubspot-default-property/68012>\
**Category:** HubSpot Ideas\
**Tags:** object, properties\
**Created:** [October 27, 2022, 12:52pm UTC](https://community.hubspot.com/t/set-validation-rules-for-postal-code-for-hubspot-default-property/68012 "2022-10-27T12:52:28Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![kikidee125](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/kikidee125/32/102498_2.png) [@kikidee125](https://community.hubspot.com/u/kikidee125)\
**Post date:** [October 27, 2022, 12:52pm UTC](https://community.hubspot.com/t/set-validation-rules-for-postal-code-for-hubspot-default-property/68012/1 "2022-10-27T12:52:28Z")

</div>

In the Beta version, there is no way to add data validation to HubSpot’s default Postal Code property. This option is currently grayed out saying the field cannot be edited. This should either be editable or should default to a minimum of 5 digits.

 ![Postal Code.PNG](https://d2qpr2jzcazej7.cloudfront.net/original/2X/1/1c772241a132a6c036ebf6d7288860419567f18c.png)

---

<div class="post-metadata">

**Author:** ![TRoberts1](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/troberts1/32/89259_2.png) [@TRoberts1](https://community.hubspot.com/u/TRoberts1)\
**Post date:** [December 7, 2022, 6:10pm UTC](https://community.hubspot.com/t/set-validation-rules-for-postal-code-for-hubspot-default-property/68012/2 "2022-12-07T18:10:02Z")

</div>

Yes, please make this available! It is grayed out for me too.

---

<div class="post-metadata">

**Author:** ![dkarrasKSI](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/dkarrasksi/32/93181_2.png) [@dkarrasKSI](https://community.hubspot.com/u/dkarrasKSI)\
**Post date:** [February 22, 2023, 5:26pm UTC](https://community.hubspot.com/t/set-validation-rules-for-postal-code-for-hubspot-default-property/68012/3 "2023-02-22T17:26:05Z")

</div>

Exactly! I have workflows that rely on people putting in 5-digit zip codes to match against a list. If somebody puts in 5 digits plus the hyphen and 4 more digits, it won’t flow through my workflow properly. If we could limit the field to 5 characters, problem solved. It would be incredible onerous for me to create a custom field just for this, migrate all the data, and ensure it doesn’t break anything anywhere else. Please liberate the validation rules on this field!

---

<div class="post-metadata">

**Author:** ![NTunnicliffe](https://avatars.discourse-cdn.com/v4/letter/n/6f9a4e/32.png) [@NTunnicliffe](https://community.hubspot.com/u/NTunnicliffe)\
**Post date:** [March 17, 2023, 3:44pm UTC](https://community.hubspot.com/t/set-validation-rules-for-postal-code-for-hubspot-default-property/68012/4 "2023-03-17T15:44:34Z")

</div>

Would also like this - seems a bit silly that there isn’t some way for us to validate a post code that’s entered on a form etc? It’s causing issues with our CRM integration and seems odd that it’s greyed out and can’t be edited. And I ideally think it needs to be editable as I need to change the maximum rather than minimum figure.

---

<div class="post-metadata">

**Author:** ![Shamgar](https://avatars.discourse-cdn.com/v4/letter/s/df788c/32.png) [@Shamgar](https://community.hubspot.com/u/Shamgar)\
**Post date:** [August 16, 2023, 3:45pm UTC](https://community.hubspot.com/t/set-validation-rules-for-postal-code-for-hubspot-default-property/68012/5 "2023-08-16T15:45:50Z")

</div>

This is insane that there’s not a way to add validation rules to HubSpot fields (like the postal code field)! @hubspot, this should be something you had in version 1 of your software! If you’re going to lock-down a default HubSpot field, at least make it smarter for what it’s intended to be used for. In this postal code example, we had someone paste in an entire Google Search query which clogged-up our entire lead import sync script from HubSpot to our database via the API. Please fix this ASAP.

---

<div class="post-metadata">

**Author:** ![magmar](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/magmar/32/101557_2.png) [@magmar](https://community.hubspot.com/u/magmar)\
**Post date:** [January 11, 2024, 2:18pm UTC](https://community.hubspot.com/t/set-validation-rules-for-postal-code-for-hubspot-default-property/68012/6 "2024-01-11T14:18:26Z")

</div>

We need validation options for all form elements. At least, it would be best, if we could add our own validation scripts directly via the form editor.

---

<div class="post-metadata">

**Author:** ![SChalmers](https://avatars.discourse-cdn.com/v4/letter/s/b77776/32.png) [@SChalmers](https://community.hubspot.com/u/SChalmers)\
**Post date:** [April 10, 2024, 1:50am UTC](https://community.hubspot.com/t/set-validation-rules-for-postal-code-for-hubspot-default-property/68012/7 "2024-04-10T01:50:26Z")

</div>

Rather than giving backend Hubspot users options to customise validations for Hubspot’s standard zip code field, Hubspot should automatically validate it taking into account that there are many different zip code validation rules required for contacts from different countries.

Even if we were given backend options to set all these rules up for ourselves, surely this is something a basic CRM system should be adding value by taking care of for us?

No country has a zip code 1 char long and yet if you make this Hubspot-supplied field mandataory on a form, Hubspot accepts this kind of input as valid.

---

<div class="post-metadata">

**Author:** ![rwebb1](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/rwebb1/32/2741_2.png) [@rwebb1](https://community.hubspot.com/u/rwebb1)\
**Post date:** [June 21, 2024, 6:41pm UTC](https://community.hubspot.com/t/set-validation-rules-for-postal-code-for-hubspot-default-property/68012/8 "2024-06-21T18:41:23Z")

</div>

👋Hello! I’m Rachel from the HubSpot Product team. Sharing an update - ' **Set validation rules from HubSpot default properties’** is now in public beta, which means you can opt into it via Product Updates. Postal Code is one of the default propertes included in the beta.
