Actions32
Overview
This node integrates with the ShipStation API v2 to manage various resources related to shipping and inventory. Specifically, for the Product resource with the List operation, it retrieves a list of products from ShipStation.
Common scenarios where this node is beneficial include:
- Synchronizing product catalogs between ShipStation and other systems.
- Automating inventory or product data retrieval for reporting or processing.
- Fetching product lists for further workflow automation such as order fulfillment or analytics.
For example, you might use this node to fetch all products available in your ShipStation account, then filter or process them downstream in your workflow.
Properties
| Name | Meaning |
|---|---|
| Options | Collection of options to control pagination and result size: |
| - Page: Page number to retrieve (default 1) | |
| - Page Size: Number of items per page (default 50) | |
| - Return All: Boolean flag to return all results across pages or limit to one page |
Output
The output is an array of JSON objects representing products retrieved from ShipStation. Each item corresponds to a product entity as returned by the ShipStation API.
The json field contains the product data structure, which typically includes product details such as SKU, name, price, weight, and other relevant attributes defined by ShipStation.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the ShipStation API.
- The node uses internal services for API requests, error handling, and pagination.
- No additional external dependencies beyond the ShipStation API and n8n's credential system.
Troubleshooting
- API Errors: If the ShipStation API returns an error (e.g., invalid credentials, rate limits), the node will throw an error with details. Ensure your API key is valid and has sufficient permissions.
- Pagination Issues: When using "Return All," large datasets are fetched in multiple requests. Network issues or API limits may cause failures; consider limiting page size or disabling "Return All" if problems occur.
- Invalid Parameters: Providing invalid page numbers or sizes may result in empty or error responses. Use sensible values within API limits.
- JSON Parsing: This operation does not require JSON input, but other operations do. Ensure JSON inputs are well-formed when used.