Skip to main content
Turso logo
  • Category: databases
  • Auth: API_KEY
  • Composio-managed OAuth available? N/A
  • Tools: 3
  • Triggers: 0
  • Slug: TURSO
  • Version: 20261101_00

Tools

Slug: 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

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: TURSO_LISTEN_TO_CHANGESListen for committed insert, update, or delete events on a table in a Turso database, using its database-specific URL. Returns up to 25 nonempty event lines.

Input Parameters

string
required
Name of the table to listen for changes on (e.g., ‘users’, ‘orders’)
string ("insert" | "update" | "delete")
required
Type of change event to listen for: ‘insert’ (new rows), ‘update’ (modified rows), or ‘delete’ (removed rows)
string
required
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.
string
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

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: TURSO_VALIDATE_API_TOKENValidate the configured Turso API token through the Platform API and retrieve its expiration information. Pipeline mode checks a database using a configurable SQL statement, which can modify data; it does not provide token expiration information.

Input Parameters

string
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.
string
SQL statement to execute for health validation when mode is ‘pipeline’ or during ‘auto’ fallback. Only used when validating against a database instance.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not