> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/outsmart-knowledge-base/outsmart-knowledge-base-nl/integraties/integraties/jortt.md).

# Jortt

Koppel OutSmart aan Jortt om klanten te importeren en voltooide werkbonnen als facturen te exporteren.

## Jortt

**Jortt** verbindt OutSmart met uw Jortt-administratie.

Gebruik deze sectie om de Integratie te koppelen en te beheren wat er in en uit wordt gesynchroniseerd.

#### In deze handleiding

* **Wat is Jortt?**
* **Jortt instellen**
* **Jortt-imports configureren**
* **Jortt-exports configureren**
* **Problemen met Jortt oplossen**

#### Wat u met Jortt doet

* Klanten importeren uit Jortt naar OutSmart Relaties
* Voltooid Werkbonnen exporteren naar Jortt als Concept Facturen
* Nieuw Klanten Aanmaken in Jortt vanuit OutSmart wanneer nodig

#### Aanbevolen volgorde

1. Begin met **Wat is Jortt?**.
2. Daarna **Jortt instellen**.
3. Stel daarna **importen** en **exporten**.
4. Gebruik **Problemen met Jortt oplossen** wanneer een synchronisatie mislukt.

#### Gerelateerde onderwerpen

* **Stel een software-integratie in**
* **Wat zijn Integraties?**
* **FAQ over Integraties**


---

# 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://knowledge.out-smart.com/outsmart-knowledge-base/outsmart-knowledge-base-nl/integraties/integraties/jortt.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.
