Assigned User Data through Data Sharing

Created by Ram Tulasi, Modified on Thu, 14 May at 6:33 AM by Aye Myat

Note: Feature(s) Pending Rollout

Features and functionality described on this page are part of our May 2026 release, which is rolling out to eligible customers May 14-June 18, 2026. See our Release Notes here to learn more.

Objective

The purpose of this article is to provide direction to Outreach customers with access to data sharing to retrieve and access the Notes data along with the other records they already have access to.

Applies To

Admins

Before You Begin

If you are unfamiliar with Data Sharing, you can learn about it in Outreach’s Developer Portal.

Overview

Set Up

There’s no specific setup required to retrieve assignment data, you can use the general set up guidance available for Snowflake and Databricks Delta Sharing.

You’ll however need to have access to Outreach’s Data Sharing capabilities, including required licenses and permissions.

Available Fields

The structure of the notes table is as follows:

column	type	definition	sample value	sample use
id	integer	Primary key of the note record	42	Uniquely identify a note entity
subject_id	integer	Foreign key to the parent entity (polymorphic — Prospect, Account, etc)	42	Link a note to a specific subject (prospect/account, etc)
subject_type	string	Polymorphic discriminator — type of the parent entity	“Prospect”, “Account”, “Opportunity”, etc	Determine which entity type the note belongs to (prospect/account, etc)
user_id	integer	Legacy field, should be ignored	87	Used to associate note with a user
message	text	Body text of the note	“Discussed pricing with the client”	Display note content in the UI; full-text search
created_at	datetime	Timestamp when the record was created	2025-03-18 09:00:00	Sort notes chronologically; filter by date range
updated_at	datetime	Timestamp of the last update	2025-03-18 10:00:00	CDC change tracking; incremental sync; sorting
note_type	string (default: “note”)	Activity type from the set: note, call, coffee, beer, meeting	“call”	Filter by note type
creator_id	integer	Foreign key to the creator (polymorphic — User, SystemActor, etc.)	87	Identify who created the note; governance and audit
creator_type	string	Polymorphic type of the creator entity (User, SystemActor, etc.)	“User” or “SystemActor”	Used with creator_id to determine creator entity
opportunity_id	integer	Foreign key to the associated opportunity	305	Link a note to an opportunity; auto-associated via association rule
pinned_at	datetime (nullable)	Timestamp when the note was pinned; nil = not pinned	2025-08-18 10:00:00	Surface pinned notes at the top of the list; transformed to boolean pinned in GraphQL/Public API
opportunity_association_rule	string	Virtual field, should be ignored	“most_recent”	Used to pass association rule when creating a note