> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/import-tool/import-setup-and-jobs/imports/creating-streams.md).
# Creating Streams
Create an import stream and define its source connection, keys, and target entity type.
A stream connects one source record type to a target entity type in Emporix. You can have multiple streams in one import.
{% hint style="info" %}
Before you create a stream, complete the [prerequisites](/import-tool/import-setup-and-jobs/prerequisites.md) and set up a [connection](/import-tool/import-setup-and-jobs/connections.md) to the source system.
{% endhint %}
{% stepper %}
{% step %}
#### Open the import
In **Imports**, choose **Edit** on an existing import.
{% hint style="warning" %}
If you do not have an import yet, first [create an import](/import-tool/import-setup-and-jobs/imports.md#creating-an-import), then continue from its details view.
{% endhint %}
{% endstep %}
{% step %}
#### Add a stream
Choose **+ New stream**.
{% endstep %}
{% step %}
#### Enter the stream details
* **Name** – a label for the stream
* **Connection** – the [connection](/import-tool/import-setup-and-jobs/connections.md) that points to the source system
* **Source record** or **Resource name** – the record type to import. Celonis connections use **Source record**. HTTP / REST API connections use **Resource name**, plus **Method**, **Path**, **Records path**, **Response format**, and **Pagination method**.
* **Key field** and optional **Candidate key fields** – choose the fields used to match records. See [Key resolution](/import-tool/import-setup-and-jobs/imports/configuring-streams.md#key-resolution).
* **Target** – the target kind in Emporix, for example `emporix.customEntity`
* **Target type** – an existing type, or a new type you enter
{% hint style="info" %}
For an HTTP stream, the **Path** is appended to the connection **Base URL**. If the **Base URL** is only the host, enter the list path here, for example `/countries/v5`. Set **Records path** to the array in the JSON response, for example `data.objects`, or **(response is the array)** when the body is the array.
{% endhint %}
After you save your setup, the stream appears in the list.
New Stream dialog where you set the connection, source record, key fields, and target type
{% endstep %}
{% step %}
#### Continue with stream configuration
Open the stream row and continue with [stream configuration](/import-tool/import-setup-and-jobs/imports/configuring-streams.md). Then define how fields are written in [Field Mapping](/import-tool/import-setup-and-jobs/imports/field-mapping.md).
{% endstep %}
{% endstepper %}
{% hint style="success" %}
Use a clear stream name that describes the source and target, for example `Payment Intents` or `AP Invoice -> PO/NON_PO`. This makes it easier to monitor status and errors later.
{% 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://developer.emporix.io/import-tool/import-setup-and-jobs/imports/creating-streams.md?ask=&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.
