Actions32
Overview
This node integrates with the ShipStation API v2 to manage various shipping-related resources. Specifically, for the Product - Update operation, it allows users to update an existing product in their ShipStation account by specifying the product ID and providing updated data in JSON format.
Common scenarios where this node is beneficial include:
- Synchronizing product information between an e-commerce platform and ShipStation.
- Updating product details such as name, SKU, price, or other attributes after changes in inventory or catalog.
- Automating bulk updates of product data based on external triggers or workflows.
Example use case:
- A user wants to update the description and price of a product identified by its ID whenever the product details change in their inventory system. This node can be configured to receive the product ID and new data, then send the update request to ShipStation automatically.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the product to update. Required to specify which product to modify. |
| JSON Data | JSON-formatted string containing the fields and values to update for the product. This should follow ShipStation's product update schema. |
Output
The node outputs a JSON object representing the updated product resource as returned by the ShipStation API. The structure corresponds to the product data model in ShipStation, including all updated fields.
If the operation fails and "Continue On Fail" is enabled, the output will contain an error message describing the failure.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the ShipStation API via an API key credential.
- The node depends on the ShipStationApiService class to handle HTTP requests to the ShipStation API endpoints.
- Proper API credentials must be configured in n8n to authenticate requests.
Troubleshooting
Common issues:
- Invalid or missing product ID: Ensure the "ID" property is correctly set to an existing product's ID.
- Malformed JSON in "JSON Data": The JSON string must be valid and conform to ShipStation's expected product update schema.
- API authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network or API downtime: Check connectivity and ShipStation service status.
Error messages:
- Errors returned from the ShipStation API are caught and presented. For example, if the product ID does not exist, the API may return a 404 error.
- If the JSON data is invalid, the API may respond with validation errors.
- The node throws descriptive errors when unknown operations or resources are specified.
To resolve errors:
- Double-check input parameters.
- Validate JSON syntax before running the node.
- Confirm API credentials and permissions.
- Review ShipStation API documentation for correct payload formats.