Templated icon

Templated

n8n node to automate the generation of images and PDFs.

Actions5

Template → List Template Renders

AI-generated

Overview

The node "Templated" automates the generation of images and PDFs based on templates. Specifically, for the "Template" resource and the "List Template Renders" operation, it retrieves a paginated list of render results associated with a given template ID. This is useful when you want to track or manage previously generated outputs from a specific template, such as reviewing all image or PDF renders created from that template.

Practical examples:

  • Fetching all rendered invoices (PDFs) generated from an invoice template.
  • Listing all marketing images created from a promotional template to analyze usage.
  • Paginating through large sets of rendered documents for archival or further processing.

Properties

Name Meaning
Template ID The unique identifier of the template whose renders you want to retrieve.
Page The page number of results to fetch, starting at 0 for the first page.
Limit The maximum number of render results to return per request. Must be at least 1.

Output

The node outputs JSON data representing the list of template renders retrieved. Each item in the output corresponds to a single render instance of the specified template, typically including metadata such as render ID, creation date, status, and possibly URLs or references to the generated files (images or PDFs).

If the node supports binary data output, it would represent the actual rendered files (images or PDFs), but based on the provided code snippet and properties, the output focuses on listing render metadata rather than delivering binary content directly.

Dependencies

  • Requires an API key credential for authentication to the external templating service.
  • Needs the base URL of the templating API configured in the node credentials.
  • The node sends HTTP requests with JSON payloads and expects JSON responses.
  • No other external dependencies are indicated in the provided source.

Troubleshooting

  • Missing or invalid Template ID: The node requires a valid template ID; ensure this is correctly set and corresponds to an existing template.
  • Authentication errors: If the API key or base URL is incorrect or missing, the node will fail to authenticate. Verify credentials configuration.
  • Pagination issues: Requesting pages beyond available data may return empty results; adjust the page and limit parameters accordingly.
  • API rate limits or downtime: External service limitations can cause failures; check service status and retry policies.

Common error messages might include unauthorized access, not found (invalid template ID), or bad request (invalid parameters). Resolving these involves verifying input values and credentials.

Links and References

  • Refer to the templating service's official API documentation for details on template render endpoints and pagination.
  • n8n documentation on creating and configuring API key credentials.
  • General REST API pagination best practices.

Discussion