Connections Screen
The Connections screen lists every Connection in the current Site across v1 Runtime and v2 Runtime. Use it to find, organize, create, rename, move, export, or delete Connections.
Create actions
When you have Connection create permission, the screen displays separate actions:
New v1 Connectionopens the v1 Runtime Connection flow.New v2 Connectionopens the v2 Runtime Connection details screen.
The new Connection is created in the current folder. If the Site has no Connections, the same actions appear in the empty state.
Explorer controls
The screen uses the shared explorer controls:
| Control | Behaviour |
|---|---|
| Breadcrumbs | Navigate the Connection folder hierarchy. |
| Search | Matches Connection name, key, internal Node name, Node version, and resolved Node display name. |
| Filters | Limit results by recently used, recently changed, v1 Runtime, or v2 Runtime. Filters can be combined. |
| Grid or table layout | Changes how the same filtered results are presented. |
| Star | Adds a Connection or folder to your personal starred view. |
| Selection | Selects Connections and folders for available bulk actions. |
| Refresh | Reloads Connections and published Node information. |
A v2 Runtime badge identifies v2 Runtime Connections. Each grid card and table row shows the Node display name and the exact Node version saved on the Connection.
Folder and item actions
Available actions depend on your permissions:
| Action | Required capability and effect |
|---|---|
New folder |
Creates a Connection folder at the current location. |
Rename |
Renames a selected Connection or folder. Connection rename loads and saves the shared record through the first-ranked Environment. |
Move to |
Moves selected Connections or folders to another Connection folder. |
Delete |
Deletes selected Connections or empty folders after confirmation. A Connection deletion removes values from all Environments. |
Selecting a folder for deletion also selects its contained items and nested folders. The explorer processes deeper folders first, but the backend still requires a folder to be empty before it can be removed.
Columns and exported data
The Connection-specific columns are Node name and Node version. Shared explorer fields provide the Connection name, path, key, modified information, and last-use information where available.
Use Download all CSV to export the current Connection data. The file includes:
- URL and folder path.
- Connection key and name.
- Node internal name and Node version.
- Last changed and last used timestamps.
The export describes Connection identities. It does not contain Environment-specific values or credentials.
Permissions
You need Connection list permission to open the explorer. Creating and renaming also require Environment list plus Connection read and write permissions. Deletion requires Connection delete permission; folder actions use their corresponding folder permissions.
Environment-scoped permissions do not hide the shared Connection identity from a user who can list Connections. They control whether that user can load and save the protected values for a particular Environment.
Automatic health checks
Flowgear records automatic Connection health checks separately for configured Environments. A successful test is evidence of the Node's test operation at that time; it does not establish that every Workflow operation will succeed.