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, enabling users to manage various resources such as accounts, stores, products, sides, images, cliparts, designs, projects, templates, storages, fonts, webhooks, clipart storages, and project folders. Specifically for the Font resource, the node supports operations including creating, updating, retrieving details, listing, counting, and deleting fonts.
The Delete Font operation allows users to remove a font from their Printcart account by specifying its unique Font ID. This is useful in scenarios where obsolete or unwanted fonts need to be cleaned up from the system to maintain an organized font library.
Practical Example
- A print shop automating their design workflow can use this node to delete fonts that are no longer used in any design projects.
- A developer managing a large collection of fonts can programmatically remove deprecated fonts to keep the font repository current.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; currently only "API Token" is supported. |
| Font ID | The unique identifier of the font to delete. This is a required string input. |
Output
The node outputs a JSON array containing the response from the Printcart API after attempting to delete the specified font. The structure typically includes confirmation of deletion or error information if the operation failed.
Example output JSON (simplified):
[
{
"success": true,
"message": "Font deleted successfully",
"fontId": "12345"
}
]
If the deletion fails, the output will contain an error message describing the issue.
The node does not output binary data.
Dependencies
- Requires an active connection to the Printcart API.
- Requires an API token credential for authentication.
- The node uses HTTP requests to communicate with the Printcart API endpoints.
- No additional environment variables or external services are needed beyond the API token.
Troubleshooting
Common Issues:
- Invalid or missing Font ID: Ensure the Font ID provided exists and is correct.
- Authentication failure: Verify that the API token is valid and has sufficient permissions.
- Network issues: Confirm that the node can reach the Printcart API endpoint (
https://api.printcart.com).
Error Messages:
"401 Unauthorized": Indicates invalid or expired API token. Refresh or update the token."404 Not Found": The specified Font ID does not exist. Double-check the Font ID."400 Bad Request": The request parameters may be malformed or incomplete. Verify all required inputs.- Other API errors will be returned in the response JSON; review these messages for guidance.
Resolution Tips:
- Use the "Get Font Detail" operation first to confirm the Font ID before attempting deletion.
- Enable "Continue On Fail" in the node settings to handle errors gracefully during batch operations.
Links and References
- Printcart API Documentation (Assumed official docs URL)
- n8n Documentation on HTTP Request Node for understanding underlying request mechanics
- General API Authentication best practices for token-based APIs