Actions45
- Evento Actions
- Criar Evento De Acesso Concedido
- Criar Evento De Aguardando Pagamento
- Criar Evento De Boleto Impresso
- Criar Evento De Carrinho Abandonado
- Criar Evento De Nota Nps
- Criar Evento De Pacote Aguardando Retirada
- Criar Evento De Pacote Saiu Para Entrega
- Criar Evento De Pedido Cancelado
- Criar Evento De Pedido Despachado
- Criar Evento De Pedido Entregue
- Criar Evento De Pedido Estornado
- Criar Evento De Pedido Pago
- Criar Evento De Pedido Processando
- Criar Evento De Pesquisa Nps
- Criar Evento De Progresso De Envio
- Criar Evento De Redefinicao De Senha
- Gerenciamento Da Conta Actions
- Grupo De Variável Customizada Actions
- Integração Actions
- Lead Actions
- Lista De Lead Actions
- Variável Customizada Actions
Overview
The provided source code snippet is minimal and does not include the implementation of the execute() method or any logic related to the "Editar Variável Customizada" (Edit Custom Variable) operation. It only shows a class constructor that sets the node description by importing it from another module. Therefore, based on the available information and the provided properties, this node likely allows users to edit a custom variable within a system by specifying its ID, description, and optionally the group ID it belongs to.
This node would be beneficial in scenarios where users need to update metadata or details of existing custom variables programmatically within an automation workflow. For example, updating the description of a variable to reflect new usage or changing its group association for better organization.
Properties
| Name | Meaning |
|---|---|
| ID Da Variável Customizada | The unique identifier of the custom variable to be edited. |
| Descrição | A brief description of the custom variable. This field is required when editing the variable. |
| ID Do Grupo | The unique identifier of the group to which the custom variable belongs. Optional for editing. |
Output
The source code does not provide explicit details about the output structure. However, typically, after editing a custom variable, the node would output a JSON object representing the updated variable, including fields such as its ID, description, group ID, and possibly timestamps or status indicators.
If the node supports binary data output, it is not indicated in the provided code or properties.
Dependencies
- The node imports its description from an external module (
./NI.description), indicating modular design. - No explicit external API calls or services are shown in the snippet.
- Likely requires an API key or authentication token configured in n8n to interact with the backend service managing custom variables.
Troubleshooting
- Missing Required Fields: If the "Descrição" property is not provided when editing, the node may throw a validation error since it is marked as required.
- Invalid IDs: Providing incorrect or non-existent custom variable IDs or group IDs could result in errors or no changes applied.
- Authentication Issues: Without proper credentials or API access, the node might fail to update the variable.
- Incomplete Implementation: Since the execute logic is missing, ensure the full node code is present and correctly deployed.
Links and References
- No external links or references are provided in the source code.
- For more information on managing custom variables, refer to the documentation of the platform or API this node integrates with.