PrintcartInstall

Overview

This node integrates with the Printcart API, allowing users to interact with various Printcart resources such as accounts, stores, products, sides, images, cliparts, designs, projects, templates, storages, fonts, webhooks, and project folders. Specifically, for the Template resource and the Get List Fonts Layer by Template operation, the node fetches the list of font layers associated with a given template ID.

This operation is useful when you want to retrieve all font-related information used in a specific template design within Printcart. For example, if you are managing print-on-demand templates and need to know which fonts are applied on a particular template layer, this node operation provides that data.

Practical scenarios include:

• Automating the retrieval of font details for templates to ensure brand consistency.
• Integrating font data into other systems or workflows for design audits.
• Dynamically adjusting or validating template font usage before production.

Properties

Output

The output is a JSON array containing the response from the Printcart API endpoint that lists fonts used in the specified template. Each item in the array represents a font layer associated with the template, typically including font properties such as name, type, URL, alias, subset, and other metadata related to the font layer.

No binary data output is involved in this operation.

Dependencies

• Requires an API token credential for authenticating requests to the Printcart API.
• The node makes HTTP GET requests to the Printcart API endpoint:
  https://<sid>:<secret>@api.printcart.com/v1/templates/{templateId}/fonts
• The user must configure the API token credentials properly in n8n to allow authenticated access.

Troubleshooting

• Common issues:

  • Invalid or missing API token credential will cause authentication failures.
  • Incorrect or non-existent Template ID will result in errors or empty responses.
  • Network connectivity issues may prevent successful API calls.

• Error messages:

  • Authentication errors typically indicate invalid or expired API tokens; reconfigure or renew the token.
  • 404 Not Found errors suggest the provided Template ID does not exist.
  • 400 Bad Request errors may occur if the Template ID format is incorrect.

• Resolution tips:

  • Verify the API token credential is correctly set up and has necessary permissions.
  • Double-check the Template ID input for correctness.
  • Ensure network access to the Printcart API endpoint is available.

Links and References

• Printcart API Documentation (general reference for endpoints and authentication)
• n8n documentation on HTTP Request Node for understanding how API calls are made within nodes