Skip to main content

Setting up connections

Several nodes need to reach an external system. Rather than putting credentials into each node, you register the system once as a connection and point nodes at it.

Connections belong to the organization, so one setup serves every workflow and everyone in the organization.

Adding a connection​

Go to Connections and add one, choosing the type you need. Each type asks for different details.

Database​

A PostgreSQL database belonging to your organization, used by the Database Read and Database Update nodes.

You will need the host, port, database name, and credentials. These are encrypted at rest.

The account you provide needs read access for Database Read and write access for Database Update — grant only what the workflows actually require.

FossID Knowledge Base​

The FossID reference data that component and license information is checked against. Used by:

You will need the Knowledge Base endpoint and your FossID credentials.

FossID Workbench​

A FossID Workbench instance, used by the Workbench nodes. You will need the Workbench URL and credentials with permission to run the operations your workflows will perform.

Both Workbench nodes offer a test-connection command, which is a useful way to confirm a new connection works before building a pipeline on top of it.

Checking a connection​

Each connection shows a status: active when it is working, pending when it has not been verified, inactive when disabled, and error when the last attempt to use it failed.

An error status usually means credentials have changed, access has expired, or the host cannot be reached from Workflows.

When a connection breaks​

Workflows using a broken connection fail at the node that needs it. If runs that used to work start failing at the same node, check that connection before looking at the workflow itself.

Updating a connection takes effect for subsequent runs; executions already in flight are not retroactively fixed.