Skip to main content

​
What this means

A data source is the record or document that supports the work: a product catalog, a knowledge-base document, an incoming message, or an order record available to the workflow. These are not interchangeable. A conversation can describe a request; it should not replace the authoritative record for price, stock, certification, or order status.

​
What to configure and check

Use the relevant product, knowledge-base, or connected-system surface that your account provides. Before a test:
  • Identify the owner and system of record for each fact.
  • Check organization scope, record identifiers, units, revision, and update time.
  • Check that the workflow can actually retrieve the intended material.
  • For documents, distinguish upload from processing, indexing, review, and publication. Do not assume these stages are one operation.
  • Exclude documents or personal information the workflow does not need.
These checks are an operating checklist, not a claim that Agents has a universal source-import screen.

​
How it connects

Integrations may deliver or expose the source. Context determines which relevant information is used for a particular task. Approvals require the reviewer to compare the proposed action with that evidence.

​
Example

For a material-property question, identify the current datasheet and the relevant test condition. If an older email contradicts it, resolve the discrepancy instead of choosing whichever value is convenient. A lesson about answer wording must not store the property value itself.

​
When information is missing

Clarify the request or ask the source owner to correct the record. Do not infer a current price, compliance claim, inventory quantity, or lead time from a similar product or an earlier conversation.