Your company knowledge base, on autopilot
Your company knowledge base, on autopilot On Nagent, Slite is exposed as a fully-configurable documents integration that any agent can call — 16 actions, and API key authentication. No code is required to wire Slite into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Slite to automate the kinds of tasks documents teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Slite into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Slite, with input parameters and output schema. Drop these into any step of an agent built in Helix.
SLITE_ASK_QUESTIONTool to ask a question to your Slite notes in natural language. Use when you need to query or search information across your notes. Supports optional filters to narrow results by parent note or specific assistant.
Input parameters
Question to ask on your notes in natural language
Optional filter to use a specific assistant (for super users only)
Optional filter to only return notes under this parent note id
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SLITE_CREATE_NOTETool to create a note from markdown or HTML content with optional template. Use when you need to create a new note in Slite with specified content and title.
Input parameters
Provide HTML content to fill the note.
Title of the note to create.
Provide Markdown content to fill the note.
Attributes for the parent collection ordered by column. If they don't match the appropriate type, they would be ignored.
If you want to apply a template to the created note.
Below which other note to create this note. If not specified, the note would be created in your personal channel.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SLITE_DELETE_NOTE_BY_IDTool to permanently delete a note and all its children by ID. Use when you need to remove a note irreversibly. This operation cannot be undone.
Input parameters
The unique ID of the note to delete. This will permanently delete the note and all its children.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SLITE_FLAG_NOTE_AS_OUTDATEDTool to set Outdated status on a note with a reason. Use when you need to flag a note as containing outdated information.
Input parameters
Outdated reason explaining why the note is being flagged as outdated.
Note id to update.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SLITE_GET_AUTHENTICATED_USERRetrieves information about the currently authenticated user. Use this to get user details including email, display name, and organization information.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SLITE_GET_NOTE_BY_IDTool to retrieve a complete note by its ID including content in Markdown or HTML format. Use when you need to fetch the full details and content of a specific note.
Input parameters
Specifies content format as either 'md' (Markdown) or 'html'. Defaults to Markdown if unspecified.
Note id to return
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SLITE_GET_NOTE_CHILDRENTool to retrieve note children by parent note ID. Use when you need to fetch child notes beneath a specified parent note. Supports pagination for notes with more than 50 children using cursor-based navigation.
Input parameters
Cursor to use to continue fetching the note children. Only used if current note has more than 50 children
Note ID to fetch its children
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SLITE_LIST_NOTESTool to list notes from Slite with optional filtering by owner. Use when you need to retrieve notes, optionally filtered by a specific user. Supports cursor-based pagination via the cursor parameter.
Input parameters
Cursor to use to continue fetching notes for pagination. Use the nextCursor value from a previous response.
User id to filter notes by owner. If not provided, returns all notes accessible to the authenticated user.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SLITE_SEARCH_GROUPSTool to search for groups by name in Slite. Use when you need to find groups matching a search query. Supports cursor-based pagination via the cursor parameter.
Input parameters
Search query to match against group names
Cursor to use to continue fetching groups for pagination
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SLITE_SEARCH_NOTESTool to search notes based on a query with optional filters. Use when you need to find notes by search term, parent note, review state, or other criteria. Supports pagination and archived note inclusion.
Input parameters
Pagination control for results. Minimum value: 0.
Filters results by note hierarchy level.
Search term for note lookup. Defaults to empty string if not provided.
Number of results per page. Range: 1-100.
Filters by review status.
Filters results to notes under a specific parent note.
Opening HTML/text tag for highlighting query matches in results.
When true, includes archived notes in results. Defaults to false.
Returns only notes modified after the specified date (ISO 8601 date-time format).
Closing HTML/text tag for highlighting query matches in results.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SLITE_SEARCH_USERSTool to search for users in Slite by email, name, or username. Use when you need to find users in the organization.
Input parameters
Search query to match against user email and display name
Cursor to use to continue fetching users for pagination. Used to retrieve the next page of results.
Include archived users in the search results. Defaults to false if not specified.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SLITE_UPDATE_NOTETool to update a note's content with markdown and/or title. Use when you need to modify an existing note's content or metadata.
Input parameters
New html content to fill the note
Title of the note to update
Note id to update
New markdown content to fill the note
Attributes for the parent collection ordered by column
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SLITE_UPDATE_NOTE_ARCHIVED_STATETool to update the archived state of a note in Slite. Use when you need to archive or unarchive a note.
Input parameters
The identifier of the note to modify
Set to true to archive the note, false to unarchive it
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SLITE_UPDATE_NOTE_OWNERTool to update the owner of a note. Use when you need to transfer note ownership to a user or group. Either userId or groupId must be provided.
Input parameters
Note id to update
User id to set as the owner of the note. Either userId or groupId must be provided.
Group id to set as the owner of the note. Either userId or groupId must be provided.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SLITE_UPDATE_TILETool to update or create a tile within a Slite note with structured header and markdown content. Use when you need to update tile information including title, status, content, icon, or external URL.
Input parameters
The tile can be linked to an external URL
Title of the tile
Note id containing the tile id
Status object for the tile.
Tile id to update
The content of the tile. Can be in markdown format.
Icon URL to show in the tile
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SLITE_VERIFY_NOTETool to set a note's verification status to Verified with optional expiration. Use when you need to mark a note as verified or update its verification expiration date.
Input parameters
Expiration of the verification status as ISO 8601 date-time string. Set to null for no expiration.
Note id to update
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 75 agents privately built on Nagent that already use Slite.
Build on Nagent
Connect Slite to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Slite, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Slite is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Slite is connected, you configure its 16 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Slite steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Slite event fires, the agent kicks off automatically.
Every Slite action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Slite ships with 16 pre-built documents actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Slite together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Slite-based workflows tailored to your business.