Slite

Set up an AI agent for Slite that answers from your Slite wiki in your helpdesk, Slack and website chat, links the page it used, and can update your docs.

Give your AI teammate your Slite wiki and it answers from it wherever it works: in your helpdesk, in Slack, on your site. It reads the documents you choose, links the page each answer came from, and can write a page back when you ask it to.

Slite is not self-serve yet. Message us in the in-app chat or email [e-mail] to have it turned on. It does not appear in your Integrations gallery until then.

A wiki page your agent updated, after a person approved the edit.

Quick start

1

Ask your agent to connect Slite

Open the chat in your dashboard and ask it to connect Slite. It points you at your Integrations page and offers to read only the documents you choose.

The agent's answer in the dashboard chat.

Open Integrations in the left sidebar and search for Slite. If Slite is not in the list, it has not been turned on for your workspace yet. Message us and we will turn it on.

Slite in the Integrations gallery.

Open the tile. Connect is in the top right.

The Slite page before it is connected.

2

Connect through Pipedream

Connect opens a window from Pipedream, the service that holds the connection. Continue takes you to a form that asks for a key from Slite. A person creates that key in Slite and pastes it in. Every screen, from Slite's settings to the pasted key, is on Set up Slite.

The Pipedream notice.

Your agent starts copying your documents in straight away, and keeps the copy fresh on a schedule after that.

Check it worked. The integration page header reads Connected, the left sidebar lists Slite, and the Documents source shows a document count.

The connected page, with the wiki already imported.

3

Choose which documents it reads

By default your agent reads the whole wiki. To narrow it, a person chooses the cog on the Documents row. The settings open in a tab. Choose Add Documents to index, enter each document's id, and choose Save Settings. The id is the last part of the document's URL in Slite, so for vostrel.slite.com/app/docs/abc123xyz it is abc123xyz. Everything nested under a listed document is included. From the next refresh, your agent reads only the listed documents.

The Documents source settings. Empty means the whole wiki.

4

Ask it something only your wiki knows

Ask your agent in the chat a question your wiki answers. It searches the imported documents and replies with the answer and the pages it used.

The policy question, answered from the wiki.

The pages it read, listed under the answer.

5

Let it edit the wiki

Ask your agent to change a page. It reads the page first and shows you the edit before it sends it. The frames below show two such edits: a sentence added to the Shipping and delivery page, then a bullet added to the Returns and exchanges page.

The edit, shown before it is sent.

When an edit waits for your OK, it appears as an approval card in the chat and on your Activity page.

The write held for approval.

Approve it and the page changes in Slite. The card records who approved it.

Approved, and the page updated.

The same page in Slite, with the new line.

From Claude Code, Cursor or a terminal. eesel login, then eesel integrations connect slite prints a link to the eesel Integrations page. A person opens it and finishes the key steps on Set up Slite. If the command does not list slite, the workspace has not been turned on for it yet, and a person messages [e-mail]. Afterwards eesel status lists slite as connected with its document count, eesel integrations download list lists the Documents source, and eesel integrations download status slite shows whether the import has finished. eesel integrations slite actions lists the actions with their keys, for example slite-update-doc. A held action returns an approval link that a person opens. Narrowing the document list is a dashboard step for a person. Full command reference: The eesel CLI. From Claude Code or another assistant that connects through MCP: Claude Code and MCP clients.

Sources, triggers and actions

Sources

Source	What your agent reads
Documents	Your Slite documents. The whole wiki by default, or only the documents you list and everything nested under them

Every other integration on your agent is also a source, so a Slite answer can sit beside your website, your helpdesk and your files.

Triggers

Slite has no triggers. Nothing in Slite wakes your agent. Your wiki is knowledge it draws on when it is asked somewhere else.

Actions

Answering a question uses no action. Your agent reads the imported Documents source. The actions below are for browsing the wiki's structure and changing it.

	Action	What it does
Look up	Browse documents	Lists documents, and the documents nested under one
Write	Create document	Adds a new document to your wiki
	Update document	Replaces a document's content with new text

You stay in control the whole way. Adjust your AI agent's access to knowledge and its action permissions to your liking. See Actions and Approvals.

Two things your agent has been taught about your wiki:

• Prefer answering from it to changing it. A wiki is writing people trust, so a write is something you asked for, not something it decided would be tidier. It searches first and proposes updating an existing page rather than adding a near-duplicate.

• Update replaces the whole document. It reads the page before it writes, and sends the full intended text, so nothing that was there is lost.

Troubleshooting

Slite is not in my Integrations gallery?

It is not self-serve yet. Message us in the in-app chat or email [e-mail] and ask to have Slite turned on for your workspace.

The document count is zero or missing pages?

Choose the cog on the Documents row of the integration page. If documents are listed there, only those and their children are imported. Clear the list to import the whole wiki, and check the on/off switch on the Documents row is on. A count that is still climbing is an import in progress. A count stuck at zero with the switch on is worth a message to us.

Your agent answered from an old version?

The copy refreshes on a schedule. Ask your agent in the chat to sync Slite and it pulls the latest versions now. From a terminal, eesel integrations download list lists the Documents source, and eesel integrations download start slite --type documents pulls the latest versions.

FAQ

Can my agent edit my wiki?

Yes, when you ask it to. It can create a new document or replace the content of an existing one.

Where does a Slite answer appear?

Anywhere your agent works: a helpdesk ticket, a Slack thread, the chat bubble on your site, the dashboard chat. The link back to the document comes with it.

Related pages

• Internal Operations for the job your teammate takes on with a company wiki

• Set up Slite for creating the key in Slite, screen by screen

• Knowledge for the other sources it can read from

• Actions and Approvals for choosing what your agent may do

• Set up from Claude Code or the terminal