> For the complete documentation index, see [llms.txt](https://docs.locoia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.locoia.com/data-and-dashboards/dashboards-and-insights/introduction-to-data-sources.md).

# Introduction to Data Sources

You can use Data Sources in Locoia to import data from the apps and systems you use in order to create Transformations, Insights, and Dashboards.

To create a new data source, click on *Data Sources* in the menu and then click on *Create DataSource* in the top left corner:

![Data Sources](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/48063798268/original/27uGM9baxzBjz_8PkgozLC8DJ4BLreypkw.png?1602250302)

Then simply follow the five steps to create a new Data Source:

1. Select the connector (app or system) where your data is stored.
2. Select the account login which you want to use with this connector. If you did not set up a Connector Auth for this connector yet, click *Create a new ConnectorAuth for this Connector* to set it up and come back to this screen afterward.
3. Select the data type which you want to import. If the data type that you want to import is not shown, [contact us](https://dynamicinsight.freshdesk.com/support/tickets/new).
4. (Optional) You can customize the request which is being sent to the connector. This can be useful if you want to in- or exclude certain details.\
   *Note:* If the connector works with views to access data (such as [Freshsales](/connectors/connectors/freshsales.md)), you need to input your individual view id which you want to query.
5. Enter general information about the data source and select how often the data should be refreshed (Scheduling interval); for most business purposes refreshing daily is ideal.

Your Data Source will now be shown in the Data Source overview and you can use the Data Source to create Transformations, Insights, and [Dashboards](/data-and-dashboards/dashboards-and-insights/introduction-to-dashboards.md).

{% hint style="info" %}
It might take a minute until the first data can be queried, and multiple hours, depending on the amount of data, until all your data is imported.
{% endhint %}

In the Data Source overview, you can see all your Data Sources, their current status, when they have last been refreshed, and more. You can also edit your Data Sources, adjust the Data Source's sharing settings, and even reimport the entire Data Source.

{% hint style="warning" %}
When you reimport a Data Source, all existing data will be deleted from this Data Source and depending of the amount of data present in your system, it might take multiple hours after the reimport is completed.
{% endhint %}


---

# 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.locoia.com/data-and-dashboards/dashboards-and-insights/introduction-to-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.