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 and retrieve information related to various resources, including stores. Specifically, for the Store resource with the Get Store Info operation, it fetches a list of store data from the Printcart platform. Users can specify parameters such as the maximum number of results, sorting options, and filtering by status.
This node is beneficial in scenarios where you want to automate the retrieval of store information for reporting, synchronization with other systems, or dynamic workflows that depend on current store data. For example, an e-commerce manager might use this node to regularly pull updated store details to sync with their inventory system or marketing tools.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; currently supports "API Token" |
| Limit | Max number of store results to return (minimum 10) |
| Sort | Collection to specify sorting order: |
| - Type: "Desc" (descending) or "Asc" (ascending) | |
| Sort By | Field name to sort the store results by (default is "id") |
| Get By Status | Filter stores by status: |
| - Type: "Publish", "Draft", or "Trashed" |
Output
The output is a JSON array containing the store information retrieved from the Printcart API. Each item in the array corresponds to a store object with fields as returned by the API endpoint /v1/stores. The exact structure depends on the API response but typically includes store identifiers, names, statuses, and other metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an API token credential for authenticating requests to the Printcart API.
- The node makes HTTP GET requests to the Printcart API endpoint
https://api.printcart.com/v1/storeswith query parameters based on user input. - Proper configuration of the API token credential within n8n is necessary.
Troubleshooting
Common Issues:
- Invalid or missing API token will cause authentication failures.
- Providing a limit less than 10 may not be accepted due to minimum value constraints.
- Incorrect values for sorting or status filters may result in unexpected or empty responses.
Error Messages:
- Authentication errors typically indicate invalid or expired API tokens; recheck and update credentials.
- HTTP request errors may occur if the API endpoint is unreachable or if network issues exist.
- If the node throws errors about missing parameters, ensure all required properties are set correctly.
Links and References
- Printcart API Documentation (assumed official docs URL)
- n8n documentation on HTTP Request Node for understanding API calls and authentication setup