In the editor, the configuration sidebar shows the Integration action name (e.g., SharePoint List - Read item) and description (Read existing…), so authors do not have to rely on the node name to know what an integration action does. This is the same name and description that authors see in the actions list when selecting an integration. Admins can configure this name and description in the Admin Console by editing the integration configuration.

<aside> 🧩

This is an add-on feature which can be enabled by your BRYTER contact person. For further information, please reach out to them or [email protected]. Additional pricing may apply.

</aside>

Why are integration details useful?

To help with customer support and troubleshooting, the sidebar also shows the integration name and version at the bottom (e.g. SHAREPOINT-LIST 3.0.1). The version number is important for troubleshooting, and upcoming changes will highlight when this is not the latest version.

This update also improves the look and feel of the integration action configuration’s Inputs and Outputs sections.

Integration node overview

[ 1 ] Integration node title

Internal node label or title used for referencing. The title of a node is only visible for authors with collaborator access to the Application containing the module.

[ 2 ] Integration name

This is the name that authors see in the actions tab list when selecting an integration. Admins can configure this name in the Admin Console by editing the integration configuration.

[ 3 ] Integration description

This is the description that authors see in the actions tab list when selecting an integration. Admins can configure descriptions in the Admin Console by editing the integration configuration.

[ 4 ] Input

Required input parameters to trigger the integration. Parameters that are denoted as "(required)" need to be provided - either manually typing or through referencing values - for the integration to run successfully.

[ 5 ] Output

Output parameters provided by the integration.

[ 6 ] Output data type

The Output data type displays the type of value the module receives from the integration. This is especially relevant if your module also contains databases as the fields need to be configured to match the data type when writing records into the database.

[ 7 ] Notes

Use notes to keep a better overview of your module or to add descriptions of the node content. Notes can also be used to leave comments for collaborators or to flag any to-dos.