Actions80
- Account Actions
- Clipart Actions
- Clipart Storage Actions
- Design Actions
- Font Actions
- Image Actions
- Product Actions
- Project Actions
- Project Folder Actions
- Side Actions
- Storage Actions
- Store Actions
- Template Actions
- Webhook Actions
Overview
This node integrates with the Printcart API to manage fonts within a Printcart store environment. Specifically, the "Create Font" operation allows users to add new font entries by specifying details such as the font's name, alias, URL, type, and subset. This is useful for automating font management in print-on-demand or design-related workflows where custom fonts need to be programmatically added to a Printcart account.
Practical examples include:
- Automatically adding new fonts from a font repository URL when onboarding new design projects.
- Integrating font creation into a larger automation that sets up product designs with specific typography.
- Managing font assets dynamically based on user input or external triggers.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; currently supports "API Token" for accessing the Printcart API. |
| Name | The official name of the font to create (required). |
| Alias | A user-friendly alias or label for the font (required). |
| Url | The URL where the font file or resource can be accessed. |
| Type | The type or category of the font (e.g., example type). |
| Subset | The subset of characters included in the font (required). |
Output
The node outputs a JSON array containing the response from the Printcart API after creating the font. This typically includes details about the newly created font such as its ID, name, alias, URL, type, subset, and any metadata returned by the API.
No binary data output is involved in this operation.
Dependencies
- Requires an active Printcart API token credential for authentication.
- The node makes HTTP requests to the Printcart API endpoints over HTTPS.
- No additional external dependencies beyond the Printcart API and n8n's HTTP request helper.
Troubleshooting
- Authentication errors: Ensure the provided API token is valid and has sufficient permissions to create fonts.
- Missing required fields: The "Name", "Alias", and "Subset" properties are mandatory; omitting them will likely cause API errors.
- Invalid URL: The "Url" property should point to a valid font resource; invalid URLs may cause the API to reject the request.
- API rate limits or downtime: If requests fail unexpectedly, check Printcart API status and consider retry logic.
- Error messages from API: Typically include HTTP status codes and error messages; review these to adjust parameters accordingly.
Links and References
- Printcart API Documentation (general reference for API endpoints)
- n8n documentation on HTTP Request Node for understanding how API calls are made within nodes