0CodeKit icon

0CodeKit

A toolbox of no-code utilities

Actions132

Shortened URL → Update Shortened URL

AI-generated

Overview

This node provides utilities for managing shortened URLs, specifically allowing users to update an existing shortened URL's destination. It is useful in scenarios where a previously created short link needs to redirect to a new target URL without changing the short identifier itself. For example, if a marketing campaign changes its landing page, you can update the shortened URL to point to the new page seamlessly.

Properties

Name Meaning
URL Identifier The unique identifier of the shortened URL to update (e.g., "to4w5vyb").
New Destination URL The new destination URL that the shortened URL should redirect to (e.g., "https://example.com").

Output

The node outputs JSON data representing the result of the update operation on the shortened URL. This typically includes confirmation details such as the updated identifier and the new destination URL. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authentication with the external 0CodeKit service.
  • The node sends a POST request to the endpoint /generate/shortenedurl/put on the base URL https://prod.0codekit.com.
  • Proper configuration of the API key credential within n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Invalid or missing URL Identifier: Ensure the identifier corresponds to an existing shortened URL.
    • Invalid destination URL format: Verify the new destination URL is a valid URL.
    • Authentication errors: Confirm the API key credential is correctly configured and has sufficient permissions.
    • Network or service downtime: Check connectivity to the 0CodeKit API endpoint.
  • Error messages:

    • "Identifier not found" or similar indicates the specified shortened URL does not exist.
    • "Invalid URL format" suggests the destination URL is malformed.
    • "Unauthorized" or "Authentication failed" points to issues with the API key credential.

Resolving these usually involves verifying input values and credential setup.

Links and References

Discussion