Get started
View the Duaer data pool
In Duaer, the data pool lists deliverables from successful production runs of digital employees. The sidebar item sits under Digital employees. Manual test runs do not write here.
What the data pool holds
After a successful production run, Duaer stores the output items of the deliverable node in the project data pool. The deliverable is the last main node that finished successfully; AI sub-nodes such as models, memories, and parsers never count.
Only production runs are stored: trigger, webhook, retry, CLI, and runs called by another workflow. Manual canvas tests, error workflows, chat, agent, and evaluation runs are skipped. At most 500 items per run; oversized items are stored as a truncation marker.
The instance must have the data-pool module on. The sidebar opens the pool for the personal Digital employees space.
Open and browse
- In the left sidebar, under Digital employees, select Data pool. The page title is Data pool.
- Filter by digital employee and by acceptance status (pending, accepted, rejected).
- Columns include Time, Digital employee, Deliverable node, Acceptance, plus item fields. Pending rows offer Accept or Reject (reject needs a short note).
- Rows are newest first. Select the time to open that execution. When more remain, select Load more.
The empty state says deliverables from successful production runs appear here pending acceptance.
Acceptance steps: Accept deliverables in Duaer.
Records stay after executions are pruned or deleted. Deleting the project deletes its pool records.
How it differs from data tables and executions
- Data pool: automatic deliverables from production runs, for viewing and filtering by digital employee. There is no edit, delete-one, or export in the pool today.
- Data table: a table you create in the project and read or write with the Data table node. Refer to Keep rows in a Duaer data table.
- Executions: every run history, including manual tests. Refer to Read executions in Duaer.
Questions
Why is the Duaer data pool empty after Execute on the canvas?
Manual test runs do not write to the pool. Publish and run successfully via a trigger, webhook, or other production path so deliverables appear.
Is the Duaer data pool the same as a data table?
No. The data pool collects production deliverables automatically. A data table is a table you create and access with the Data table node.
In this section
Accept deliverables in Duaer
In Duaer, production deliverables in the data pool start as pending. Accept or reject them so delivery is complete.
Get startedDuaer data catalog
External data Duaer can fetch, what you get, and the price. Add a node from the Duaer Data category in the node creator, or give an agent the skill.
Get startedKey concepts in Duaer
In Duaer a workflow is the canvas flow, and a digital employee is the side that delivers a result. Nodes, credentials, expressions, and plans are on this page.
Get startedCreate your first digital employee in Duaer
In Duaer, create a digital employee: write instructions, pick a model, publish, then open a chat and accept the result. The UI may label the control Agent.
DataKeep rows in a Duaer data table
In Duaer, a data table lives in the current project. A new table stays closed to other workflows until you grant one of them view or edit. A table that already exists stays open until that first grant.