Shippo icon

Shippo

Interact with Shippo API

Actions68

Overview

This node interacts with the Shippo API to delete the default parcel template associated with a user's account. It is useful in scenarios where you want to programmatically remove an existing default parcel template, for example, when updating shipping configurations or cleaning up unused templates in your shipping setup.

Practical examples include:

  • Automating the removal of outdated parcel templates before creating new ones.
  • Managing shipping settings dynamically based on changing business needs.

Properties

Name Meaning
SHIPPO API VERSION Optional string to specify a non-default version of the Shippo API to use for this request. See Shippo's API versioning guide for details.

Output

The node outputs JSON data representing the response from the Shippo API after attempting to delete the default parcel template. This typically includes confirmation of deletion or error information if the operation failed.

No binary data output is expected from this operation.

Dependencies

  • Requires an active Shippo API key credential configured in n8n to authenticate requests.
  • The node sends HTTP requests to the Shippo API endpoint at https://api.goshippo.com.
  • Optionally supports specifying a custom API version via the SHIPPO API VERSION property header.

Troubleshooting

  • Common issues:

    • Invalid or missing API key will cause authentication errors.
    • Attempting to delete a default parcel template that does not exist may result in a "not found" error.
    • Using an unsupported API version string could lead to version mismatch errors.
  • Error messages and resolutions:

    • 401 Unauthorized: Check that the API key credential is correctly set and has proper permissions.
    • 404 Not Found: Verify that a default parcel template exists before attempting deletion.
    • 400 Bad Request: Ensure the API version string (if provided) is valid according to Shippo's API versioning documentation.

Links and References

Discussion