Snowflake Integration Data Reference

Last updated: October 7, 2026

This guide covers the data Nooks shares with your Snowflake account via the Snowflake integration. It explains how the data is organized, how the tables relate to each other, and what each column contains.

Applies To: All Nooks Workspaces with the Snowflake integration connection. Which tables contain data depends on your Nooks Workspace's seats.

Overview

The Nooks data share integration with Snowflake shares your Workspace's email, call, task, account-signal, and prospect-signal data with your Snowflake account as a read-only database. You can query the data like any other table in your warehouse and join it with your own data.

Data flows one way, from Nooks to Snowflake. After the initial data share, Nooks updates the data every 6 hours. For setup steps and the full refresh schedule, see Connecting Nooks to Snowflake.

Nooks may add tables and columns to the data share over time to give you access to more Nooks data to query in Snowflake. This guide lists every table and column currently included in the data share. Nooks updates this guide when the data share changes.

Database and Schema Structure

The Nooks data share with Snowflake uses the following structure:

Database name: You choose the name when you create the database from the Nooks listing.
Schema name: Every table is in one schema, named shared. For example, if you named the database NOOKS, the Calls table is NOOKS.SHARED.CALLS.
Available Tables: The schema includes the CALLS, EMAILS, TASKS, ACCOUNT_SIGNALS, and PROSPECT_SIGNALS tables.
Column Formatting: All columns use snake_case, the standard style for analytics tables in Snowflake.
Timestamps: All timestamp columns are in UTC.

Tables in the Nooks Data Shares

The Nooks data share currently contains five tables. The following table shows what each one contains, its grain, and which Workspaces have rows in it.

Table	Represents	Grain	Rows Populated For
`CALLS`	Calls made or received through the Nooks dialer.	One row per call	All Workspaces
`EMAILS`	Emails sent through Nooks.	One row per email	Only Workspaces with Nooks Sequencing
`TASKS`	Nooks tasks, active and completed.	One row per task	Only Workspaces with Nooks Sequencing
`ACCOUNT_SIGNALS`	Account signals Nooks has detected.	One row per Signal–account pair	Only Workspaces with Nooks Sequencing or AI Prospector
`PROSPECT_SIGNALS`	Prospect signals Nooks has detected.	One row per Signal–prospect pair	Only Workspaces with Nooks Sequencing or AI Prospector

Your data share always includes all five tables. A table is empty if your Workspace's seat holdings do not include the product it requires, or if your Workspace has no activity of that type.

Joining Tables

The tables share a set of relationship columns with the same names and meanings, so you can join activities without per-table naming rules. The relationship columns are:

User: user_nooks_id, user_email
Prospect: prospect_nooks_id, prospect_external_id, prospect_name
Account: account_nooks_id, account_external_id, account_name
Sequence: sequence_nooks_id, sequence_name, sequence_step_nooks_id, sequence_step_order, sequence_step_action

The _nooks_id columns are stable identifiers you can rely on for joins across these tables. The _external_id columns are the matching record IDs from your connected CRM or sales engagement platform (SEP):

For Workspaces with Nooks Sequencing: These columns contain the prospect or account's Salesforce or HubSpot ID.
For Workspaces without Nooks Sequencing: These fields contain the record ID from the CRM or SEP where the activity originated. For calls, the source field shows which system that is.

A relationship column is null when the activity is not linked to that kind of record. For example, a one-off task that is not part of a Nooks Sequence has a null value for sequence_nooks_id.

Data Dictionary

The data dictionary defines every column in the data share. For each table, it lists the column names, data types, whether each column can be null, and what each column contains. Each table's section also explains which Workspaces have rows in that table.

The data dictionary covers the Calls, Emails, Tasks, Account Signals, and Prospect Signals tables, in that order.

Calls Table

The tables share a set of relationship columns with the same names and meanings, so you can join activities without per-table naming or enrichment rules.

User: user_nooks_id, user_email
Prospect: prospect_nooks_id, prospect_external_id, prospect_name
Account: account_nooks_id, account_external_id, account_name
Sequence: sequence_nooks_id, sequence_name, sequence_step_nooks_id, sequence_step_order, sequence_step_action

The _nooks_id fields are stable identifiers you can rely on for joins across these tables. The _external_id fields are the matching record IDs from your connected CRM or SEP:

For Workspaces with Nooks Sequencing, these fields contain the prospect or account's Salesforce or HubSpot ID.
For Workspaces without Nooks Sequencing, these fields contain the record ID from the CRM or SEP where the activity originated. For calls, use the source field in the Calls table to identify the source system.

