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 storage entities within a Printcart account. Specifically, the "Create Storages" operation allows users to create new storage entries by specifying a name and optionally a parent storage ID to nest storages hierarchically.
Common scenarios for this node include organizing digital assets or files in a structured manner within Printcart's storage system, such as creating folders or categories to better manage design files, cliparts, or other resources.
Practical example: A user wants to programmatically add a new storage folder named "Summer Collection" under an existing parent storage to organize seasonal design assets.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; currently supports only "API Token" authentication. |
| Name | The name of the storage to be created. This is a required string input. |
| Parent ID | Optional ID of the parent storage under which the new storage will be nested (string). |
Output
The node outputs JSON data representing the response from the Printcart API after creating the storage. This typically includes details of the newly created storage such as its unique identifier, name, parent ID, creation timestamps, and other metadata provided by the API.
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 requests to
https://api.printcart.com/v1/storagesendpoint. - Proper configuration of the API token credential in n8n is necessary for successful execution.
Troubleshooting
- Authentication errors: If the API token is invalid or missing, the node will fail to authenticate. Ensure the API token credential is correctly set up and has sufficient permissions.
- Validation errors: Missing the required "Name" property or providing an invalid "Parent ID" may cause the API to reject the request. Verify that all required fields are filled correctly.
- Network issues: Connectivity problems to the Printcart API endpoint can cause timeouts or failures. Check network access and proxy settings if applicable.
- API rate limits: Excessive requests might lead to rate limiting by the Printcart API. Implement retry logic or reduce request frequency if needed.
Error messages returned by the API will generally be included in the node's output when "Continue On Fail" is enabled, helping diagnose issues.
Links and References
- Printcart API Documentation (for detailed API endpoints and payloads)
- n8n documentation on HTTP Request Node (for understanding underlying request mechanics)