QuestDB n8n integrationAutomate QuestDB with n8n.
Reading or writing QuestDB rows from a workflow takes a single node. The QuestDB n8n integration carries 2 operations on one resource: Execute Query and Insert. n8n ships no QuestDB trigger, so a Schedule or Webhook node starts the run. Written for builders who already keep an instance up.
Verified Trustpilot reviews · AI, automation & growth agency
What does the QuestDB n8n integration actually do?
The QuestDB n8n integration is one node that opens a database connection to your QuestDB instance and runs SQL on it. Two operations cover the ground. Execute Query sends any statement you write and hands back what the statement returns. Insert takes the items flowing through the workflow and writes them as rows in a table you name. The connection details live in a reusable credential: host, port, database, user, password, plus an SSL mode.
Start with the reporting case, since it is the one people build first. A Schedule Trigger fires every morning, Execute Query runs a SELECT, and the rows leave n8n as a tab in Google Sheets or a message in Slack. The node reads, the rest of the workflow formats.
Then the write side. Items arriving from an n8n Webhook, a form or another system get stored with Insert. You give the table name, list the properties that should become columns, and each item lands as a row. There is a published template, n8n.io/workflows/592, that creates a table and inserts data in the same workflow, which is a decent starting point when the table does not exist yet.
The third case is the quiet one: a scheduled statement that keeps the data usable. Execute Query accepts anything you can write in SQL, so the same node that reads for a report can run the housekeeping statement your team already runs by hand.
One habit to unlearn. On most n8n integrations, when the node lacks the operation you want, the advice is to fall back on the HTTP Request node and call the API yourself. That does not apply here. The QuestDB credential opens a database connection, not an HTTP API, so there is no endpoint to call. The fallback is Execute Query, which takes any SQL statement. The same reflex applies on other database nodes, such as Postgres.
Two limits worth knowing before you draw the workflow. There is no QuestDB trigger, so nothing watches the database on your behalf: every run starts on a Schedule Trigger, on an n8n Webhook called by a third party, or on the trigger of another app. And both operations go through the same credential, so the database account you configure sets the ceiling. Point it at the read-only user from your server config and the workflow reads, nothing else. If you are still weighing platforms, the n8n review goes into the hosting question in more detail.
How do you connect QuestDB to n8n?
- 01
Create the QuestDB credential
In n8n, open the Credentials menu and pick QuestDB. Fill Host with the host name or the IP address of the server, and Database with the database name,
qdbfor example. A credential is a stored set of connection details: you create it once, and every QuestDB node you drop in any workflow after that offers it in a dropdown. - 02
Fill the account and the port
User and Password come from your
server.conf: thepg.userandpg.passwordproperties, orpg.readonly.userandpg.readonly.passwordfor an account meant to read only. A fresh install answers onadminandquest. Port is the port used for this connection,8812by default, so leave it alone unless someone changed it on the server. - 03
Pick the SSL mode, then test it
SSL sets the
sslmodeparameter on the connection and offers three options: Allow, Disable and Require. Save, then drop a QuestDB node into a scratch workflow, select the credential, and run a short Execute Query. A connection problem shows up there, not three nodes later.
What can the QuestDB node do?
The QuestDB node exposes 2 operations. For each one: the node as you configure it in n8n, the required fields, and our field notes.
Execute a SQL query
executeQueryWhat you see in n8n
Notes & use cases
Sends the statement you write straight to QuestDB and returns what it returns. It doubles as the answer when the node has no dedicated operation.
Key parameters
- Query: the SQL to execute, required. n8n expressions work here, and so do
$1and$2paired with query parameters, as inSELECT id, name FROM product WHERE quantity > $1. - Mode: in Additional Fields. Independently runs each query on its own, Transaction executes all of them in a single transaction.
- Query Parameters: a comma-separated list of the properties used as query parameters,
quantity,pricefor the statement above.
Insert rows in database
insertWhat you see in n8n
Notes & use cases
Writes the items reaching the node into a table you name. One item in, one row out, no SQL to write.
Key parameters
- Table: the name of the table to insert into, required. Typed in plain text most of the time, or taken from the previous node with
{{ $json.field }}. - Columns: a comma-separated list of the properties to use as columns for the new rows,
id,name,descriptionfor instance. Append:typeto a name to set that column data type, as inid:int,name:text. - Return Fields: a comma-separated list of the fields the operation gives back.
592 creates the table first, then writes into it.Need help automating QuestDB with n8n?
A person reads every message.
