Skip to content
The Workflow Library
Get the full library

Calculated property: full name from first and last name

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.

Contact2 stepsUpdated for HubSpot seat pricing
OutcomeA single, always-current full name value exists on every contact, ready for list views, exports, and integrations that expect one name field instead of two.
Workflow mapdata-quality-010
First or last name known or changed leads to Custom code: trim and join first + last name. Custom code: trim and join first + last name leads to Set Full name calculated. First or last name known or changed Custom code: trim and join first + last name Set Full name calculated
First or last name known or changed leads to Custom code: trim and join first + last name. Custom code: trim and join first + last name leads to Set Full name calculated. First or last name known or changed Custom code: trim and join first + last name Set Full name calculated

When to use it, when not to

Use it

  • Use it when an export, a connected tool, or a report needs one combined name field and cannot concatenate first and last name itself.
  • Use it when first or last name is sometimes blank, and you want a graceful single-field fallback (just the name that exists) rather than a value with a stray leading or trailing space.
Read more on when to use itShow less

Skip it

  • Do not use it purely for personalization inside HubSpot emails or internal notifications. Native personalization tokens ({{contact.firstname}} {{contact.lastname}}) already combine both without needing a stored property.
  • Do not use it as a substitute for keeping First name and Last name themselves clean. This workflow reads them as they are; pair it with data-quality-005 if casing is inconsistent.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 2 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 · 2 numbered actions

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

Not the workflow you needed?

More in Data quality

50 specs in this section

See all 50 This category, 39 EUR
FreeRequired field enforcement on contact creation (email or phone missing)Contact9 steps Name casing cleanup for first name, last name, and company nameContact6 steps Duplicate contact detection and merge review queueContact7 steps Phone number formatting to a standard international formatContact4 steps

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