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 is designed to update the name of an existing integration within a system. It allows users to specify the ID of the integration they want to rename and provide a new name for it. This functionality is useful in scenarios where integrations need to be re-labeled for clarity, organization, or reflecting changes in their purpose.
Practical examples include:
- Renaming an integration after a system upgrade or rebranding.
- Correcting typos or errors in the integration's original name.
- Standardizing naming conventions across multiple integrations.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the existing integration that you want to rename. |
| Novo Nome (New Name) | The new name to assign to the integration in the panel, limited to 100 characters. |
Output
The node outputs JSON data representing the result of the rename operation. Typically, this would include confirmation of the update, possibly the updated integration object with its new name, or status information indicating success or failure.
If the node supports binary data output, it would relate to any files or attachments associated with the integration, but based on the provided code and properties, no binary output is expected.
Dependencies
- Requires access to the system or API managing integrations.
- Needs appropriate authentication credentials (e.g., an API key or token) configured in n8n to authorize the rename operation.
- The node depends on the underlying service's API endpoint that handles integration updates.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent integration ID will likely cause the operation to fail.
- Exceeding the 100-character limit for the new name may result in validation errors.
- Insufficient permissions or missing authentication credentials can prevent the update.
Error Messages:
- "Integration not found" indicates the specified ID does not match any existing integration.
- "Name exceeds maximum length" suggests the new name is too long.
- "Unauthorized" or "Authentication failed" means the API credentials are missing or incorrect.
Resolutions:
- Verify the integration ID is correct and exists.
- Ensure the new name is within the allowed character limit.
- Check that valid API credentials are set up in n8n and have sufficient permissions.
Links and References
- Refer to your integration platform’s API documentation for details on updating integration names.
- Consult n8n documentation on setting up API credentials and using HTTP request nodes if custom API calls are needed.