A relationship field is null when activity is not linked to that kind of record. For example, a one-off task that is not part of a Nooks Sequence has a null value for sequence_nooks_id.

All timestamp columns are in UTC.

Data Dictionary

The data dictionary provides per-table column definitions.

Calls

The CALLS table has one row per call, including dialer disposition and, when applicable, any Nooks Sequencing context.

The Calls table contains rows for all Workspaces. If your Workspace does not have Nooks Sequencing, the sequence_ columns are null.

The following table describes each column in the Calls table.

Column	Type	Nullable	Description
`id`	varchar	No	Unique call ID
`source`	varchar	No	Call source (values include `Nooks`, `Apollo`, `CSV Import`, `Gong`, `Groove`, `HubSpot`, `Other`, `Outreach`, `Salesforce`, `Salesloft`)
`duration`	double	No	Call duration in seconds
`from`	varchar	Yes	Caller phone number
`to`	varchar	Yes	Called phone number
`direction`	varchar	Yes	`inbound` or `outbound`
`prospect_nooks_id`	varchar	Yes	Nooks prospect ID
`prospect_external_id`	varchar	Yes	Prospect ID in the source CRM or SEP
`prospect_name`	varchar	Yes	Prospect display name
`account_nooks_id`	varchar	Yes	Nooks account ID
`account_external_id`	varchar	Yes	Account ID in the source CRM or SEP
`account_name`	varchar	Yes	Account / company name
`user_nooks_id`	varchar	Yes	Nooks user ID for the user who made the call
`user_email`	varchar	Yes	Email address of the Nooks user who made the call
`sequence_nooks_id`	varchar	Yes	Nooks sequence ID Null if the call was not part of a Nooks Sequence
`sequence_name`	varchar	Yes	Sequence name Null if the call was not part of a Nooks Sequence
`sequence_step_nooks_id`	varchar	Yes	Nooks sequence step ID Null if the call was not part of a Nooks Sequence
`sequence_step_order`	int64	Yes	Step position in the sequence (1-based) Null if the call was not part of a Nooks Sequence
`sequence_step_action`	varchar	Yes	Step action type Null if the call was not part of a Nooks Sequence
`call_disposition_id`	varchar	Yes	Disposition ID
`call_disposition_name`	varchar	Yes	Disposition label (e.g. `Connected`, `Voicemail`)
`dialing_mode`	varchar	Yes	Method used to place the call E(values include `parallel`, `power`, `one-off`)
`transcript`	variant	Yes	The transcript of the call. See the Transcript Format section below for details.
`created_at`	timestamp_ms	No	Record creation time (UTC)
`updated_at`	timestamp_ms	No	Last update time (UTC)
`workspace_id`	varchar	No	Nooks Workspace ID

Transcript Format

The transcript column holds the call transcript as a list of conversation turns. Each turn includes the following fields:

turn_number (integer): The turn's position in the conversation
speaker (varchar): Who spoke
start_seconds: (float, 2 decimal places): When the turn started, in seconds from the start of the call
end_seconds (float, 2 decimal places): When the turn ended, in seconds from the start of the call
text (varchar): The transcribed text

Download the following file for an example value for the transcript column:

Example Value for the Call Transcript Field

Emails Table

The EMAILS table has one row per outbound email send through Nooks, including delivery and engagement timestamps. It . Email subjects and bodies are not included in the data share.

The Emails table only contains rows if your Workspace has Nooks Sequencing. If the email was not sent from a Sequence, the sequence_ columns are null.

The following table describes each column in the Emails table.

