Actions12
- Short URL Actions
- Tag Actions
- Visit Actions
- Domain Actions
Overview
This node integrates with the Shlink URL Shortener API, allowing users to manage short URLs programmatically. Specifically, the "Get" operation for the "Short URL" resource retrieves detailed information about a short URL using its unique short code.
Common scenarios where this node is beneficial include:
- Retrieving metadata or statistics about a specific shortened URL.
- Validating if a short URL exists before performing further actions.
- Integrating URL shortening and management into automated workflows, such as marketing campaigns or link tracking systems.
For example, you can input a short code to fetch the corresponding long URL, visit counts, tags, and other associated data.
Properties
| Name | Meaning |
|---|---|
| Short Code | The unique short code identifier of the URL to retrieve. |
Output
The output is a JSON object containing detailed information about the requested short URL. This typically includes fields such as the original long URL, creation date, tags, visit statistics, title, validity period, and domain information.
No binary data is returned by this operation.
Dependencies
- Requires an API key credential for authenticating with the Shlink URL Shortener API.
- The base URL of the Shlink instance must be configured in the credentials.
- The node makes HTTP requests to the Shlink REST API endpoints.
Troubleshooting
Common issues:
- Invalid or missing short code parameter will cause the request to fail.
- Incorrect or missing API credentials will result in authentication errors.
- Network connectivity problems or incorrect base URL configuration may cause request failures.
Error messages:
- Errors from the API are logged with status codes and response data when available.
- Typical error responses include 404 Not Found if the short code does not exist, or 401 Unauthorized if credentials are invalid.
Resolution tips:
- Verify that the short code is correct and exists in your Shlink instance.
- Ensure the API key and base URL are correctly set in the node credentials.
- Check network access to the Shlink server.