Add Project properties to message templates

HubSpot Ideas
1

Message templates are incredibly powerful in HubSpot and save users a lot of time in day-to-day communication.
However, personalization is currently limited to properties from contacts, companies, deals, tickets, and the sender. This becomes a real limitation when working with Projects.

The problem

Projects are often the central object for operational and service-driven communication. Think of onboarding projects, implementations, migrations, or delivery-related workflows. In these scenarios, teams regularly need to send structured, recurring messages that are project-specific.

At the moment, it’s not possible to personalize message templates using Project properties (such as project name, start date, status, deadline, owner, or custom project fields). This forces users to either:

  • Manually edit messages each time, or
  • Fall back to copy-pasting content outside of HubSpot

Both options reduce efficiency and increase the risk of errors.

Why Projects are a perfect fit for message templates

Projects are, by nature, ideal candidates for templated communication:

  • Status updates
  • Kick-off messages
  • Deadline reminders
  • Completion or handover emails
  • Internal notes or customer-facing messages

Being able to use Project properties in message templates would allow teams to communicate consistently, accurately, and at scale, fully aligned with HubSpot’s promise of a connected CRM.

Suggested solution

Allow Project properties to be used as personalization tokens in message templates, similar to how contact, company, deal, and ticket properties work today.

Value for HubSpot users

  • Faster and more consistent communication
  • Fewer manual edits and errors
  • Better adoption of Projects as a first-class object
  • Stronger alignment between CRM data and daily workflows

This enhancement would significantly improve usability for teams that rely on Projects and further strengthen HubSpot as an all-in-one platform for both commercial and operational processes.

Thanks for considering this idea!

2

I have the same issue. See my post below:

Hi everyone,

I’m running into a limitation when working with HubSpot’s newer Projects object, and I’m curious if others are experiencing the same.

When creating standardized email templates, I’m unable to use personalization tokens from Projects.

For example:

  • I’m working from a Project record
  • I want to send a structured email update related to that Project
  • But I can’t insert any Project properties (like project name, status, deadlines, custom fields, etc.)

It seems like email templates are still mainly limited to Contact (and partially Company/Deal) properties.

This is problematic because Projects are clearly becoming a core object for delivery and operations — and communication is often directly tied to those Project properties.

What I’m trying to achieve:

  • Send emails directly from a Project
  • Use Project properties as personalization tokens
  • Standardize communication (updates, status emails, milestones, etc.)

My questions:

  • Is this currently a known limitation for the Projects object?
  • Are there any workarounds to include Project data in emails?
  • Would this only be possible via workflows (and if so, how)?
  • Or is this functionality on the roadmap?

Curious how others are handling Project-based communication within HubSpot.

Thanks in advance!

3

SAME ISSUE! I want to send message templates from a project record, but I can’t use project properties for the personalization tokens. This would seem like an easy fix for HubSpot. Why have an object available to use if I can’t then personalize emails with the object’s properties?

4

I want to call attention to this again. I have multiple clients that need this feature!