Actions83
- 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 account. Specifically, the "Update Font" operation allows users to modify an existing font's details such as its name, alias, URL, type, and subset. This is useful in scenarios where you need to keep your font resources up-to-date or correct metadata for fonts used in your print designs.
Practical examples include:
- Updating the URL of a hosted font file after migration.
- Changing the display name or alias of a font for better identification.
- Modifying the font type or subset to reflect new categorization or supported character sets.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; currently supports "API Token" |
| Font ID | The unique identifier of the font to update (required) |
| Name | The new name for the font (required) |
| Alias | The new alias for the font, e.g., a friendly or alternative name (required) |
| Url | The URL pointing to the font resource (e.g., hosted font file location) |
| Type | The type/category of the font (e.g., example, custom) |
| Subset | The subset of characters supported by the font (required) |
Output
The node outputs a JSON array containing the response from the Printcart API after updating the font. The structure corresponds to the updated font object returned by the API, typically including fields like font ID, name, alias, URL, type, subset, and possibly timestamps or status indicators.
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 are required beyond the API token.
Troubleshooting
Common Issues:
- Invalid or expired API token will cause authentication failures.
- Providing an incorrect or non-existent Font ID will result in errors indicating the font was not found.
- Missing required parameters (Font ID, Name, Alias, Subset) will cause validation errors.
- Network connectivity issues can prevent successful API calls.
Error Messages & Resolutions:
- 401 Unauthorized: Check that the API token is valid and has necessary permissions.
- 404 Not Found: Verify the Font ID exists in your Printcart account.
- 400 Bad Request: Ensure all required fields are provided and correctly formatted.
- Network Errors: Confirm internet connectivity and that the Printcart API endpoint is reachable.
Links and References
- Printcart API Documentation (for detailed API usage and font resource management)
- n8n Documentation on Creating Custom Nodes