> For the complete documentation index, see [llms.txt](https://docs.daylite.app/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.daylite.app/help/mac-fundamentals/german/overview/contact-integration.md).

# Kontakt Integration

Wir wissen, dass der Gedanke, Ihre Kontakte zu importieren, sehr einschüchternd sein kann, vor allem, wenn Ihre Geschäftskontakte in die Hunderte oder gar Tausende gehen. Müssen Sie jeden Kontakt einzeln eingeben? Was passiert, wenn diese Kontakte verloren gehen oder die Informationen nicht korrekt in die richtigen Felder eingegeben werden?

Wenn Sie spüren, wie sich Ihre Brust zusammenzieht, wenn Sie nur daran denken, atmen Sie tief durch und entspannen Sie sich.

Daylite kümmert sich um alles.

Daylite importiert die Informationen Ihrer Kontakte, egal ob es sich um **CSV**-Dateien aus Tabellenkalkulationen oder **vCards** aus Anwendungen wie Apple Contacts handelt und sorgt dafür, dass Ihre Informationen genau dort abgelegt werden, wo sie hingehören.

<figure><img src="https://2322625605-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fzrg5JoZ5dsf4Yyp8vQMZ%2Fuploads%2Fgit-blob-d0cd611dd5d053ecb1fa350405b2c570ea73a6d8%2Foverviewcontact-integration.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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.daylite.app/help/mac-fundamentals/german/overview/contact-integration.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.
