Turso is a fully managed database platform built on libSQL, offering serverless SQLite databases with global replication and low-latency access.
Turso is a fully managed database platform built on libSQL, offering serverless SQLite databases with global replication and low-latency access. On Nagent, Turso is exposed as a fully-configurable databases integration that any agent can call — 3 actions, and API key authentication. No code is required to wire Turso into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Turso to automate the kinds of tasks databases 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 Turso 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 Turso, with input parameters and output schema. Drop these into any step of an agent built in Helix.
TURSO_CLOSEST_REGIONTool to get the closest Turso region based on client location. Use when you need to minimize latency by selecting the nearest deployment region.
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
TURSO_LISTEN_TO_CHANGESListen to committed table changes in a Turso database via the /beta/listen endpoint. This tool streams real-time insert/update/delete events for a specific table. IMPORTANT: Requires a database-specific URL (e.g., 'https://mydb-myorg.turso.io'), NOT the platform API URL (api.turso.tech). Note: The /beta/listen endpoint is NOT available on AWS regions for Free, Developer, and Scaler plans. When unavailable, the action falls back to a /v2/pipeline health check.
Input parameters
Name of the table to listen for changes on (e.g., 'users', 'orders')
Type of change event to listen for: 'insert' (new rows), 'update' (modified rows), or 'delete' (removed rows)
The database-specific URL to connect to (e.g., 'https://mydb-myorg.turso.io'). This is NOT the platform API URL (api.turso.tech). Get this from the 'hostname' field when listing databases via the Platform API.
Optional database-specific JWT token for authentication. If not provided, a token will be automatically generated using the Platform API. You can create one via POST /v1/organizations/{org}/databases/{db}/auth/tokens
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
TURSO_VALIDATE_API_TOKENValidates a Turso API token and retrieves its expiration time. Use this action to verify that an API token is valid and check when it expires. Returns the token's expiration timestamp, or -1 if the token has no expiration.
Input parameters
Validation mode: 'platform' (recommended) validates via the Platform API at https://api.turso.tech/v1/auth/validate and returns token expiration. 'pipeline' validates by executing a health-check SQL query against a database URL (requires a database-specific base_url like https://<db>-<user>.turso.io). 'auto' tries platform first, falling back to pipeline on failure.
SQL statement to execute for health validation when mode is 'pipeline' or during 'auto' fallback. Only used when validating against a database instance.
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 53 agents privately built on Nagent that already use Turso.
Build on Nagent
Connect Turso 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 Turso, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Turso is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Turso is connected, you configure its 3 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Turso 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 Turso event fires, the agent kicks off automatically.
Every Turso 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 Turso ships with 3 pre-built databases actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Turso together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Turso-based workflows tailored to your business.