<< Click to Display Table of Contents >> Navigation:  Low-code Process Automation > Studio Cloud - Authoring environment > Bizagi Studio > Integrating external applications from Bizagi > Bizagi connectors > Integration Hub > Creating connectors > Connectors concepts and guidelines > Connector Editor: Naming attributes

Introduction

Starting with Fall 25, the Connector Editor for Custom and REST connectors in Bizagi Studio allows you to use clipboard actions when editing the names of attributes.

 

This capability helps you work more efficiently when creating or maintaining connector structures. To help ensure successful mapping and execution, it is recommended that attribute names follow the supported naming conventions described in this article.

 

Edit attribute names using the clipboard

You can use standard copy and paste actions to enter or update attribute names in the Connector Editor.

1.Open the Connector Editor.

2.Create a new action or select an existing one.

3.Go to the Inputs or Outputs section.

4.Add a new attribute or select an existing attribute.

5.Copy the desired name to your clipboard.

6.Paste the value into the attribute name field.

 

Using the clipboard can help maintain consistent naming conventions across connector definitions.

 

Supported attributes

These recommendations apply to:

•Input attributes

•Output attributes

•Attributes inside Object structures

•Nested Input and Output attributes

 

Naming recommendations

To help ensure compatibility during mapping and execution, use names that contain only:

•Letters

•Numbers

•Underscores (_)

•Hyphens (-)

 

When editing attribute names, consider the following recommendations:

•Use clear and descriptive names.

•Apply a consistent naming convention throughout the connector structure.

•Review values copied from external applications before pasting them into the Connector Editor.

•Review values inserted through operating system clipboard features, such as clipboard history tools.

•Ensure nested attributes follow the same naming conventions as parent attributes.

•Avoid using emojis or special characters other than underscores (_) and hyphens (-).

 

Recommended examples

CustomerId

customer_name

AddressLine1

Output_Status

API-Response

customer_email

OrderNumber

Response_Code

Contact-Phone

 

Examples to avoid

customer😀

order#

response@

name$

 

Using recommended naming conventions helps ensure that connector structures are easier to understand, map, maintain, and execute.

Last Updated 7/1/2026 4:16:17 PM