Overview
The "Delete Template" operation of the Carbone n8n node allows users to delete a template from the Carbone API by specifying its ID. This is useful in scenarios where you need to manage and clean up templates that are no longer needed, ensuring your Carbone environment remains organized and up-to-date.
Practical examples:
- Automatically remove outdated report templates after generating new versions.
- Clean up test or temporary templates as part of a workflow automation process.
Properties
| Name | Type | Meaning |
|---|---|---|
| ID | String | ID of resource to Get, Edit, Delete or add data to. For this operation, it's the template ID to delete. |
Output
The output for the "Delete Template" operation is a JSON object containing the response from the Carbone API after attempting to delete the specified template. The structure typically looks like:
{
"json": {
// Response from Carbone API, e.g., success message or status
},
"binary": {}
}
- json: Contains the result of the deletion request (e.g., confirmation of deletion).
- binary: Not used for this operation.
Dependencies
- External Service: Requires access to the Carbone API.
- Credentials: You must configure the
carboneApicredential in n8n for authentication.
Troubleshooting
Common Issues:
- Invalid or missing ID: If the provided ID does not correspond to an existing template, the API may return an error indicating the template was not found.
- Authentication errors: If the
carboneApicredentials are not set up correctly, requests will fail with authentication errors. - Network issues: Connectivity problems between n8n and the Carbone API can cause failures.
Error Messages:
"No binary data exists on item!": Not relevant for this operation, but may appear if the wrong operation is selected.- Errors from the Carbone API (e.g., "Template not found"): Ensure the ID is correct and the template exists.
How to resolve:
- Double-check the template ID.
- Verify Carbone API credentials in n8n.
- Ensure network connectivity to the Carbone API endpoint.