> For the complete documentation index, see [llms.txt](https://docs.jigx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jigx.com/building-apps-with-jigx/data/data-providers.md).

# Data Providers

Utilize the data providers available in Jigx to seamlessly integrate with data from diverse sources, including Jigx's dynamic data store. These providers efficiently handle data inputs and deliver accurate data outputs.

1. [Dynamic Data](/building-apps-with-jigx/data/data-providers/dynamic-data.md) is a Jigx-specific database that automatically syncs data between devices in real time. It is an excellent platform for disposable data, defining data that is not already available in existing systems and how to sync data in real time between users and their devices, regardless of where it is updated.
2. [Microsoft Azure SQL](https://docs.jigx.com/microsoft-azure-sql) is configured to allow secure access, and Jigx functions to read, update, and delete data with queries and stored procedures.
3. [Microsoft OneDrive](/building-apps-with-jigx/data/data-providers/microsoft-onedrive.md) integration allows you to create, update, and delete files in OneDrive. In a solution, you can list and download files from OneDrive onto your device.
4. [REST](/building-apps-with-jigx/data/data-providers/rest.md) provides an overview of working with REST services, including how data is returned, transformed, and used in the solution. This section explains selective data updates and how to configure security and more complex REST calls.
5. [Salesforce](/building-apps-with-jigx/data/data-providers/salesforce.md) allows you to integrate with your Salesforce instance, with access to share data about sales, customers, markets, and more.
6. LOCAL - Stores data locally inside your solution until the app closes.
7. SOAP - works with APIs based on SOAP protocols.


---

# 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.jigx.com/building-apps-with-jigx/data/data-providers.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.