Column	Type	Nullable	Description
`id`	varchar	No	Unique email ID
`type`	varchar	Yes	Email provider type (e.g., `outlook`)
`status`	varchar	Yes	Delivery status (e.g. `sent`, `delivered`, `bounced`)
`from`	varchar	Yes	Sender email address
`to`	varchar	Yes	Primary recipient email address
`recipients`	varchar (JSON)	Yes	JSON array of all recipient email addresses
`prospect_nooks_id`	varchar	Yes	Nooks prospect ID
`prospect_external_id`	varchar	Yes	Prospect ID in the source CRM or SEP
`prospect_name`	varchar	Yes	Prospect display name
`account_nooks_id`	varchar	Yes	Nooks account ID
`account_external_id`	varchar	Yes	Account ID in the source CRM
`account_name`	varchar	Yes	Account / company name
`user_nooks_id`	varchar	Yes	Nooks user ID for the user who sent the email
`user_email`	varchar	Yes	Email addres of the Nooks user who sent the email
`sequence_nooks_id`	varchar	Yes	Nooks sequence ID Null if the email was not part of a Nooks Sequence
`sequence_name`	varchar	Yes	Sequence name Null if the email was not part of a Nooks Sequence
`sequence_step_nooks_id`	varchar	Yes	Nooks sequence step ID Null if the email was not part of a Nooks Sequence
`sequence_step_order`	int64	Yes	Step position in the sequence (1-based) Null if the email was not part of a Nooks Sequence
`sequence_step_action`	varchar	Yes	Step action type Null if the email was not part of a Nooks Sequence
`date`	timestamp_ms	Yes	Email sent date (UTC)
`delivered_at`	timestamp_ms	Yes	Delivery timestamp (UTC)
`opened_at`	timestamp_ms	Yes	First open timestamp (UTC)
`clicked_at`	timestamp_ms	Yes	First click timestamp (UTC)
`bounced_at`	timestamp_ms	Yes	Bounce timestamp (UTC)
`replied_at`	timestamp_ms	Yes	Reply timestamp (UTC)
`open_count`	int64	Yes	Total open count
`click_count`	int64	Yes	Total click count
`created_at`	timestamp_ms	No	Record creation time (UTC)
`updated_at`	timestamp_ms	No	Last update time (UTC)
`workspace_id`	varchar	No	Nooks Workspace ID

Tasks Table

The TASKS table has one row per Nooks task that has not been deleted. The status column is a normalized lifecycle value that Nooks derives from the task's status, completion, and in-progress fields, so you do not need to reconcile them yourself.

The Tasks table only contains rows if your Workspace has Nooks Sequencing. If a Task originated outside a Sequence, the sequence_ columns are null.

The following table describes each column in the Tasks table.

Column	Type	Nullable	Description
`id`	varchar	No	Unique task ID
`action`	varchar	No	Task action type, such as `call`, `manual_email`, `auto_email`, `basic_task`, LinkedIn, or SMS variants
`status`	varchar	No	Normalized lifecycle status: `pending`, `ready`, `in_progress`, `finished`, `skipped`, or `failed`
`priority`	varchar	No	Task priority: `low`, `normal`, `high`, or `urgent`
`due_at`	timestamp_ms	No	Time the task becomes due (UTC)
`completed_at`	timestamp_ms	Yes	Time the task was completed (UTC)
`note`	varchar	Yes	Task note or instructions
`user_nooks_id`	varchar	Yes	Nooks user ID for the user currently assigned to the task
`user_email`	varchar	Yes	Email address of the Nooks user currently assigned to the task
`prospect_nooks_id`	varchar	Yes	Nooks prospect ID; may be absent for some one-off or imported tasks
`prospect_external_id`	varchar	Yes	Prospect ID in the source CRM
`prospect_name`	varchar	Yes	Prospect display name
`account_nooks_id`	varchar	Yes	Nooks account ID, resolved through the prospect
`account_external_id`	varchar	Yes	Account ID in the source CRM
`account_name`	varchar	Yes	Account / company name
`sequence_state_id`	varchar	Yes	Enrollment ID Null if the task was not part of a Nooks Sequence
`sequence_state_status`	varchar	Yes	Current enrollment status: `active`, `paused`, or `finished` Null if the task was not part of a Nooks Sequence
`sequence_nooks_id`	varchar	Yes	Nooks sequence ID Null if the task was not part of a Nooks Sequence
`sequence_name`	varchar	Yes	Sequence name Null if the task was not part of a Nooks Sequence
`sequence_step_nooks_id`	varchar	Yes	Nooks sequence step ID Null if the task was not part of a Nooks Sequence
`sequence_step_order`	int64	Yes	Step position in the sequence (1-based) Null if the task was not part of a Nooks Sequence
`sequence_step_action`	varchar	Yes	Action configured on the associated sequence step Null if the task was not part of a Nooks Sequence
`is_one_off`	boolean	No	Whether the task was created independently of a sequence enrollment
`external_id`	varchar	Yes	External CRM or imported task identifier
`workflow_id`	varchar	Yes	Associated Nooks Play / workflow ID
`created_at`	timestamp_ms	No	Record creation time (UTC)
`updated_at`	timestamp_ms	No	Last update time (UTC)
`workspace_id`	varchar	No	Nooks Workspace ID

