> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atako.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Slite

> Connect Slite to your Atako agents — 7 read and 5 write actions.

Let your agents search, read, create and update the notes of your Slite knowledge base, ask questions in natural language, and keep documentation verified or flagged as outdated.

## Connection

* **Authentication**: API key.

<Note>
  Open your organization menu at the top left of the Slite app → Settings → API → Create a new key. The key is shown only once, so copy it immediately.

  See [Slite's documentation](https://developers.slite.com/docs/getting-started).
</Note>

## Read actions (7)

| Action | Description |
| - | - |
| `ask` | Ask a question in natural language; Slite answers from the notes the key's user can read and cites its sources. A long answer comes back as status "processing" with a threadId — read it afterwards with get\_thread. |
| `get_current_user` | Get the user the API key belongs to. Probe action — no arguments required. |
| `get_note` | Read one note with its content, as Markdown (default) or HTML. |
| `get_thread` | Read an ask thread back as question/answer rounds — the way to collect an answer that came back as "processing", and to re-read a past conversation. |
| `list_note_children` | List the children of a note — use it to walk the documentation tree. Paginate with the cursor returned by the previous call. |
| `list_notes` | List notes, optionally under one parent, in a chosen order. Paginate with the cursor returned by the previous call. |
| `search_notes` | Full-text search across the notes the key's user can read. Every argument is optional; an empty query returns the most relevant notes. |

## Write actions (5)

| Action | Description |
| - | - |
| `archive_note` | Archive or unarchive a note. Arguments: noteId (string, in the path) and archived (boolean, required — true archives, false restores). Reversible: this is not a deletion. |
| `create_note` | Create a note. Arguments: title (string), parentNoteId (string, optional — the note is created in the key user's personal channel when omitted), and the content as either markdown (string) or html (string), never both. |
| `flag_note_as_outdated` | Flag a note as Outdated. Arguments: noteId (string, in the path) and reason (string, required — why the note is out of date). |
| `update_note` | Replace the title and/or the whole content of a note. Arguments: noteId (string, in the path), title (string, optional), and the new content as either markdown (string) or html (string), never both. Content is replaced, not appended — read the note first if you mean to extend it. |
| `verify_note` | Mark a note as Verified. Arguments: noteId (string, in the path) and until (required — an ISO 8601 date-time string when the verification expires, or null for no expiration). |

## Permissions

Every action above must be explicitly granted to an agent before it can be used. See [Permissions](/integrations/permissions) for the grant model and [Security](/integrations/security) for how credentials are protected.

***

*Last reviewed against the provider API: September 2026.*


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.