Skip to main content
Your workspace holds several kinds of data, each grouped into a domain. This page is the map: what each domain is, in plain language, and a direct link to the full field-by-field reference for every single dataset. To learn how to work with any of these as a table — filtering, columns, visibility — see Data Views.

Sales & Commerce

Your shop’s transactions — orders, line items, the customers behind them, the products they bought, and synced meeting notes.

Procurement

Buying the right stock at the right time — demand, a per-SKU queue, purchase orders, suppliers, seasonality and trend analytics.

Marketing & Outreach

How you reach and track customers — LinkedIn, email, ads, web events, the YouTube market-intelligence pipeline, and support.

Governance

The rules and playbooks your company runs on — decisions, strategy documents, and SOPs.

Every dataset, in detail

Every dataset below has its own reference page — what it is, how it gets its data, and every field explained. This is the full catalog.

Sales & Commerce

Your shop’s raw transaction data — the material behind almost every sales and retention number.
  • Orders — every e-commerce order with status, totals, and shipping.
  • Order Line Items — the individual products on each order.
  • Customers — customer/contact records with lifecycle status.
  • Products — product master data: stock, prices, lead times, family/model attributes.
  • Meeting Notes — synced call and meeting notes with action items.

Procurement

Turning sales history into one clear buying decision per product. Start with the Purchasing & Procurement chapter for the full workflow.
  • Product Demand — how fast each variant sells and how long stock lasts.
  • Procurement Queue — one row = one buying decision per SKU, with status and recommendation.
  • Purchase Orders — order lines from draft through received.
  • Suppliers — supplier master data: lead times, target stock, currency.
  • Procurement Config — the tunables: demand weights, cutoffs, seasonality.
  • Weekly Sales — units sold per product per calendar week.
  • Family Trend — which model families are rising or falling, seasonally adjusted.
  • Seasonality — the seasonal factor per month and where it comes from.
  • Customer Reorder Due — repeat customers due for their next purchase.

Marketing & Outreach

How you reach and track customers. These are largely agent-maintained — they fill and stay current once your workspace runs the relevant outreach and market-intelligence agents.
  • LinkedIn Leads — the LinkedIn lead/CRM record: identity, pipeline scoring, outreach timing, agent handoff.
  • LinkedIn Messages — the per-message log behind each lead.
  • LinkedIn Activity Limits — the daily guardrail keeping automated activity safe.
  • Email Campaigns — one row per send: audience, opens, clicks, revenue.
  • Meta Ads — daily Facebook/Instagram ad performance.
  • Web Events — raw website behaviour events with session and device context.
  • YouTube Watch — watched channels and the videos pulled, transcribed, and AI-enriched from them.
  • Support Tickets — customer support tickets with status, priority, and resolution.
  • Customer Outreach — the reorder-outreach tracker, one row per customer per cycle.

Governance

The rules and playbooks your company runs on.
  • Decisions — process questions and the rules they become (61 fields, the full loop).
  • Strategy — company strategy documents.
  • SOP — standard operating procedures.

Knowledge (what your agents know)

Not business tables but the context agents draw on — documented in the API reference: Knowledge, Memory, Skills.

How data gets in

Most domains fill themselves as your business runs. Two paths bring data in:
  • Connectors & ingest — admins connect external systems under Settings › Data Sources and point them at an ingest endpoint; rows appear idempotently (re-sending the same record updates instead of duplicating). Full details in the Ingest API reference.
  • Agents — the marketing, outreach, and market-intelligence domains are largely agent-maintained: they appear and stay current once your workspace runs the relevant agents.
Every table is isolated to your company and then filtered by your departments and each record’s visibility scope — see Data Views for how that works in the UI.