Actions6
- Template Actions
- Pdf Renderer Actions
- Txt Renderer Actions
Overview
This node integrates with a template-based document generation service, focusing here on the Txt Renderer resource with the Render as TXT Byte Array operation. It renders a specified text template into a byte array format. This is useful when you want to generate plain text documents programmatically and handle them in binary form, for example, to store or transmit them efficiently.
Common scenarios include:
- Generating customized text reports or logs from templates.
- Creating downloadable text files dynamically within workflows.
- Passing rendered text content as binary data to other systems or nodes that require byte arrays.
Example: You select a predefined text template by its ID, then render it as a TXT byte array to upload to a file storage service or send as an email attachment.
Properties
Name | Meaning |
---|---|
Template | The specific text template to be rendered. Options are dynamically loaded from available templates. |
Output
The node outputs a JSON array where each item corresponds to one input item processed. For the Render as TXT Byte Array operation, the output contains the rendered template content encoded as a byte array (binary data). This byte array represents the generated plain text document in binary form, suitable for further processing or storage.
Dependencies
- Requires an API key credential for authenticating with the external template rendering service.
- The node makes HTTP requests to
https://api.templateto.com
. - The environment must allow outbound HTTPS connections to this endpoint.
- The node depends on a helper function to load available templates dynamically for the Template property.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Specifying a non-existent template ID will result in errors from the API.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors typically indicate invalid or missing API keys; verify credentials configuration.
- "Template not found" errors mean the selected template ID does not exist; check available templates.
- Timeout or connection errors suggest network issues; ensure the node can reach the API endpoint.
Links and References
- TemplateTo API Documentation (assumed official API docs)
- n8n documentation on Creating Custom Nodes