SQLite
SQLite stores data in a small database that lives in your NappAI account storage, with no servers or credentials. You can add rows, query them with SQL and see which tables the database has.
When to use it
- Keeping a log of what a flow processes, for example each email handled.
- Accumulating data between runs to query it later.
- Having a working table without hiring any database.
Configuration
The Operation field decides what the component does: Add (default) stores the rows in Ingest Data in the table and creates it if it does not exist; SQL runs the query in Search Query; DatabaseInfo describes the database’s tables.
| Field | What it does |
|---|---|
| Operation | What the component does. |
| Database Name (required) | The name of the database. |
| Persist Directory | The storage folder where the database is kept. |
| Table Name (required) | The table. |
| Search Query | With SQL, the query to run, for example SELECT * FROM emails WHERE date >= '2026-10-01'. |
| Ingest Data | With Add, the data to store as rows. |
Advanced options
| Field | What it does |
|---|---|
| Drop Table | With Add, deletes the table and creates it again before storing. Off by default; use with care. |
Output
The Data output holds the rows stored or the query result. The Database Info output holds the description of the tables.
Example
A support service stores every enquiry an agent classifies.
- Add SQLite with Operation set to
Add, Database Namesupportand Table Nameenquiries. - Connect each enquiry’s data to Ingest Data.
- At month end, another flow uses
SQLto count enquiries by topic.
Good practices
- You can download the database from storage to open it with another tool.
Related components
- MySQL: for a database on your own server.