Slite
Read, write, search and curate Slite notes, ask questions of your knowledge base, and look up users and groups.
About
Slite ships in the w6w first-party pack. It declares 23 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.slite- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Productivity · Documents & Files · AI & Machine Learning
Overview
Slite is a team knowledge base: notes organised under channels and parent notes, with owners, review states and an AI that answers questions from what the team has written. This app lets a workflow work with that knowledge base the way a person would.
It can create, read, update, archive and delete notes in Markdown, HTML or Slite’s own SliteML format, list a note’s children, search notes with review-state and date filters, and push structured content into a tile inside a note. It can set a note’s owner, mark it Verified (with an optional expiry) or flag it as Outdated with a reason, and page through the knowledge-management views that surface stale, public, inactive and empty notes.
It can also ask Slite a question in natural language and get back an answer with its sources, polling the answer thread when Slite needs longer than its synchronous deadline, and look up users and groups to resolve who owns what. Slite publishes a status page but no machine-readable feed, so health is tracked by an unauthenticated reachability check on the API plus the credential check.
Build with Slite
Three routes to the same 23 actions. The Workflow tab is generated from Slite's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Ask a Question
ask Ask Slite a question in natural language and get an answer with its sources. When Slite needs longer it returns a thread id to poll with Get Thread.
List Empty Notes
km-empty-note-list List empty notes for knowledge management, filtered by owner and channel.
List Inactive Notes
km-inactive-note-list List inactive notes for knowledge management, filtered by owner and channel.
List Knowledge-Management Notes
km-note-list List notes for knowledge management, filtered by review state, owner, channel and recency.
List Public Knowledge-Management Notes
km-public-note-list List public notes for knowledge management, filtered by review state, owner, channel and recency.
Get Authenticated User
me-get Return the user the API key belongs to, with their organization's name and domain.
List Note Children
note-children-list List a note's direct children, or its whole subtree flattened.
Create Note
note-create Create a note from Markdown, HTML or SliteML content, from a template, or empty.
Delete Note
note-delete Permanently delete a note AND all its children. Irreversible — archive instead if unsure.
Update Note
note-update Replace a note's content and/or title, set collection attributes or its position.
Get Thread
thread-get Read an ask thread: its status and every question and answer round. Use it to poll an answer that Ask returned as processing.
Update Tile
tile-update Update (or create) a tile block inside a note with a title, status, link and Markdown content.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Slite's real ids.
{
"manifestVersion": "2",
"name": "slite-example",
"steps": [
{
"id": "ask",
"uses": {
"app": "io.w6w.slite",
"action": "ask",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"question": "<question>"
}
}
]
}Here are some of the things you can do
-
Ask a Question
readask -
Get Group
readgroup-get -
Search Groups
searchgroup-search -
List Empty Notes
searchkm-empty-note-list -
List Inactive Notes
searchkm-inactive-note-list
+18 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Slite, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Slite. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "ask",
payload: {
question: "<value>",
// parentNoteId: "<value>",
// assistantId: "<value>",
// wait: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action ask --payload '{"question":"<value>"}'Give an AI agent Slite — without giving it Slite's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.slite#ask",
"input": {
"question": "<question>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Slite connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Slite's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Slite itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Slite declares its own checks, so its health is a property of the app rather than something the host guesses at.
Slite platform status
API reachable
Unauthenticated GET https://api.slite.com/v1/me. A 401 carrying Slite's JSON `{"id": …, "message": …}` passes — it proves the API and its auth layer are answering. Credential validity is the derived `auth:*` check's job.