👥 Owners, users and the current user
Placeholders for the record owner, associated users and the current user – with consistent v6 syntax and all HubSpot user properties.
In v6 ChiliDocs uses HubSpot's internal user properties directly – no more custom naming scheme. Owner and user placeholders now work consistently across every object.
âś… Record owner
The owner placeholder always names its object, followed by the user property you want to output:
[contact.owner.hs_email][company.owner.hs_given_name][deal.owner.hs_family_name][ticket.owner.hs_job_title]
The pattern applies to every object with an owner – including orders, quotes, subscriptions, courses and custom objects.
âś… Non-default owner property
If an object has more than one owner property (e.g. a quote with an additional domain owner), you can specify the property explicitly:
[quote.owner(hs_quote_owner_id).hs_email]
âś… Owner with an association label
With multiple associated companies or contacts, use labels to pick the exact record and get its owner:
[company(Primary).owner.hs_email]
âś… Owner inside tables
Within a table like [deal_table], [deal.owner.hs_email] gives you the owner of each row's deal.
âś… Associated HubSpot users
For users associated with the record (via HubSpot user associations):
[user.hs_email]– all associated users[user(Label).hs_email]– targeted via an association label
âś… Current user
The user who clicked Generate:
[currentuser.hs_given_name]
In a workflow context, currentuser is empty – no user triggers the run.
âś… Available user properties
Any HubSpot user property works – most common:
hs_given_name(first name)hs_family_name(last name)hs_emailhs_main_phonehs_job_title
⚠️ Owner without an object is an error
A bare [owner.hs_email] (without an object in front) produces a red error in the document:
SyntaxError: owner needs its object, e.g. contact.owner.x [owner.x]
đź’ˇ Legacy placeholders (v5)
Names like [contact.ownerfirstname], [contact.owneremail], [currentuser.firstname] have been removed. Existing templates still work (they are translated at generation time) – a one-time migration is worth it: see Migrate templates to the v6 placeholder syntax.