- Category: databases
- Auth: API_KEY
- Composio-managed OAuth available? N/A
- Tools: 3
- Triggers: 0
- Slug:
TURSO - Version: 20261101_00
Tools
Closest Region
Closest Region
Listen To Changes
Listen To Changes
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
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
Validate API Token
Validate API Token
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
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.