> For the complete documentation index, see [llms.txt](https://docs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akinon.com/tutorials/marketplace-dashboard/n11.md).

# N11

This section covers the **N11** marketplace integration in the Marketplace Dashboard: how products are sent, kept up to date, and how to monitor and troubleshoot the related flows.

{% hint style="info" %}
For channel-level setup (feature flags, category mapping, failed integration rules, etc.), see [N11 Marketplace Setup Configurations](/technical-guides/marketplace-dashboard/n11-marketplace-setup-configurations.md) tutorial.
{% endhint %}

## <mark style="color:red;">Flows</mark>

* [**Order Create**](/tutorials/marketplace-dashboard/n11/order-create.md) — Pulls orders from N11 into Omnitron based on specific order statuses, covering both orders that have not been retrieved before and orders that are still sitting in one of the qualifying N11 statuses awaiting retrieval.


---

# 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.akinon.com/tutorials/marketplace-dashboard/n11.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.