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 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 in scenarios where you want to programmatically add custom fonts to your Printcart environment for use in designs or templates.
Practical examples include:
- Automating the addition of brand-specific fonts to your Printcart store.
- Bulk uploading multiple fonts from an external source.
- Integrating font management into a larger workflow that handles design assets.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; currently supports "API Token" |
| Name | The official name of the font to be created (required) |
| Alias | A user-friendly alias or nickname for the font (required) |
| Url | The URL where the font file is hosted or can be accessed |
| Type | The type or category of the font (e.g., example, custom) |
| Subset | The subset of characters included in the font (required), e.g., "latin", "cyrillic" etc. |
Output
The output of this operation is a JSON object representing the newly created font resource as returned by the Printcart API. It typically includes all properties of the font such as its unique identifier, name, alias, URL, type, subset, creation timestamps, and any other metadata provided 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 endpoint at
https://api.printcart.com/v1/fonts. - Proper network connectivity to the Printcart API service is necessary.
Troubleshooting
- Authentication errors: Ensure the API token is valid and has sufficient permissions to create fonts.
- Missing required fields: The operation requires
name,alias, andsubsetfields. Omitting these will likely cause API errors. - Invalid URL: If the
urlproperty points to an inaccessible or invalid font file location, the API may reject the request. - API rate limits or downtime: Temporary failures might occur if the Printcart API is unavailable or rate-limited.
- Error messages: Errors returned from the API are propagated. Check the error message for details, such as validation errors or permission issues.
To resolve common errors:
- Double-check all required input parameters.
- Verify API token validity.
- Confirm the font URL is reachable and correctly formatted.
- Review Printcart API documentation for any changes or additional requirements.
Links and References
- Printcart API Documentation (general reference for endpoints and payloads)
- Printcart Fonts API Endpoint (specific endpoint used by this node)