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
This node operation allows users to change the name of an existing integration within a system. It is useful when you want to update or correct the display name of an integration without creating a new one. For example, if an integration was initially named incorrectly or needs rebranding, this operation lets you rename it easily.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the existing integration that you want to rename. |
| Novo Nome | The new name for the integration as it will appear in the panel (maximum 100 characters). |
Output
The output JSON typically contains confirmation details about the updated integration, such as its ID and the new name. This confirms that the renaming operation was successful. There is no indication that binary data is involved in this operation.
Dependencies
- Requires access to the system where integrations are managed.
- Needs appropriate authentication credentials (e.g., an API key or token) configured in n8n to authorize the renaming request.
Troubleshooting
- Invalid ID: If the provided integration ID does not exist, the node may return an error indicating the integration was not found. Verify the ID before running the node.
- Name Length Exceeded: The new name must be 100 characters or fewer. Longer names may cause validation errors.
- Authentication Errors: Ensure that the API credentials used have permission to update integrations.
- Network Issues: Connectivity problems can prevent the node from reaching the integration service.
Links and References
No external links were provided in the source code or properties. For more information, consult the documentation of the platform managing the integrations.