# Quickstart

<figure><img src="/files/JbPpmym2xcqWdcrm4IYR" alt=""><figcaption></figcaption></figure>

**There are four basic steps to build an end-to-end flow on Context Data**

1\). Source Connection: Build connection(s) to where your source data resides (e.g. MySQL, PostgreSQL, Amazon S3)

2\). Embedding Model: Create a link to the embedding model which will convert data retrieved from the source to vector embeddings (basically an array of numbers)

3\). Target Connection: Build connection(s) to where the vector embeddings will be saved (and where your AI application will read from)

4\). Flow: The flow ties of the steps above (source connection, embedding model and target connection) into an end-to-end process ready to be executed.

Basically, when a flow is triggered, it will:

* Get the data from the source connection that you defined
* Convert the retrieved data to a format optimized for vector search
* Write the converted data to the vector database/store&#x20;

{% embed url="<https://www.youtube.com/watch?v=7wXk_kATjFQ>" %}


---

# Agent Instructions: 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:

```
GET https://context-data.gitbook.io/context-data-1/quickstart.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.