Actions32
Overview
This node integrates with the ShipStation API v2 to manage various shipping-related resources. Specifically, for the Warehouse - Delete operation, it allows users to delete a warehouse record by specifying its unique ID. This is useful in scenarios where warehouses are no longer active or need to be removed from the system to keep data clean and up-to-date.
Practical examples include:
- Removing a closed or relocated warehouse from your ShipStation account.
- Automating cleanup of warehouses that are temporarily used for special events or seasonal storage.
- Integrating with inventory management workflows to ensure only active warehouses are maintained.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the warehouse to delete. This is a required string input. |
Output
The node outputs a JSON object representing the response from the ShipStation API after attempting to delete the warehouse. Typically, this will contain confirmation details or status information about the deletion request.
Example output structure (simplified):
{
"json": {
// API response data confirming deletion or providing status
}
}
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the ShipStation API.
- The node uses the ShipStation API v2 endpoints.
- No additional environment variables are needed beyond the API authentication setup.
Troubleshooting
Common issues:
- Providing an invalid or non-existent warehouse ID will result in an error from the API.
- Network connectivity problems can cause request failures.
- Insufficient permissions on the API key may prevent deletion.
Error messages:
- Errors returned by the ShipStation API are handled and surfaced by the node. For example, if the warehouse ID does not exist, the API might return a 404 error.
- If the node throws an "Unknown operation" error, verify that the Resource is set to "Warehouse" and Operation to "Delete".
Resolution tips:
- Double-check the warehouse ID value before running the node.
- Ensure the API key has proper permissions to delete warehouses.
- Use the node's "Continue On Fail" option to handle errors gracefully in workflows.