Skip to content

Standardize date property format across import sources

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Data Hub Professional.

Contact1 stepUpdated for HubSpot seat pricing
OutcomeA date property fed by multiple import sources in inconsistent formats reads and sorts correctly everywhere in HubSpot, instead of storing some records as text-parsed garbage or the wrong day from a day and month swap.
Workflow mapdata-quality-037
Contract start date raw known leads to Format Data: parse into date. Format Data: parse into date leads to Parse succeeded and unambiguous?. Parse succeeded and unambiguous? leads to yes: Set Contract start date, status Converted; no: Status: Ambiguous, create review task. yes no Contract start date raw known Format Data: parse into date Parse succeeded and unambiguous? Set Contract start date, status Converted Status: Ambiguous, create review task
Contract start date raw known leads to Format Data: parse into date. Format Data: parse into date leads to Parse succeeded and unambiguous?. Parse succeeded and unambiguous? leads to yes: Set Contract start date, status Converted; no: Status: Ambiguous, create review task. yes no Contract start date raw known Format Data: parse into date Parse succeeded and unambiguous? Set Contract start date, status Converted Status: Ambiguous, create review task

When to use it, when not to

Use it

  • Use it when a date property, a contract start date, a renewal date, is fed by more than one source, an import, a form, a native integration, each of which may format the raw date differently, DD/MM/YYYY versus MM/DD/YYYY versus a plain text string.
  • Use it right after import, before the date property is relied on by a report or another workflow's delay or branch logic that assumes a correct date.
Read more on when to use itShow less

Skip it

  • Do not use it on a property that is already a native HubSpot date field populated only through the UI's own date picker. The picker already prevents ambiguous entry; this fiche targets fields that started life as text or arrive through an unmanaged import path.
  • Do not use it to guess a date format silently when the source format is genuinely ambiguous, a two-digit day and month both under 12. Flag those for manual confirmation instead of assuming one convention.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 5 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 1 numbered action

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 3 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV, code

The properties JSON creates the fields in one call. The workflow JSON documents the build. The custom coded action ships as a ready-to-paste .js file.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Data quality spec

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library