WbProducts icon

WbProducts

n8n node to interact with WB API

Overview

This node is designed to delete a tag by its numeric ID within the "Ярлыки" (Tags) resource. It is useful in scenarios where you need to programmatically remove specific tags from a system, such as cleaning up unused or obsolete tags, managing tag lifecycle, or automating tag maintenance workflows.

For example, if you have a list of tags associated with products or items and want to delete a particular tag identified by its ID, this node allows you to do so efficiently within an n8n workflow.

Properties

Name Meaning
Id Numeric ID of the tag to delete

Output

The node outputs JSON data representing the result of the delete operation. Typically, this will include confirmation of deletion or details about the deleted tag. The exact structure depends on the API response but generally confirms success or failure of the deletion request.

No binary data output is expected from this node.

Dependencies

  • Requires an API key credential for authentication with the external service managing tags.
  • The node uses a base URL configured from an OpenAPI specification bundled within the node.
  • Proper network access to the external API endpoint is necessary.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent tag ID may result in an error indicating that the tag was not found.
    • Missing or incorrect API credentials can cause authentication failures.
    • Network connectivity problems can prevent the node from reaching the API.
  • Error messages and resolutions:

    • "Tag not found" — Verify the tag ID exists before attempting deletion.
    • "Authentication failed" — Check that the API key credential is correctly configured and valid.
    • Timeout or network errors — Ensure the API endpoint is reachable and there are no firewall restrictions.

Links and References

  • Refer to the external API documentation for detailed information on tag management endpoints.
  • Consult n8n documentation on how to configure API credentials and handle HTTP requests within custom nodes.

Discussion