1001fx - NoCode functions icon

1001fx - NoCode functions

1001fx is a set of functions for any automation platform. Our functions are simple, very well tested, scalable and offer features that most automation platforms do not offer.

Actions74

carbone → Render Carbone Template

AI-generated

Overview

The Render Carbone Template operation in the "carbone" resource allows you to generate documents by merging a template file (such as DOCX, ODT, PDF, etc.) with dynamic data. This is particularly useful for automating the creation of reports, invoices, certificates, or any document that requires templated content filled with variable data.

Common scenarios:

  • Generating personalized invoices for each customer from a template.
  • Creating custom reports based on user input or database records.
  • Automating the production of certificates, contracts, or letters with unique information per recipient.

Practical example:
You have a DOCX invoice template and a list of customers with their purchase details. Using this node, you can automatically produce a ready-to-send invoice for each customer in PDF format.


Properties

Name Meaning
Template file Template file to be processed. This is the base document (e.g., DOCX, ODT) containing placeholders for your data. Required.
Data Data to fill your template with. You must provide either structured JSON data or a stringified version. This data will replace the placeholders in your template.
Output Format Output format for your rendered template. If not specified, it defaults to the format of the provided template. Options: csv, docx, ods, odt, pdf, txt, xslx.
Binary Property Name of the binary property to which to write the data of the rendered file. This determines where the output file will be stored in the n8n item. Default is "data". Required.

Output

  • The node outputs an item with a binary field.
  • The rendered document (e.g., PDF, DOCX, etc.) is available under the property name specified in Binary Property (default: data).
  • The binary field contains:
    • The file data (buffer)
    • Metadata such as filename and MIME type
  • The json field is preserved from the input item.

Example output structure:

{
  "json": { /* original input json */ },
  "binary": {
    "data": {
      "data": "<base64-encoded file>",
      "fileName": "output.pdf",
      "mimeType": "application/pdf"
    }
  }
}

Dependencies

  • External Service: Requires access to the 1001fx API.
  • API Key: You must configure the 1001fxApi credential in n8n.
  • Environment: No special environment variables are required beyond standard n8n configuration.

Troubleshooting

Common issues:

  • Missing or invalid template file: Ensure the template file is correctly uploaded and referenced.
  • Malformed data: The data property must be valid JSON or a properly stringified object matching the template's placeholders.
  • Incorrect binary property name: If you change the default, ensure you reference the correct property in downstream nodes.
  • Authentication errors: Make sure your 1001fx API credentials are set up and valid.

Error messages:

  • "error": "Invalid template file" – Check that the file is a supported template format.
  • "error": "Data does not match template" – Ensure your data keys correspond to the placeholders in your template.
  • "error": "Authentication failed" – Verify your API key in the n8n credentials.

Links and References

Discussion