Connect Your Slite Knowledge Base to Promptless
Promptless reads your Slite workspace when it generates documentation suggestions. Connect Slite with an API key from the Integrations page. Promptless then searches your Slite notes for context each time it creates a suggestion.
The problem
Section titled “The problem”Teams that scope and plan in Slite had to keep that context separate from their documentation workflow. When Promptless generated a suggestion from a merged PR, it could read the diff. It could pull context from Jira or Linear if you connected those tools. Anything stored in Slite stayed invisible.
The gap mattered because the code did not always show decisions your team had already documented. Those decisions included the official feature name and the retry limit settled in a design thread. They also included the reasoning your product team wrote down before engineering started. When Promptless generated documentation, it inferred those details from the diff instead of reading the spec.
The result was documentation that needed more revision than it should have. Some terminology did not match the rest of the product. Some descriptions missed context the team had already worked out.
What it does now
Section titled “What it does now”When you connect Slite as a context source, Promptless searches your workspace for notes related to the current suggestion. It looks for product specs, RFCs, design threads, and other notes that relate to the code being documented.
If a PR description links to a Slite note, Promptless fetches that note’s content directly. You can point the agent at a specific spec by including the link. Promptless reads it while creating the suggestion.
Promptless never writes to Slite. It reads Slite in real time and caches results for the duration of a single documentation session. It then discards the cached results and does not store Slite content.
Who benefits most
Section titled “Who benefits most”Teams that use Slite as their primary internal knowledge base benefit most. If your team writes a spec in Slite before building a feature, Promptless can use it. The spec’s feature name, constraints, and rationale can reach the documentation Promptless generates. The agent reads the spec. It does not infer those details from the diff alone.
This also helps teams keep consistent terminology across documentation. A feature can have an official name decided in a Slite thread. Once you connect the workspace, that name is more likely to appear in Promptless’s output.
How to connect
Section titled “How to connect”Slite uses API key authentication, not OAuth.
- In Slite, go to Settings > API and create a new API key. The key grants read access to all notes visible to that account. We recommend using a service account with appropriate scope.
- Go to the Integrations page in your Promptless dashboard.
- Click Connect on the Slite integration card.
- Enter your API key and click Connect.
Once connected, Slite appears as an available context source in your promptless.yaml. Promptless then uses your workspace for new suggestions.