> For the complete documentation index, see [llms.txt](https://docs.tallygo.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tallygo.ai/context-graph-overview/connect-integrating-your-data-sources.md).

# Connect: Integrating Your Data Sources

The graph's value is proportional to the data flowing into it. The LCG supports multiple data source types, with email and operating systems being the most common starting point, most logistics context lives in inboxes while operational steps live in operating systems.

<figure><img src="https://819938234-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBWPWJvyeCPL5LtfhMI6b%2Fuploads%2FcAHhQKv2ZcwUeWeIYZr8%2Funknown.jpeg?alt=media&amp;token=d0e2a4d0-de24-49ba-83e8-4afdd85ab36e" alt=""><figcaption></figcaption></figure>

#### Document and System Feeds

Documents can be ingested directly via PDFs, spreadsheets, and images from your WMS, TMS, or other systems. Every source passes through the same pipeline, making integration source-agnostic.

#### Email Connectors

The system provides native connectors for Gmail and Outlook / Microsoft 365, including shared mailbox support. Once connected via OAuth, the system continuously syncs new messages using incremental cursors. Users connect once, and the graph stays current automatically.

#### Full Provenance

Every entity in the graph traces back to its origin. When an agent answers "what are the charges on this shipment?", it can also tell you which document and which email thread those charges came from.

<figure><img src="https://819938234-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBWPWJvyeCPL5LtfhMI6b%2Fuploads%2FWqyPaaM0dIeJnm7YudeP%2Funknown.png?alt=media&amp;token=db166d4c-80d9-44b7-8029-b4774b682921" alt=""><figcaption></figcaption></figure>

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tallygo.ai/context-graph-overview/connect-integrating-your-data-sources.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.