Universal nodes

99 universal nodes. 10 categories. One typed schema.

Every record in the Product Graph is one of 99 universal node types. Each carries a stable discriminator and lives in a typed store; most also carry three principal filters. Some node types, such as Contact, Company, Product, Review, and Feature, have both a public (PYRAMYD-curated) and a private (your Organization's) variant so you get our dataset plus your own.

Each card lists the node's core fields, its most valuable ones. The fields marked with a dot are required: a record must have them to be stored, such as its name, its type and, for a transaction, its amount, currency, and date. Types are the values its type field accepts; hover or tab to one to see them all. PYRAMYD adds the rest itself: the record ID, owner, team, Organization, sharing level, and timestamps, and for a synced record the system it came from.

Required field
Core field
Public
Private
Public + Private

99 node types10 categoriesTyped schemaAPEX-queryable

People · 8 nodes

Human identity, roles, and labor

Contacts, roles, positions, interviews, skills, compensation · anything that represents a person or their work in the graph.

contact

Vendor Contacts · Customer Contacts

Public + Private

Core fields

Required: Name or email
Required: Contact type
Email
Job title
Company
Phone
LinkedIn profile

role

Roles

Public

Core fields

Required: Role name
Required: Role code
Required: Role type
Seniority
Definition

position

Customer Positions

Private

Core fields

Required: Job title
Required: Position status
Company
Role
Seniority
Start date
Location

interview

Customer Interviews

Private

Core fields

Required: Title
Required: Interview type
Required: Interview date
Interviewee
Outcome
Format
Deal
Transcript

assignment

Customer Assignments

Private

Core fields

Required: Name
Required: Assignment type
Assigned person
Project
Due date

timesheet

Customer Timesheets

Private

Core fields

Required: Name
Required: Time type
Required: Date worked
Required: Time spent
Person
End date
Time-off type
Approval status

skill

Skill Catalog · Customer Skills

Public + Private

Core fields

Required: Skill name
Required: Skill type
Catalog skill
Description

compensation

Customer Compensation

Private

Core fields

Required: Name
Required: Compensation type
Required: Amount
Required: Currency
Required: Effective date
Pay interval
Person
Status

Companies · 8 nodes

Structural boundaries and markets

Companies, teams, workspaces, segments, locations, countries, industries — the containers that hold everything else.

company

Vendor Companies 180K+ · Customer Companies

Public + Private

Core fields

Required: Company name
Required: Company type
Domain
Website
Industry
Country
Employees

team

Customer Teams

Private

Core fields

Required: Team name
Required: Team type
Manager
Parent team
Description

group

Customer Groups

Private

Core fields

Required: Group name
Required: Group type
Group email
Members
Description

workspace

Customer Workspaces

Private

Core fields

Required: Workspace name
Required: Workspace type
Description
Created in source

segment

Customer Segments

Private

Core fields

Required: Segment name
Required: Segment type
Member node type
Mode
Members
Description

location

Customer Locations

Private

Core fields

Required: Location name
Required: Location type
Country
City
Street address
Postal code

country

Countries

Public

Core fields

Required: Country name
Required: ISO country code
Required: Country type
Region
Sub-region

industry

Industries

Public

Core fields

Required: Industry name
Required: Industry type
Industry
NAICS code

Products · 6 nodes

Catalogs, lifecycles, hierarchies

Products, categories, features, releases, reviews — the unbranded and branded product universe.

product

Vendor Products 250K+ · Customer Products

Public + Private

Core fields

Required: Product name
Required: Product type
Required: Vendor
Catalog product name
Description
Lifecycle stage
Pricing model
Website

feature

Standard Features 190K+ · Customer Features

Public + Private

Core fields

Required: Feature name
Required: Feature type
Required: Product or portfolio
Description
Status
Taxonomy feature
Module
Capability

release

Customer Releases

Private

Core fields

Required: Release name
Required: Release type
Required: Release date
Version
Status
Product
Release notes

review

Public Reviews 2.4M+ · Customer Reviews

Public + Private

Core fields

Required: Review title
Required: Review type
Required: Reviewed product
Required: Review text or score
Score
Pros
Cons
Review date

portfolio

Customer Portfolios

Private

Core fields

Required: Portfolio name
Required: Portfolio type
Description
Parent portfolio
Status

Revenue · 12 nodes

Pipelines, marketing, closing tools

Deals, orders, line items, price lists, pipelines, contracts, campaigns, cadences, battlecards · the revenue motion.

deal

Customer Deals

Private

Core fields

Required: Deal name
Required: Deal type
Required: Deal stage
Close date
Amount
Currency
Buyer company
Outcome

order

Customer Orders

Private

Core fields

Required: Order name
Required: Order type
Required: Order total
Required: Currency
Customer
Status
Order date
Price list

pipeline

Customer Pipelines

Private

Core fields

Required: Pipeline name
Required: Pipeline type
Required: Stages
Description
Created in source

subscription

Customer Subscriptions

Private

Core fields

Required: Subscription name
Required: Subscription type
Required: Start date
Customer
Recurring amount
Billing interval
Currency
End date

contract

Customer Contracts

Private

Core fields

Required: Contract name
Required: Contract type
Required: Counterparty
Start date
End date
Annual contract value
Status

campaign

Customer Campaigns

Private

Core fields

Required: Campaign name
Required: Campaign type
Start date
End date
Budget
Status
Audience

cadence

Customer Cadences

Private

Core fields

Required: Cadence name
Required: Cadence type
Steps
Status

battlecard

Customer Battlecards

Private

Core fields

Required: Battlecard title
Required: Battlecard type
Required: Competitor
Our company
Our product
Summary
Status

assessment

Customer 360 Reports

Private

Core fields

Required: Report title
Required: Report type
Required: Subject
Required: Captured on
Subject name
Refresh cadence
Version

evaluation

Evaluations

Private

Core fields

Required: Evaluation name
Required: Evaluation type
What is evaluated
Vendors evaluated
Proposal due
Budget

lineitem

Customer Line Items

Private

Core fields

Required: Line item name
Required: Line item type
Required: Parent document
Required: Line amount
Currency
Quantity
Unit price
Product

pricelist

Customer Price Lists

Private

Core fields

Required: Price list name
Required: Price list type
Status
Parent list
Customers

Finance · 7 nodes

Money flows and accounting periods

Transactions, postings, ledgers, periods, budgets, forecasts, filings — the books behind the business.

transaction

Customer Transactions

Private

Core fields

Required: Transaction name
Required: Transaction type
Required: Amount
Required: Currency
Required: Transaction date
Direction
Counterparty company
Document number

posting

Customer Postings

Private

Core fields

Required: Posting name
Required: Posting type
Required: Amount
Required: Debit or credit
Required: Ledger account
Currency
Journal entry
Accounting period

ledger

Customer Ledgers

Private

Core fields

Required: Account name
Required: Ledger type
Active
Current balance
Parent account
Description
Account number

period

Customer Periods

Private

Core fields

Required: Period name
Required: Period type
Required: Start date
Required: End date
Status
Current period
Parent period

budget

Customer Budgets

Private

Core fields

Required: Budget name
Required: Budget type
Required: Budget amount
Required: Currency
Required: Start date
Budget period
Ledger account
Status

forecast

Customer Forecasts

Private

Core fields

Required: Forecast name
Required: Forecast type
Required: Forecast period
Status
What is forecast
Baseline budget
Forecast amount
Description

filing

Customer Filings

Private

Core fields

Required: Filing name
Required: Filing type
Required: Filing company
Status
Filed date and period covered
Description

Operations · 12 nodes

Strategy, scheduling, architecture

Ideas, requirements, issues, projects, roadmaps, cycles, objectives, capabilities, processes · how work happens.

idea

Customer Ideas

Private

Core fields

Required: Idea title
Required: Idea type
Description
Status
Priority
Submitted by
Votes

requirement

Business Requirements

Public

Core fields

Required: Requirement
Required: Requirement type
Description
Priority
Status
Feature
Roadmap

issue

Customer Issues

Private

Core fields

Required: Title
Required: Issue type
Status
Priority
Description
Assignee
Project
Key

project

Customer Projects

Private

Core fields

Required: Project name
Required: Project type
Status
Start date
Target end date
Description
Priority

roadmap

Customer Roadmaps

Private

Core fields

Required: Roadmap name
Required: Roadmap type
Start date
Status
Description
Portfolio

cycle

Customer Cycles

Private

Core fields

Required: Cycle name
Required: Cycle type
Required: Start date
Required: End date
Status
Project or roadmap
Completed at
Goal

objective

Customer Objectives

Private

Core fields

Required: Objective name
Required: Objective type
Target date
Start date
Status
Progress
Current value
Parent objective

capability

Business Capabilities

Public

Core fields

Required: Capability name
Required: Capability type
Required: Catalog path
Definition
Domain
Category
Aliases

process

Business Processes

Public

Core fields

Required: Process name
Required: Process type
Required: Catalog path
Framework code
Definition
Activity
Category

value

Business Values

Public

Core fields

Required: Value name
Required: Value type
Required: Catalog path
Definition
Value driver
Lever
Aliases

submission

Customer Submissions

Private

Core fields

Required: Form
Required: Submission type
Required: Submitted at
Required: Answers
Submitted by
Submitter email
Score
Completed at

schedule

Customer Schedules

Private

Core fields

Required: Schedule name
Required: Schedule type
Time zone
Enabled
Description
What it runs

Comms · 4 nodes

Meetings, calls, interactions

Communications, chats, channels, events — anything that captures human-to-human interaction.

communication

Customer Communications

Private

Core fields

Required: Subject or title
Required: Communication type
Required: When it happened
Direction
Participants
End time
Company
Channel

chat

Customer Chats

Private

Core fields

Required: Chat name
Required: Chat type
Participants
Channel
Started
Assistant mode

channel

Customer Channels

Private

Core fields

Required: Channel name
Required: Channel type
Workspace
Purpose or topic
Shared with other organizations
Created

event

Customer Events

Private

Core fields

Required: Event name
Required: Event type
Required: Start time
End time
Location or join link
Attendees
Related conversation
Description

Content · 12 nodes

Documents and artifacts

Documents, articles, sheets, slides, notebooks, canvases, forms, files, folders, transcripts — what gets written down.

document

Customer Documents

Private

Core fields

Required: Document title
Required: Document type
Content
Status
Folder
Author
Link to the original
Last edited

article

Customer Articles

Private

Core fields

Required: Headline
Required: Article type
Required: Link
Required: Publish date
Publisher
Body
Language
Author

snippet

Snippets

Private

Core fields

Required: Snippet title
Required: Snippet type
Required: Snippet text
Code language
Description
Where it came from

sheet

Customer Sheets

Private

Core fields

Required: Sheet name
Required: Sheet type
Columns
Description
Lifecycle

slide

Customer Slides

Private

Core fields

Required: Deck name
Required: Deck type
Description
Theme
Made in

notebook

Customer Notebooks

Private

Core fields

Required: Notebook name
Required: Notebook type
Code language
Dataset
Description

canvas

Customer Canvases

Private

Core fields

Required: Canvas name
Required: Canvas type
Description
Thumbnail
Project

form

Customer Forms

Private

Core fields

Required: Form name
Required: Form type
Questions
Status
Public link
Responses

file

Customer Files

Private

Core fields

Required: File title
Required: File type
Required: File name
Required: MIME type
Where the file is stored
Size
Folder
Checksum

folder

Customer Folders

Private

Core fields

Required: Folder name
Required: Folder type
Parent folder
Path
Link
Items

transcript

Customer Transcripts

Private

Core fields

Required: Transcript title
Required: Transcript type
Required: Source meeting, call or recording
Required: Transcript text
Language
Speakers
Summary
Link to the recording

discussion

Discussions

Public

Core fields

Required: Thread title
Required: Discussion type
Required: Link
Required: Posted date
Text
Author
Company discussed
Sentiment

Data · 14 nodes

Datasets, models, AI runtime

Datasets, catalogs, connectors, transformations, prompts, agents, runs, models, experiments, metrics, signals, dashboards, graphs, queries · the data plane.

dataset

Customer Datasets

Private

Core fields

Required: Dataset name
Required: Dataset type
Display name
Description
Columns
Row count
Database
Schema

catalog

Customer Catalogs

Private

Core fields

Required: Catalog name
Required: Catalog type
Description
Parent catalog
Created in source

connector

Customer Connectors

Private

Core fields

Required: Connector name
Required: Connector type
Required: Integration
Sign-in method
Enabled
Last sync
Description
Link

transformation

Customer Transformations

Private

Core fields

Required: Transformation name
Required: Transformation type
Language
Description
Runs on

prompt

Customer Prompts

Private

Core fields

Required: Prompt name
Required: Prompt type
Required: Prompt text
Status
System message
User message template
Variables
Model

agent

Customer Agents

Private

Core fields

Required: Agent name
Required: Agent type
Status
Mode
Steps
Description
Last successful run

run

Customer Processes

Private

Core fields

Required: Run name
Required: Run type
Required: Run status
Start time
End time
Agent
Error
Duration

model

Customer Models

Private

Core fields

Required: Model name
Required: Model type
Algorithm
Framework
Status
Training dataset
Predicts for
Trained at

experiment

Customer Experiments

Private

Core fields

Required: Experiment name
Required: Experiment type
Status
Hypothesis
Primary metric
Start time
End time
Variants

metric

Customer Metrics

Private

Core fields

Required: Metric name
Required: Metric type
Current value
Unit
Measured at
Aggregation
Description

signal

Customer Signals

Private

Core fields

Required: Title
Required: Signal type
Required: Source
Required: Date detected
Source link
Source name
Event date
Summary

dashboard

Customer Dashboards

Private

Core fields

Required: Dashboard name
Required: Dashboard type
Description
Status
Link
Template
Last changed in source

graph

Customer Graphs

Private

Core fields

Required: Graph name
Required: Graph type
Description
Build settings
Layout

query

Customer Queries

Private

Core fields

Required: Query name
Required: Query language
Required: Query text
Description
Dataset
Runs on

Systems · 16 nodes

Identity, devices, developer tools

Repositories, branches, commits, packages, vulnerabilities, flags, resources, credentials, settings, labels, activities, devices, alerts, applications, policies, services · the system substrate.

repository

Customer Repositories

Private

Core fields

Required: Name
Required: Repository type
Visibility
Main language
Default branch
Description

branch

Customer Branches

Private

Core fields

Required: Name
Required: Branch type
Required: Repository
Head commit
Description

commit

Customer Commits

Private

Core fields

Required: Commit ID
Required: Commit type
Required: Repository
Message
Committed at
Author
Lines added

credential

Customer Credentials

Private

Core fields

Required: Name
Required: Credential type
Required: Provider
Required: Secret (stored encrypted)
Expires at
Scopes
Last used
Revoked at

setting

Customer Settings

Private

Core fields

Required: Name
Required: Setting type
Key
Value
Scope

label

Customer Labels

Private

Core fields

Required: Name
Required: Label type
Colour
Description

activity

Customer Activities

Private

Core fields

Required: Action
Required: Activity type
Required: When it happened
Required: Who did it
What it acted on
Outcome
Description

device

Customer Devices

Private

Core fields

Required: Name
Required: Device type
Serial number
Model
Manufacturer
Assigned to

alert

Customer Alerts

Private

Core fields

Required: Title
Required: Alert type
Required: Severity
Summary
Status
Detected at
Category

application

Customer Applications

Private

Core fields

Required: Name
Required: Application type
Vendor
Status
Description

policy

Customer Policies

Private

Core fields

Required: Name
Required: Policy type
Rules
Status
Priority

service

Customer Services

Private

Core fields

Required: Name
Required: Service type
Health
Repository
Owner

package

Package Catalog · Customer Packages

Public + Private

Core fields

Required: Package name
Required: Ecosystem
Description
Repository or feed
Public package
Status
Published at

vulnerability

Vulnerability Catalog · Customer Advisories

Public + Private

Core fields

Required: Name
Required: Vulnerability type
Description
Status
Public advisory
Repository

flag

Customer Flags

Private

Core fields

Required: Name
Required: Flag type
Required: Flag key
On
Status
Variants
Targeting rules

resource

Customer Resources

Private

Core fields

Required: Resource name
Required: Resource type
Cloud provider
Provider resource ID
Region
Status
Size or SKU
Cloud account

99 universal nodes. 10 categories. One typed schema.

Every node in your business. One typed schema.