Skip to main content
The Datum node lets you interact with your Datum collections directly from Brain Studio flows. You can read, create, update, and delete records as part of your automations.
To learn about all Datum features (collections, imports, API Keys, triggers, and MCP), see the complete Datum documentation.

​
What is Datum?

Datum is Jelou’s managed database solution. You do not need to configure servers, manage replicas, or worry about auto-scaling — everything is managed automatically.

Collections

Create and manage your data tables

Records

CRUD, filters, search, and export

Imports

Import data from CSV or XLSX

API Keys

Programmatic access to your data

Triggers

Automatic webhooks for events

MCP

Connect with ChatGPT, Claude, Cursor, and VS Code

Monitor

Performance metrics and activity logs

​
Supported data types

​
Hold the conversation while waiting

By default, while the node waits for Datum to respond, the user is free: if they write, their message is handled by the project router and can start another flow in the same conversation. To prevent this, enable Hold the conversation while waiting at the bottom of the node’s configuration: the user stays in this workflow until the query finishes or the hold expires. The option is available on the Datum node and on the Datum Marketplace node, the Datum node that appears when you build a Marketplace skill.
Messages the user sends while the conversation is held do not enter the flow: they are always discarded, so later nodes —including an AI Agent— will not see what they wrote.

​
How long it lasts

The conversation is released as soon as the node finishes, through either the success or the error output, and the flow continues. As a safeguard, the hold lasts at most the Request timeout you configured; if you did not set one, it lasts 60 seconds. It never exceeds 1 hour.
If you leave the Request timeout empty, the request is not cut: if Datum takes longer than the hold, the user goes back to talking to the router even though the request is still running.

​
When it does not apply

  • Nodes inside a Tool: only the workflow that talks to the user can hold them, so the option is ignored on a Datum node running inside a Tool. In that case, enable it on the workflow’s Tool node; see What is a Tool.
  • Conversations with an operator: if a human agent takes over the conversation, their messages bypass the hold.
  • User already held: if another node —for example, a Pause or a Tool with the same option— is already holding the user, that hold is kept and this node does not replace it.
Tests from the canvas also apply the hold, just like in production.