Shlink icon

Shlink

Interact with Shlink URL Shortener API

Actions12

Overview

This node integrates with the Shlink URL Shortener API, allowing users to manage URL tags among other resources. Specifically, for the Tag - Delete operation, it deletes a tag by its name from the Shlink system.

Common scenarios where this node is beneficial include:

  • Cleaning up unused or obsolete tags in your URL shortener setup.
  • Automating tag management workflows, such as removing tags after certain conditions are met.
  • Maintaining organized and relevant tagging of URLs by programmatically deleting tags.

Example use case:

  • You have a tag named "campaign2023" that is no longer needed. Using this node, you can delete that tag automatically as part of a cleanup workflow.

Properties

Name Meaning
Tag Name The name of the tag to delete.

Output

The output JSON contains the response from the Shlink API after attempting to delete the specified tag. Typically, this will be an empty object or confirmation of deletion if successful.

No binary data is output by this operation.

Dependencies

  • Requires connection to a Shlink URL Shortener instance via its REST API.
  • Requires an API key credential configured in n8n to authenticate requests.
  • The base URL of the Shlink instance must be provided in the credentials.
  • The node makes HTTP DELETE requests to the endpoint /rest/v3/tags/{tagName}.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Providing a tag name that does not exist may result in a 404 error from the API.
    • Network connectivity issues to the Shlink server will cause request failures.
  • Error messages:

    • "Request failed:" followed by an HTTP status code indicates the nature of the failure.
    • If the response status is 404, verify that the tag name exists.
    • For 401 or 403 errors, check that the API key credential is correct and has sufficient permissions.
  • Resolution tips:

    • Ensure the tag name is spelled correctly and exists in the Shlink system.
    • Confirm the API key and base URL in the credentials are accurate.
    • Check network access to the Shlink server from the n8n environment.

Links and References

Discussion