Setting Up Custom Salesforce Fields for Nooks Sequencing Data

Last updated: September 21, 2026

This guide walks through the custom data Nooks can push to Salesforce and provides guidance on creating or identifying custom fields to house this data in Salesforce.

Applies to: The content in this guide applies to Workspaces with Nooks Sequencing enabled.

Overview

Nooks can stamp your Salesforce Contact, Lead, Task, and Event records with custom prospect and activity data as you engage prospects through Sequences, one-off tasks and calls, and your Nooks Booking Link. This makes Nooks data visible in Salesforce to your entire team, where it can be used in Salesforce reports and dashboards.

Work with your Salesforce admin team to create the custom fields below on the relevant objects, or repurpose existing fields with matching field 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 most teams; you are free to adjust them to adhere to your org's conventions. The only hard requirement is creating a new or identifying an existing field with a matching field type. See this guide for instructions on creating new fields in Salesforce.

Once you have these fields, you can map them in Nooks CRM Settings. Afterwards, new data will begin to populate in these fields.

Contact & Lead Fields

Create these fields on both the Contact and Lead objects (or identify existing fields with matching properties). None are unique or set an External ID unless noted.

Field Label (Suggested)	API Name (Suggested)	Type	Definition (Description)
Nooks Active in Sequence	`nooks_activeinsequence__c`	Checkbox	“True” or “False” depending on whether or not the prospect is currently active in at least 1 Sequence.
Nooks Current Sequence Status	`nooks_currentsequencestatus__c`	Text (255)	The prospect’s status in their most recently enrolled Sequence (e.g., “Active”, “Paused”).*
Nooks Current Sequence Name	`nooks_currentsequencename__c`	Text (255)	The name of the prospect’s most recently enrolled Sequence.*
Nooks Current Sequence Step	`nooks_currentsequencestep__c`	Text (255), not case sensitive	The sequence step the prospect is currently on in their most recently enrolled Sequence (e.g., “Step 1”, “Step 2”).*
Nooks Sequenced By	`nooks_sequencedby__c`	Lookup (User)	The Salesforce user who enrolled the prospect in their most recently enrolled Sequence.*
Nooks Date Added to Current Sequence	`nooks_dateaddedtocurrentsequence__c`	Date/DateTime	The date the prospect was added to their most recently enrolled Sequence.*
Nooks Most Recent Sequence Removal Date	`nooks_mostrecentsequenceremovaldate__c`	Date/DateTime	The date the prospect finished or was removed from their most recently enrolled Sequence.
Nooks Current Sequence ID	`nooks_currentsequenceid__c`	Text (255), not case sensitive	The Nooks ID of the prospect’s most recently enrolled Sequence.*
Nooks Current Sequence Step Type	`nooks_currentsequencesteptype__c`	Text (255), not case sensitive	The action type of the prospect’s current step in their most recently enrolled Sequence.*
Nooks Current Sequence Task Due Date	`nooks_currentsequencetaskduedate__c`	Date/DateTime	The due date of the prospect’s current step in their most recently enrolled Sequence.*
Nooks Number of Active Sequences	`nooks_numberofactivesequences__c`	Number	Count of Sequences the prospect is currently active or paused in.

*If a prospect is active in more than one Sequence, each field reflects the most recently enrolled active Sequence. When that Sequence finishes (or the prospect is removed), every field rolls forward to the next most recently enrolled active Sequence. The fields clear entirely once the prospect is no longer active in any Sequence.

**This field 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: Which users require access to these fields depends on your Nooks Workspace’s Integration User for Sequence Fields setting (set in Settings → All Settings → CRM Settings → Advanced Settings). If set to the default “None – use each rep’s own token,” every Nooks user requires read and write access to these fields. If set to a specific integration user, only that user requires read and write access to these fields.

Activity Object: Core Fields

Create these fields on the Activity object (or identify existing fields with matching properties). None are unique or require an External ID unless otherwise noted.

Field Label (Suggested)	API Name (Suggested)	Type	Page Layout (Suggested)	Definition (Description)
Nooks Sequence Name	`nooks_sequencename__c`	Text (255), not case sensitive	Task and Event	The name of the Sequence the task/event originated from, when applicable.
Nooks Sequence Step Name	`nooks_sequencestepname__c`	Text (255), not case sensitive	Task and Event	The name of the Sequence step the task/event originated from, when applicable.
Nooks Recording URL	`nooks_recordingurl__c`	URL	Task	For recorded calls, the URL to the call recording.
Nooks Call Result	`nooks_callresult__c`	Text (255), not case sensitive	Task	For calls, the disposition the rep attributed to the call.
Nooks Prospect Number Dialed	`nooks_numberdialed__c`	Phone number	Task	For calls, the recipient’s phone number.
Nooks Calling Method	`nooks_callingmethod__c`	Text (64)	Task	For calls, the method used to make the call (e.g., “Power”, “Parallel”, “One-off”.)
Nooks Email Source Type	`nooks_emailsourcetype__c`	Text (64)	Task	For emails, the source of the email (e.g., “AI”, “Automatic”, “Manual”).

