Overview
The Carbone node for n8n enables interaction with the Carbone API, specifically for managing templates and reports. The Get Template operation retrieves a template file from Carbone by its ID and outputs it as binary data. This is useful in scenarios where you need to fetch and use document templates (e.g., DOCX, ODT) stored in Carbone for further processing or distribution within your workflow.
Practical examples:
- Downloading a template to attach to an email.
- Fetching a template to use as input for another automation step.
- Archiving templates from Carbone into cloud storage.
Properties
| Name | Type | Meaning |
|---|---|---|
| ID | String | ID of the template to retrieve. |
| Binary Property | String | Name of the binary property under which the downloaded template will be stored in output. |
Output
- json: Contains any JSON data passed through from the input item. No new JSON fields are added by this operation.
- binary:
- A property named according to the value of Binary Property (default:
data) will contain the downloaded template file as binary data. - The binary data represents the template file (e.g., DOCX, ODT).
- A property named according to the value of Binary Property (default:
Dependencies
- External Service: Requires access to the Carbone API.
- Credentials: Needs a configured
carboneApicredential in n8n. - Environment: No special environment variables required beyond n8n's standard configuration.
Troubleshooting
Common issues:
- Missing or incorrect ID: If the provided ID does not correspond to an existing template, the node may throw an error indicating that the resource was not found.
- No binary property in output: If the Binary Property name is misspelled or conflicts with other properties, the binary data may not appear as expected.
- Credential errors: If the Carbone API credentials are missing or invalid, authentication errors will occur.
Error messages:
"No binary data exists on item!": This should not occur for "Get Template", but if encountered, ensure the input item structure is correct."No binary data property ... does not exist on item!": Ensure the Binary Property matches the expected output property name.