> For the complete documentation index, see [llms.txt](https://help.notabase.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.notabase.io/importing-exporting.md).

# Importing / Exporting

## How does importing work?

You can import standard Markdown files into Notabase. If any imported files have the same name as an existing note inside of Notabase, then the existing note will be **overridden**, so be careful.

If you have wikilinks `[[ ]]`  in your Markdown, we also support the wikilink aliases using the `|` symbol, e.g. `[[Note|Note alias]]` will create a note link in Notabase with the text "Note alias" that points to the note "Note".

## How does exporting work?

You can export your notes to standard Markdown.

Notabase features not present in standard Markdown are converted to their best equivalent. For example, note links are converted into wikilinks, and block references are converted to plaintext.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.notabase.io/importing-exporting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.