> For the complete documentation index, see [llms.txt](https://data-tiles.gitbook.io/latttice-how-to-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://data-tiles.gitbook.io/latttice-how-to-guide/how-to-guides/getting-started.md). # Getting Started Before you can start creating Data Products using **Latttice CoPilot**, the first step is to connect your data sources. This involves adding your data sources through the **Data Sources** section in Latttice, where you’ll configure and authenticate the connections. Setting up your data sources ensures that Latttice has the necessary access to fetch, manage, and process the data you’ll use to build Data Products. The guide below provides a step-by-step walkthrough of how to securely add and configure your data source(s), ensuring a seamless integration process so you can quickly start leveraging the full capabilities of Latttice. Latttice offers over **30+ connectors** to the most common analytical systems, enabling seamless integration with your existing data infrastructure. These connectors make it easy to connect to popular platforms like cloud data warehouses and databases, allowing you to start working with your data quickly. Latttice supports both structured and unstructured data sources, meaning you can connect everything from SQL-based systems to documents like PDFs, Word files, and more - making your entire data landscape accessible and actionable. If your desired data source isn’t included in our existing connectors, you can also upload your own data directly into Latttice. Additionally, if a specific data source connection is not currently available, don’t hesitate to reach out to our team—we’re happy to investigate the possibility of creating a custom connector to meet your needs. This ensures that Latttice can adapt to your unique data ecosystem. Below is a guide on connecting your Structured Data Source to Latttice. {% embed url="" %} In addition to connecting to a data source through one of Latttice’s pre-built connectors, you also have the flexibility to upload data files directly into the platform. This option is ideal for working with ad hoc datasets, custom data exports, or files that are not part of an integrated system. The file upload process is simple and user-friendly, allowing you to quickly add data in a CSV format. Once uploaded, your data is immediately available to use within Latttice for creating Data Products. The guide below provides a step-by-step walkthrough to help you seamlessly upload and configure your files. {% embed url="" %} Once the file has been uploaded. You can also add more files to the same File Data Source that has been created. Below is a guide that outlines the steps you will take to do this. {% embed url="" %} Connecting to unstructured data—like PDFs, Word documents, or website content—has traditionally been a challenging task. Latttice simplifies this process by allowing you to securely access and work with these types of sources directly within the platform. This unlocks valuable information that was previously difficult to use, helping you enrich your Data Products with broader and more diverse insights. Below is a guide to walk you through the steps needed to connect Latttice to your unstructured data, in this example, a website. {% embed url="" %} --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://data-tiles.gitbook.io/latttice-how-to-guide/how-to-guides/getting-started.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.