Note on Deleted Tasks

Nooks regenerates the shared data every 6 hours. Tasks that were deleted do not appear in the regenerated data.

Account Signals

The ACCOUNT_SIGNALS table has one row per signal–account pair, including Signal activity timestamps.

The Account Signals table only contains rows if your Workspace has Nooks Sequencing or AI Prospector, and has Signals set up.

The following table describes each column in the Account Signals table.

Column	Type	Nullable	Description
`account_nooks_id`	varchar	No	Nooks account id
`account_external_id`	varchar	Yes	Account ID in the source CRM
`account_name`	varchar	Yes	Account name
`signal_id`	varchar	No	Nooks signal id
`signal_name`	varchar	Yes	Signal name as configured in Nooks
`signal_type`	varchar	Yes	Signal type (e.g. TechStack, CompanyNewsFacts, CrmField, JobPostTitles)
`signal_category`	varchar	Yes	`hot-account`, `account-insights`, `icp-fit`, `warm-prospect`, `prospect-insights`
`is_signal_archived`	boolean	Yes	Signal has been archived in Nooks
`is_active`	boolean	No	Signal currently fires for this account
`evaluation_status`	varchar	No	`matched`, `not_matched`, or `failed` (the evaluation errored, so this is not a true negative)
`failure_reason`	varchar	Yes	Why the evaluation failed
`signal_feedback`	varchar	Yes	Rep feedback: `Thumbs Up` / `Thumbs Down`
`short_summary`	varchar	Yes	Short AI-generated summary of why the signal fired
`summary`	varchar	Yes	Full AI-generated summary
`is_active_changed_at`	timestamp	Yes	When `is_active` last flipped
`last_evaluated_at`	timestamp	Yes	Last time Nooks evaluated this signal (null = never evaluated)
`updated_at`	timestamp	Yes	Last time the signal result changed
`workspace_id`	varchar	No	Nooks Workspace ID

Prospect Signals

The PROSPECT_SIGNALS table has one row per signal–prospect pair, including signal activity timestamps.

The Prospect signals table only contains row if your Workspace has Nooks Sequencing or AI Prospector, and has signals set up.

The following table describes each column in the Prospect Signals table:

Column	Type	Nullable	Description
`prospect_nooks_id`	varchar	No	Nooks prospect id
`prospect_external_id`	varchar	Yes	Prospect ID in the source CRM
`prospect_name`	varchar	Yes	Prospect name
`account_nooks_id`	varchar	Yes	The prospect's Nooks account id
`account_external_id`	varchar	Yes	The prospect's account ID in the source CRM
`account_name`	varchar	Yes	The prospect's account name
`signal_id`	varchar	No	Nooks signal id
`signal_name`	varchar	Yes	Signal name as configured in Nooks
`signal_type`	varchar	Yes	Signal type (e.g. TechStack, CompanyNewsFacts, CrmField, JobPostTitles)
`signal_category`	varchar	Yes	`hot-account`, `account-insights`, `icp-fit`, `warm-prospect`, `prospect-insights`
`is_signal_archived`	boolean	Yes	Signal has been archived in Nooks
`is_active`	boolean	No	Signal currently fires for this account
`evaluation_status`	varchar	No	`matched`, `not_matched`, or `failed` (the evaluation errored, so this is not a true negative)
`failure_reason`	varchar	Yes	Why the evaluation failed
`signal_feedback`	varchar	Yes	Rep feedback: `Thumbs Up` / `Thumbs Down`
`short_summary`	varchar	Yes	Short AI-generated summary of why the signal fired
`summary`	varchar	Yes	Full AI-generated summary
`is_active_changed_at`	timestamp	Yes	When `is_active` last flipped
`last_evaluated_at`	timestamp	Yes	Last time Nooks evaluated this signal (null = never evaluated)
`updated_at`	timestamp	Yes	Last time the signal result changed
`workspace_id`	varchar	No	Nooks Workspace ID

FAQs

Can I choose which tables are shared with my Snowflake account?

No. Your data share always includes every table. A table is empty if your Workspace's seats do not include the product it requires, or if your Workspace has no activity of that type. For each table's requirements, see the Tables in the Nooks Data Share section.

Can I modify the shared tables?

No. The database Snowflake created from the shared listing is read-only.

Can I join Nooks data with tables already in my Snowflake account?

Yes. You can query the Nooks tables alongside any other data in your warehouse. For the columns to join on, see Joining Tables.