How does OCNORA authenticate with QuestDB?

With a stored Username & password credential, shaped the password (optional), or {"password": "…"}. A connection test can check it when you add it.

What can I automate with QuestDB?

1 typed operation, each with a reference page listing its config fields and the shapes it emits.

What if the QuestDB operation I need is not listed?

Where QuestDB has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.

Are there templates that use QuestDB?

Not yet. Start from a blank workflow, or describe the workflow to Build with AI.

How are QuestDB calls controlled?

Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

QuestDB

Databases & warehousesUsername & passwordConnection test available

Run SQL against QuestDB over HTTP.

OCNORA ships 1 typed QuestDB operation. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.

Ask about QuestDB

Before you connect QuestDB

Authentication: Username & password
Credential: the password (optional), or {"password": "…"}
Connection test: Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.

What you can do with QuestDB

Operations, grouped by what they do to your data.

Create and send 1

Run Query

A sample QuestDB workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no QuestDB trigger is needed.
2
Run Queryquestdb.query
Run SQL against QuestDB over HTTP.

An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.

Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.

Operations 1

Run Query
Run SQL against QuestDB over HTTP.
questdb.query

QuestDB questions

How does OCNORA authenticate with QuestDB?: With a stored Username & password credential, shaped the password (optional), or {"password": "…"}. A connection test can check it when you add it.
What can I automate with QuestDB?: 1 typed operation, each with a reference page listing its config fields and the shapes it emits.
What if the QuestDB operation I need is not listed?: Where QuestDB has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
Are there templates that use QuestDB?: Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
How are QuestDB calls controlled?: Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

See your first QuestDB workflow run.

Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.

Book a technical demo Talk to sales