Evidence

Adapter classifies every piece of ingested data as an evidence type. Each evidence type has a fixed schema regardless of which provider it came from.

General types are not tied to a provider. email has the same schema whether it came from Gmail or Outlook, and deal is the same whether you push it yourself or sync it from a CRM.
Provider types are records as one integration stores them, such as salesforce_opportunity or github_issue. Where a provider record has a general equivalent, the Becomes column shows the general type it is modeled as.

When you query the Search endpoint, each result includes an evidence_type field set to one of the values below.

General

Evidence type	Description
`article`	An external publication — a news article, blog post, press release, or syndicated feed item
`asset`	Stored as a blob and analyzed via vision/OCR/EXIF; not text-indexed unless analysis yields text
`calendar_event`	Normalized across Google Calendar, Outlook, and .ics attachments
`conversation_message`	For Slack connector data use evidence_type=‘slack_message’
`document`	The generic sibling of provider-specific document types like notion_page
`drive_file`	Normalized across Google Drive, OneDrive, and SharePoint document libraries
`email`	Normalized across Gmail and Outlook
`file`	Linked to its parent evidence (e.g
`invoice`	Becomes an invoice on the transaction it belongs to; its line items arrive as separate line_item records and fold into the transaction
`line_item`	A line declares its parent record and its product in related_records; the graph build folds it into the parent’s line_items and links the parent to the product
`order`	Becomes an order on the transaction it belongs to; its line items arrive as separate line_item records and fold into the transaction
`product`	Anchors a product entity; line items on deals, quotes, orders and invoices point at it
`video`	Caller-supplied text tracks (subtitles, captions, audio descriptions, transcript, chapters) are indexed as searchable content alongside pipeline-derived keyframe captions

By provider

GitHub

6 evidence types

Evidence type	Description
`github_comment`	A human comment on a GitHub issue or pull request: a conversation comment, a review summary, or an inline review comment on a line of the diff
`github_discussion`	A GitHub Discussions thread: a forum-style question, answer or announcement on a repository
`github_issue`	A GitHub issue or pull request, told apart by its kind
`github_push`	A git push to a repository: one or more commits landing on a branch
`github_release`	A published release of a GitHub repository, usually tied to a git tag
`github_repo`	A GitHub repository and its top-level details

HubSpot

16 evidence types

Evidence type	Becomes	Description
`hubspot_call`	`document`	A logged call, with its notes or recorded-call transcript
`hubspot_company`	`company`	A company in the HubSpot CRM
`hubspot_contact`	`contact`	A person in the HubSpot CRM, with their lifecycle stage and lead status
`hubspot_deal`	`deal`	A deal and its pipeline stage, with the company and contacts it involves
`hubspot_email`	`email`	A logged email, with its sender and recipients
`hubspot_invoice`	`invoice`	An invoice for a sale
`hubspot_lead`	`lead`	A lead being qualified, always tied to a contact
`hubspot_line_item`	`line_item`	A product line on a deal, quote, order or invoice, with its quantity and price
`hubspot_meeting`	`calendar_event`	A logged meeting
`hubspot_note`	`document`	A note pinned to CRM records
`hubspot_order`	`order`	A commerce order
`hubspot_owner`	`contact`	A HubSpot user who owns CRM records
`hubspot_product`	`product`	A product in the product library
`hubspot_quote`	`document`	A quote shared with a buyer
`hubspot_task`	`task`	A task assigned to someone
`hubspot_ticket`	`document`	A help desk ticket

Linear

5 evidence types

Evidence type	Description
`linear_comment`	A comment on a Linear issue: discussion, status updates and decisions
`linear_cycle`	A Linear cycle: a time-boxed sprint planning a batch of work
`linear_initiative`	A Linear initiative: a high-level goal spanning several projects
`linear_issue`	A Linear issue: a unit of tracked work with a workflow state, priority and assignees
`linear_project`	A Linear project: issues organised around a shared deliverable or milestone

Notion

1 evidence type

Evidence type	Description
`notion_page`	A Notion page: a standalone document, a wiki entry, or a row in a Notion database

Salesforce

30 evidence types

Evidence type	Becomes	Description
`salesforce_account`	`company`	A company the business sells to or works with
`salesforce_campaign`		A marketing campaign: its type, status, dates, budget and the leads, contacts and revenue it produced
`salesforce_campaign_member`		A lead or contact taking part in a marketing campaign, with their member status and whether they responded
`salesforce_case`	`document`	A customer support case
`salesforce_case_comment`	`document`	A comment written on a support case, and whether the customer can see it
`salesforce_case_history`		A change to a support case: a tracked field changing, or the case being opened or closed
`salesforce_contact`	`contact`	A person at an account
`salesforce_contract`	`document`	A contract with an account, with its signature and term dates
`salesforce_email_message`	`email`	An email logged against a case or another record
`salesforce_event`	`calendar_event`	A calendar event logged as an activity
`salesforce_knowledge_article`	`document`	One version of a knowledge base article
`salesforce_lead`	`lead`	A prospect not yet converted; on conversion it becomes a contact, an account and optionally a deal
`salesforce_live_chat_transcript`	`document`	The transcript of a live chat between a support agent and a customer, with its timing and the case it belongs to
`salesforce_opportunity`	`deal`	A deal, tracked through pipeline stages
`salesforce_opportunity_contact_role`		A contact’s role on a deal, such as decision maker or economic buyer, and whether they are the deal’s primary contact
`salesforce_opportunity_line_item`	`line_item`	A product line on a deal, with its quantity and price
`salesforce_order`	`order`	An order placed by an account
`salesforce_order_item`	`line_item`	A product line on an order, with its quantity and price
`salesforce_pricebook`		A named price list that sets what products sell for, such as the org’s standard price book
`salesforce_pricebook_entry`		A product’s price in one price book: the unit price, its currency, and whether it is active
`salesforce_product`	`product`	A product the business sells
`salesforce_product_category`		A named category in a product catalog, used to group products
`salesforce_product_category_product`		A product’s placement in a catalog category, including whether it is the product’s primary category
`salesforce_quote`	`document`	A quote for a deal
`salesforce_quote_line_item`	`line_item`	A product line on a quote, with its quantity, price and discount
`salesforce_task`	`task`	A task or logged activity, related to any record and person
`salesforce_territory`		A named sales territory and the regions it covers
`salesforce_user`	`contact`	A person who uses the Salesforce org and owns records
`salesforce_user_role`		A role in the org’s role hierarchy, such as a sales team or management level, and the role above it
`salesforce_user_territory_association`		A user’s membership of a sales territory

Slack

1 evidence type

Evidence type	Description
`slack_message`	A single Slack message: a channel post, direct message or thread reply

Experimental

Coming soon. These evidence types are experimental: the schema is published so you can start sending data, but ingestion, querying, and entity resolution support is limited and the schema may change.

Evidence type	Description
`company`	An organization’s profile — identity, firmographics, and ownership — as recorded in a source system
`contact`	A person’s professional profile — name, role, contact details, and the company they belong to — as recorded in a source system
`deal`	A sales opportunity tracked through a pipeline — its value, stage, outcome, and the people and company it involves
`fact`	Adapter resolves the people and organizations it names against the knowledge graph, creates the ones that are missing, records the relation or attribute as a claim on each, cites the evidence given, and attaches any further corroborating evidence it finds
`lead`	Synced from sources that model leads as records, or inferred from interaction evidence
`task`	Provider-neutral: CRM tasks, Google Tasks, Asana, Todoist and similar flatten into it, with the source system named in provider

All values

Every evidence_type value

All evidence_type values

[
  "article",
  "asset",
  "calendar_event",
  "conversation_message",
  "document",
  "drive_file",
  "email",
  "file",
  "github_comment",
  "github_discussion",
  "github_issue",
  "github_push",
  "github_release",
  "github_repo",
  "hubspot_call",
  "hubspot_company",
  "hubspot_contact",
  "hubspot_deal",
  "hubspot_email",
  "hubspot_invoice",
  "hubspot_lead",
  "hubspot_line_item",
  "hubspot_meeting",
  "hubspot_note",
  "hubspot_order",
  "hubspot_owner",
  "hubspot_product",
  "hubspot_quote",
  "hubspot_task",
  "hubspot_ticket",
  "invoice",
  "line_item",
  "linear_comment",
  "linear_cycle",
  "linear_initiative",
  "linear_issue",
  "linear_project",
  "notion_page",
  "order",
  "product",
  "salesforce_account",
  "salesforce_campaign",
  "salesforce_campaign_member",
  "salesforce_case",
  "salesforce_case_comment",
  "salesforce_case_history",
  "salesforce_contact",
  "salesforce_contract",
  "salesforce_email_message",
  "salesforce_event",
  "salesforce_knowledge_article",
  "salesforce_lead",
  "salesforce_live_chat_transcript",
  "salesforce_opportunity",
  "salesforce_opportunity_contact_role",
  "salesforce_opportunity_line_item",
  "salesforce_order",
  "salesforce_order_item",
  "salesforce_pricebook",
  "salesforce_pricebook_entry",
  "salesforce_product",
  "salesforce_product_category",
  "salesforce_product_category_product",
  "salesforce_quote",
  "salesforce_quote_line_item",
  "salesforce_task",
  "salesforce_territory",
  "salesforce_user",
  "salesforce_user_role",
  "salesforce_user_territory_association",
  "slack_message",
  "video"
]

Getting Started

Core Concepts

Triggers

General

By provider

Experimental

All values

​General

​By provider

​Experimental

​All values

General

By provider

Experimental

All values