Database

These nodes connect a workflow to a database your organization has registered as a connection — pulling work in at the start of a pipeline and writing results out at the end.

Database Read

Reads data from a database, and starts the workflow when there is something to process.

This node is a trigger: rather than waiting for someone to upload a file, the workflow watches a database and runs on its own.

Category	Database
Input	— (starts a workflow)
Output	sbom
Multiple inputs	No

Parameter	Type	Default	Description
Connection	connection — required	—	The database connection to read from.
Frequency	immediately, hourly, daily, weekly, monthly — required	hourly	How often to check for new data. Checks run on a five-minute interval, so immediately means "at the next check", not instantly.
Processing Mode	New Entries Only, All Entries — required	New Entries Only	Whether to process only entries created after the workflow was created, or everything from the beginning.

caution

All Entries will work through the entire table, which on a large database means a large number of executions. Unless you are deliberately backfilling, New Entries Only is the setting you want.

Database Update

Writes data to a database.

Use it at the end of a pipeline to persist results somewhere you control, rather than relying on the execution's own retained files.

Category	Database
Input	sbom
Output	— (ends a branch)
Multiple inputs	Yes

Parameter	Type	Default	Description
Connection	connection — required	—	The database connection to write to.

Related

• Connections — registering a database.
• Triggers — the other ways to start a workflow.