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 to manage projects and other related resources. Specifically, for the Project resource with the Get List of Project operation, it retrieves a list of projects from the Printcart platform based on user-defined filters such as limit, sorting, and status.
Typical use cases include:
- Fetching a paginated list of projects for display or further processing.
- Filtering projects by their status (e.g., Processing, Accepted).
- Sorting projects by specific fields like ID in ascending or descending order.
For example, a user might want to retrieve the 10 most recent projects that are currently in "Processing" status, sorted by project ID in descending order.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; only option is "API Token". |
| Limit | Maximum number of project results to return; minimum value is 10. |
| Sort | Collection specifying sort direction: either "Asc" (ascending) or "Desc" (descending). |
| Sort By | Field name to sort the projects by; defaults to "id". |
| Status | Filter projects by status; options include "Processing", "Accepted", "Trashed", "Reviewing". |
Output
The node outputs an array of JSON objects representing projects retrieved from the Printcart API. Each object corresponds to a project and contains its details as returned by the API.
The exact structure depends on the Printcart API response but typically includes fields such as project ID, name, status, note, creation date, 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 endpoints like
https://{sid}:{secret}@api.printcart.com/v1/projectswith query parameters for filtering and sorting. - The user must configure the API token credentials properly in n8n before using this node.
Troubleshooting
Common issues:
- Invalid or missing API token will cause authentication failures.
- Providing a limit below 10 may be rejected due to API constraints.
- Incorrect status or sort values may result in empty responses or errors.
Error messages:
- Authentication errors usually indicate invalid or expired API tokens; recheck and update credentials.
- HTTP 4xx or 5xx errors suggest issues with request parameters or server availability.
- If the node returns no projects, verify that the status filter matches existing projects.
Resolution tips:
- Ensure the API token credential is correctly set up and has necessary permissions.
- Use valid status values as per the provided options.
- Check network connectivity and API endpoint accessibility.
Links and References
- Printcart API Documentation (Assumed URL for reference; replace with actual if available)
- n8n documentation on HTTP Request Node for understanding API calls
- n8n credential setup guides for managing API tokens