Setting Up Custom HubSpot Properties for Nooks Sequencing Data
Last updated: November 6, 2026
This guide walks through the custom Nooks Sequencing data that Nooks can push to HubSpot, as well as providing guidance on creating or identifying properties to house this data in your HubSpot account.
Applies To: Workspaces with Nooks Sequencing enabled.
Overview
Nooks can enrich your HubSpot Contact and Meeting records with custom data as you engage prospects through Nooks. This makes Nooks data visible in HubSpot to your entire team, and allows you to use it in HubSpot reports and dashboards.
Work with your HubSpot admin team to create the custom properties in this guide on the relevant objects, or repurpose existing properties with matching property types. There is no required naming convention for Nooks to write back the data. The labels and API names in this guide are a suggested convention that works well for more teams; you are free to adjust them to align with your company’s property-naming conventions. The only hard requirement is creating new or identifying existing property with a matching property type. For instructions on creating properties in HubSpot, see HubSpot’s Create and edit properties.
Once you have these properties, you can map them in Nooks CRM Settings. Afterwards, Nooks will populate new data in these properties.
Contact Properties
Create these properties on the Contact object in HubSpot, or identify existing properties with matching property types.
Nooks Field | (Suggested) HubSpot Property Label | Property Type | Definition |
|---|---|---|---|
Actively Being Sequenced | Nooks Actively Being Sequenced | Single checkbox | “True” or “False” depending on whether or not the prospect is currently active in at least 1 Sequence. |
Number of Active Sequences | Nooks Number of Active Sequences | Number | A count of Sequences the prospect is currently active or paused in. |
Current Sequence ID | Nooks Current Sequence ID | Single-line text | The Nooks ID of the prospect’s most recently enrolled Sequence.* |
Current Sequence Name | Nooks Current Sequence Name | Single-line text | The name of the prospect’s most recently enrolled Sequence.* |
Current Sequence Status | Nooks Current Sequence Status | Single-line text | The prospect’s status in their most recently enrolled Sequence (e.g., “Active”, “Paused”).* |
Sequence Step | Nooks Current Sequence Step | Single-line text | The sequence step the prospect is currently on in their most recently enrolled Sequence (e.g., “Step 1”, “Step 2”).* |
Current Sequence Step Type | Nooks Current Sequence Step Type | Single-line text | The action type of the prospect’s current step in their most recently enrolled Sequence.* |
Current Sequence Task Due Date | Nooks Current Sequence Task Due Date | Date | The due date of the prospect’s current step in their most recently enrolled Sequence.* |
Sequenced By | Nooks Sequenced By | HubSpot user (single user) | The HubSpot user who enrolled the prospect in their most recently enrolled Sequence.* |
Date Added to Current Sequence | Nooks Date Added to Current Sequence | Date | The date the prospect was added to their most recently enrolled Sequence.* |
Most Recent Sequence Removal Date | Nooks Most Recent Sequence Removal Date | Date | The date the prospect finished or was removed from their most recently enrolled Sequence.** |
*If a prospect is active in more than one Sequence, each property reflects the most recently enrolled active Sequence. When that Sequence finishes (or the prospect is removed), every property rolls forward to the next most recently enrolled active Sequence. The properties clear entirely once the prospect is no longer active in any Sequence.
**This property only updates when a Sequence finishes or the prospect is removed. It is only blank if the prospect has never finished or been removed from a Nooks Sequence.
Permissions Required: Nooks populates these properties using your Workspace’s connected HubSpot integration user. That user must have read and write access to each property.
Meeting Properties
Create these properties on the Meeting object in HubSpot, or identify existing properties with matching property types.
Nooks Field | (Suggested) HubSpot Property Label | Property Type | Definition |
|---|---|---|---|
Meeting Status | Nooks Meeting Status | Single-line text | The status of the meeting. |
Booking Link | Nooks Booking Link | Single-line text | The slug of the Nooks Booking Link used to schedule the meeting, when applicable. |
Nooks Meeting ID | Nooks Meeting ID | Single-line text | The Nooks ID for the meeting, a standard UUID handy for cross-referencing with Nooks support or in reporting. |
Calendar Event ID | Nooks Calendar Event ID | Single-line text | The ID for the event on the connected Google or Outlook calendar. Helps match the Event record created by Nooks to Events created by other tools. |
Conference Link | Nooks Conference Link | Single-line text | The video-conferencing join link for the meeting. |
Organizer Email | Nooks Organizer Email | Single-line text | The email address of the meeting organizer. |
Sequence Name | Nooks Sequence Name | Single-line text | The Sequence name the meeting was booked through, when applicable. |
Sequence Step Name | Nooks Sequence Step Name | Single-line text | The Sequence step the meeting was booked through, when applicable. |
Meeting Duration (minutes) | Nooks Meeting Duration (minutes) | Number or Single-line text | The scheduled length of the event (from the start to end times) in minutes. |
Booked By | Nooks Booked By | HubSpot user (single user) | The HubSpot owner ID of the rep who booked the meeting. |
Permissions Required: Nooks populates these properties using your Workspace’s connected HubSpot integration user. That user must have read and write access to each property.
FAQs
Do we have to use specific property labels or API names for data to write back successfully?
No. You can choose whatever property labels or API names work best for your team. The labels suggested in this guide are just an example convention that works well for most teams. When creating the properties, the only requirement is that the property types match.