Actions48
- Custom Variable Actions
- Custom Variable Group Actions
- Event Actions
- Integration Actions
- Lead Actions
- Lead List Actions
Overview
This node operation allows users to rename an existing custom variable group by specifying its unique identifier and the new desired name. It is useful in scenarios where variable groups need to be reorganized or renamed for clarity, consistency, or updated naming conventions within automation workflows.
For example, if you have a variable group named "Marketing Campaign" and want to rename it to "Q2 Marketing Campaign," this operation facilitates that update without needing to recreate the group or manually adjust references.
Properties
| Name | Meaning |
|---|---|
| Group ID | Unique identifier of the variable group to be renamed. |
| New Group Name | The new name to assign to the variable group. This is a required field. |
Output
The output JSON will typically contain the updated details of the variable group after renaming, including at least the group's unique identifier and its new name. The exact structure depends on the API response but generally confirms the successful update.
No binary data output is expected from this operation.
Dependencies
- Requires access to the external API endpoint managing variable groups.
- Needs an authenticated HTTP request setup with appropriate credentials (e.g., an API key or token) configured in n8n to authorize the rename operation.
- Network connectivity to
https://api.notificacoesinteligentes.comor the relevant service endpoint.
Troubleshooting
- Invalid Group ID: If the provided Group ID does not exist or is incorrect, the API may return an error indicating the group was not found. Verify the Group ID before retrying.
- Authentication Errors: Missing or invalid authentication credentials will cause authorization failures. Ensure the API key or token is correctly configured in n8n.
- Empty New Group Name: Since the new group name is required, leaving it empty will likely result in validation errors. Always provide a valid non-empty string.
- Network Issues: Timeouts or connectivity problems can prevent the request from completing. Check network status and API availability.
- API Rate Limits: Excessive requests might trigger rate limiting; handle such errors by implementing retries with backoff.
Links and References
- Refer to the official API documentation of the variable group management service for detailed information on the rename endpoint.
- n8n HTTP Request node documentation for configuring authenticated API calls.