SQL Database component (AI Flowi Workflow)
SQL Database executes SQL queries on SQLAlchemy-compatible databases. Its exported result is a Table, so plan the receiving port before connecting a query to later processing.
SQL Database is documented in the catalogue; not production-tested by Ai Flowi.
By Ai Flowi · Published
Catalogue reference
This SQL reference uses the AI Flowi Workflow 1.9.2 catalogue exported 9 October 2026, specifically data_source.SQLComponent. Catalogue description: Executes SQL queries on SQLAlchemy-compatible databases.
Browse the SQL Database catalogue entry.
Related: Natural Language To SQL.
Inputs
database_url and query are the two required fields; both accept Message connections. The boolean fields have no accepted-input-type metadata, shown as “Not listed”.
| Name | Type | Required | Accepted input types | Plain explanation |
|---|---|---|---|---|
add_error | bool | No | Not listed | Boolean setting named add_error; error formatting and its default are not described. |
database_url | str | Yes | Message | Required database connection URL; a Message is the listed accepted connection type. |
include_columns | bool | No | Not listed | Boolean setting named include_columns; the export does not explain its effect on the result. |
query | str | Yes | Message | Required SQL query text, also connectable from a Message. |
Outputs
| Display name | Name | Type |
|---|---|---|
| Result Table | run_sql_query | Table |
Result Table is the display label for run_sql_query, whose declared type is Table. No separate error port or JSON output is listed for SQL Database.
When to use SQL Database
Choose SQL Database when the source is a database and you already have a SQL query to execute. For a text-processing step after the result, Parser.input_data lists Table as accepted; inspect the returned columns before defining the next configuration.
When to choose another component
For an HTTP endpoint, follow API Request rather than configuring a database URL. For work on an existing JSON object, consult JSON Operations; for a Table-to-JSON conversion, inspect Type Convert before using a JSON-only processor.
Example configuration
example configuration, not a recorded test
{
"database_url": "YOUR_DATABASE_URL",
"query": "SELECT 1 AS sample_value;"
}Replace YOUR_DATABASE_URL locally with the connection URL for a database you are authorized to query. The constant SELECT is an illustrative starting query; no database connection, returned row or supported driver was verified for this page.
For SQL connection credentials and variables, read Connections and models and variables.
Limitations
- SQLAlchemy compatibility is the catalogue scope, not an exported list of database engines or installed drivers. The source gives no connection-string examples, TLS controls or network requirements.
- add_error does not establish exception recovery, sanitized errors or an error branch. Confirm failure handling before exposing query results or error details to another system.
- include_columns has no documented default or output-layout definition; a column-name setting alone does not establish the structure of Result Table.
- No parameter-binding input, transaction control, row limit or timeout setting appears among the four exported fields. Use a controlled query and database permissions appropriate to the task; this reference supplies no write, rollback or injection-protection guarantee.
- Select Data.data_list and Filter Data.data list Data and JSON, without Table. A direct connection from Result Table to either input is not supported by the exported type lists.
Node usage
For SQL workflow usage, consult pricing and the cost guide.
Related components
API Request · Parser · Type Convert · Select Data · Filter Data