Permissions Required: Every Nooks user requires read and write access to the “Nooks Sequence Name” and “Nooks Sequence Step” fields. Access to the remaining fields depends on your Nooks Workspace’s Integration User for Activity Logging setting (set in Settings → All Settings → CRM Settings → Advanced Settings). If set to the default “None – use each rep’s own token,” every Nooks user requires read and write access to these fields. If set to a specific integration user, only that user requires read and write access to these fields.

Activity Object: Email Tracking Fields

Create these fields on the Activity object (or identify existing fields with matching properties). None are unique or require an External ID unless otherwise noted. Skip this field entirely if you are not enabling email open or link click tracking for your Workspace.

Field Label (Suggested)	API Name (Suggested)	Type	Page Layout (Suggested)	Definition (Description)
Nooks Open Count	`nooks_opencount__c`	Number (18, 0 decimals)	Task	For tracked emails, the number of opens detected.
Nooks First Opened At	`nooks_firstopenedat__c`	Date/Time	Task	For tracked emails, the date and time the first open was detected.
Nooks Last Opened At	`nooks_lastopenedat__c`	Date/Time	Task	For tracked emails, the most recent date and time an open was detected.
Nooks Track Opens	`nooks_trackopens__c`	Checkbox	Task	For emails, true or false depending on whether email open tracking was enabled or not, respectively.
Nooks Click Count	`nooks_clickcount__c`	Number (18, 0 decimals)	Task	For tracked email, the number of link clicks detected.
Nooks First Clicked At	`nooks_firstclickedat__c`	Date/Time	Task	For tracked emails, the date and time the first link click was detected.
Nooks Last Clicked At	`nooks_lastclickedat__c`	Date/Time	Task	For tracked emails, the date and time the most recent link click was detected.
Nooks Track Links	`nooks_tracklinks__c`	Checkbox	Task	For tracked emails, true or false depending on whether link click tracking was enabled or not, respectively.

Permissions Required: Which users require access to these fields depends on your Nooks Workspace’s Integration User for Activity Logging setting (set in Settings → All Settings → CRM Settings → Advanced Settings). If set to the default “None – use each rep’s own token,” every Nooks user requires read and write access to these fields. If set to a specific integration user, only that user requires read and write access to these fields.

Activity Object: Nooks Meeting Fields

Create these fields on the Activity object (or identify existing fields with matching properties). All of these fields go on the Event page layout. None are unique or require an External ID unless otherwise noted.

Field Label (Suggested)	API Name (Suggested)	Type	Page Layout (Suggested)	Definition (Description)
Nooks Meeting Status	`nooks_meetingstatus__c`	Text (64), not case sensitive	Event	The status of the meeting.
Nooks Booking Link	`nooks_bookinglink__c`	Text (255), not case sensitive	Event	The slug of the Nooks Booking Link used to schedule the meeting, when applicable.
Nooks Meeting ID	`nooks_meetingid__c`	Text (255), not case sensitive, unique	Event	The Nooks ID for the meeting, a standard UUID handy for cross-referencing with Nooks support or in reporting.
Nooks Conference Link	`nooks_conferencelink__c`	URL	Event	The video-conferencing join link for the meeting.
Nooks Organizer Email	`nooks_organizeremail__c`	Email	Event	The email address of the meeting organizer.

Permissions Required: Nooks populates these fields during Event creation. All users require read and write permissions to these fields.

FAQs

Do we have to use the field labels and API names exactly as they are written in this guide?

No. Ultimately your field mapping selections in Nooks CRM Settings is what tells Nooks where to write data in your instance, not the fields’ labels or API names themselves. The field labels and API names in this guide are only a suggested convention that tends to work well for most teams. You may adjust them to fit your org’s naming conventions. The only requirement is that you use the same field type and configuration, as Nooks blocks you from mapping fields of an incorrect type in CRM Settings.

Can we use fields that already exist in our Salesforce instance instead of creating new ones?

Yes. If needed, you can repurpose existing fields in your Salesforce instance instead of creating brand new ones. If you choose to use existing fields, ensure that:

The fields you choose for each data point match the field type and configuration listed in the Type column on the tables in this guide.
The fields are not actively being populated by another tool or workflow, which could cause Nooks data to be overwritten.