Query tools in the console
Each database page in the console has tabs: Connect, Query, Import, Export, Activity, Metrics and Backups. This page covers the ones you use to work with data.
Console queries are real requests: they count against your allowance and rate limits like any other, and follow your organization’s IP allowlist.
Query editor
The Query tab runs one Cypher statement at a time against the database.
- Run with ⌘/Ctrl + Enter; Explain with ⌘/Ctrl + Shift + Enter, which shows the plan without running the query.
- Parameters: when the statement uses
$nameparameters, a form appears for their values. Prefer parameters to pasting values into the text. - Your role decides what runs: owners, admins and developers run reads and writes; members run read-only queries; billing members and viewers don’t query.
- An empty database offers Load sample dataset (a small movies graph) and a few guided first queries.
Results
| View | Shows |
|---|---|
| Table | One row per result row, one column per RETURN column |
| JSON | The raw response, as the HTTP API returns it |
| Graph | Every node and relationship found anywhere in the rows, laid out as a graph |
The graph view supports pan and zoom, colours and captions per label, an
inspector for the selected node or relationship, and Expand neighbours,
which fetches up to 50 neighbours of a node. It draws at most 300 nodes; add a
LIMIT for larger results.
Results export as CSV (values that a spreadsheet would treat as formulas are neutralised) or JSON.
Schema browser
Next to the editor: labels, relationship types, property keys from indexes and constraints, and the indexes and constraints themselves. Click a name to insert it, or the run icon for a sample query. Counts and the full list of property keys run a query only when you ask for them.
Saved queries and history
- Saved queries belong to the organization: anyone who can query saves one (⌘/Ctrl + S); its author, owners and admins edit or delete it. Up to 200 per organization.
- History keeps your last 100 statements in this browser only (per user and organization). It is never sent to NamiDB. Alt + ↑ / ↓ walks through it.
Activity
Owners, admins and developers see the Activity tab:
- Running queries: every statement running on the database right now,
from any client (HTTP, Bolt, MCP or the console), longest first, with a
Cancel button. A cancelled statement stops at its next check, within
milliseconds, and its client gets a
cancellederror. The same is available on the HTTP API. - Slow-query log: statements over HTTP, Bolt, MCP and the console that took
longer than one second, kept 7 days. Each entry has its duration, time in
the engine, row count, outcome and source (an API key’s prefix, or the
console user), and a preview of the statement with string and number
literals replaced by
?. Parameters are never recorded. View entries one by one, or grouped by statement shape to find the queries worth an index.
For a Bolt statement, the duration runs from the statement to the end of its result stream, so a client that reads slowly counts too.
Watching the Activity tab never wakes an idle engine.
Metrics
The Metrics tab charts the database’s requests (reads and writes), errors, latency (p50 and p95) and data transfer over time, from the same counts that billing uses. The organization’s Usage page shows the totals against the plan’s allowances, with the estimated overage when the spend cap is off.
Connect
The Connect tab shows the database’s HTTPS endpoint and Bolt URI and ready-to-copy snippets for curl, the JavaScript and Python SDKs, and the Neo4j drivers.