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
The node integrates with the Printcart API to manage various resources related to print-on-demand services. Specifically, for the Storage resource and the Update Storages operation, it allows updating an existing storage entity by specifying its ID and new details such as name and parent ID.
This node is beneficial in scenarios where you need to programmatically organize or restructure storage categories within a Printcart account, for example:
- Renaming a storage folder.
- Moving a storage folder under a different parent category.
- Automating updates to storage metadata as part of a larger workflow managing print assets.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; currently supports "API Token" only. |
| Name | The new name to assign to the storage entity being updated. |
| Parent ID | The identifier of the parent storage entity under which this storage will be nested. |
| Storages ID | The unique identifier of the storage entity to update. |
Output
The node outputs JSON data representing the response from the Printcart API after attempting to update the storage entity. This typically includes the updated storage details such as its ID, name, parent ID, creation and modification timestamps, and any other metadata returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Printcart API.
- Needs an API token credential configured in n8n for authenticating requests.
- The node uses HTTP requests to the Printcart API endpoints, specifically the
/v1/storages/{storages_id}endpoint with the PUT method.
Troubleshooting
- Invalid or missing Storage ID: If the
storages_idparameter is incorrect or not provided, the API will likely return an error indicating the storage entity was not found. Ensure the correct ID is used. - Authentication errors: If the API token is invalid or expired, the request will fail with an authentication error. Verify that the API token credential is correctly set up and valid.
- Permission issues: The API user associated with the token must have permissions to update storages. Lack of permission will result in authorization errors.
- Network or connectivity problems: Ensure that the n8n instance can reach the Printcart API endpoint without firewall or network restrictions.
- API changes: If the Printcart API changes its endpoint or required parameters, the node may fail. Check the Printcart API documentation for updates.
Links and References
- Printcart API Documentation (general reference for API endpoints and usage)
- n8n documentation on HTTP Request Node for understanding how API calls are made within nodes