Actions32
Overview
This node integrates with the ShipStation API v2 to manage various shipping-related resources, including tags. Specifically, the Tag - Update operation allows users to update an existing tag by specifying its ID and providing new JSON data for the tag. This is useful in scenarios where you need to modify tag details such as name or other metadata after creation.
Practical examples include:
- Renaming a tag used for categorizing shipments.
- Updating tag attributes to reflect changes in your shipping workflow.
- Automating tag updates based on external triggers or data changes.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the tag resource to update. Required to specify which tag to update. |
| JSON Data | JSON-formatted string containing the fields and values to update on the tag resource. For example, updating the tag's name or description. |
Output
The node outputs a JSON object representing the updated tag resource as returned by the ShipStation API. The structure corresponds to the tag's properties after the update has been applied.
Example output JSON (simplified):
{
"tagId": 123,
"name": "Updated Tag Name",
"otherProperties": "..."
}
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the ShipStation API via an API key credential configured in n8n.
- The node uses the ShipStationApiService internally to perform HTTP requests to the ShipStation API endpoints.
- Proper permissions on the ShipStation account are necessary to update tags.
Troubleshooting
Common issues:
- Providing an invalid or non-existent tag ID will result in an error from the API.
- Malformed JSON in the "JSON Data" property can cause parsing errors.
- Insufficient API permissions may lead to authorization errors.
Error messages:
- Errors returned from the ShipStation API are caught and presented. For example, "Resource not found" if the tag ID does not exist.
- JSON parsing errors if the input JSON is invalid.
Resolutions:
- Verify the tag ID exists before attempting to update.
- Ensure the JSON data is valid and correctly formatted.
- Check API credentials and permissions.