Node reference
Every node available for building pipelines, grouped by what it is for. Each entry lists what the node accepts, what it produces, and how to configure it.
The node palette in the editor may show additional entries beyond those documented here. Nodes are documented once their behaviour is settled; anything not listed on these pages should be treated as not yet ready for production pipelines.
Getting data in
Most workflows start with an upload page.
Local Upload
Gives the workflow its own upload page where people can submit files. Starting a workflow this way is covered in Using the upload portal.
| Category | Import/Export |
| Input | — (starts a workflow) |
| Output | file |
| Parameter | Type | Default | Description |
|---|---|---|---|
| Headline | text | — | Heading shown on the upload page. |
| Message | text | — | Explanatory text shown under the heading. |
| Require Authentication | boolean | false | Require visitors to sign in before they can upload. |
| Notify when Page Available | boolean | false | Notify users associated with the workflow when the page becomes available. |
The uploaded file is passed on unchanged, as type file. Follow it with
Read CycloneDX or
Read SPDX to parse it before anything else
processes it.
By category
| Page | Nodes |
|---|---|
| Format conversion | Read CycloneDX, Read SPDX, Write CycloneDX, Write SPDX |
| Data processing | Normalize Data, Merge Data |
| Compliance | Verify Licenses, Regulatory Compliance |
| FossID Workbench | Workbench Review, Workbench Report |
| Reporting and review | Generate PDF Report, Send Email Report, Review |
| Database | Database Read, Database Update |
Reading the tables
Input and Output use the data types described in Edges and data flow. They determine which nodes can be connected to which.
Parameters marked required must be set before the workflow will validate. Where a node needs a connection, set it up first — see Setting up connections.