Actions6
Overview
This node integrates with the Short.io service to manage short links. Specifically, the "Update Existing Link" operation allows users to modify properties of an already created short link on their Short.io account. This is useful for updating the destination URL, changing expiration dates, adding tracking parameters, or customizing redirection behavior without creating a new short link.
Practical scenarios include:
- Updating the target URL of a marketing campaign link after launch.
- Setting or extending expiration dates for limited-time promotions.
- Adding UTM parameters to track traffic sources more effectively.
- Enabling device-specific redirects (e.g., different URLs for iPhone and Android users).
- Securing links with passwords or cloaking them to hide the original URL.
Properties
| Name | Meaning |
|---|---|
| Existing Short Link Identifier | Identifier of the short link to update. Can be specified either as the path part of the short URL (e.g., "6fzQYy") or as the internal ID string. |
| New Long URL | The new destination URL that the short link should redirect to. |
| Additional Fields | Optional additional settings for the link update: |
| - Path | Custom path segment for the short link. |
| - Allow Duplicates | Boolean indicating if multiple short links can point to the same original URL. |
| - Title | A descriptive title shown in the Short.io admin panel. |
| - Expires At (Unix Milliseconds) | Timestamp when the link will expire. After this time, the link will no longer be active. |
| - Expired URL | URL to redirect users to when the link has expired. |
| - iPhone URL | Redirect URL specifically for users opening the link on an iPhone. |
| - Android URL | Redirect URL specifically for users opening the link on an Android device. |
| - Cloaking | Boolean to enable cloaking, which hides the original URL in the browser address bar during redirection. |
| - Redirect Type | HTTP redirect status code to use (options: 301, 302, 303, 307, 308). Default is 302. |
| - Password | Password protection for the link (requires a paid plan). The password is securely hashed and not stored in plain text. |
| - Deletes At (TTL) | Timestamp when the link will be deleted permanently. Unlike expiration, deletion removes the link from the account and frees up link quota. Must be at least one week in the future. |
| - UTM Source | Referrer source for tracking (e.g., google, newsletter). |
| - UTM Medium | Marketing medium for tracking (e.g., cpc, banner, email). |
| - UTM Campaign | Campaign name or promo code (e.g., spring_sale). |
| - UTM Term | Paid keywords identifier. |
| - UTM Content | Used to differentiate ads or content variations. |
| - Tags | List of tags to categorize or label the link. Multiple tags can be added. |
Output
The node outputs a JSON object under the field shortIoResponse containing the response from the Short.io API after updating the link. This typically includes the updated link details such as its ID, path, original URL, expiration info, and any other metadata reflecting the changes made.
No binary data output is produced by this operation.
Dependencies
- Requires an active Short.io account and an API key credential configured in n8n for authentication.
- The node communicates with the Short.io REST API at
https://api.short.io/api. - Proper permissions on the API key are necessary to update existing links.
Troubleshooting
- Invalid Short Link Identifier: If the provided identifier does not correspond to an existing link, the API will return an error. Ensure the correct path or ID is used.
- Permission Denied: Insufficient API key permissions may cause authorization errors. Verify the API key has rights to update links.
- Invalid URL Format: The new long URL must be a valid URL; otherwise, the API may reject the request.
- Expiration or Deletion Timestamps: Setting expiration or deletion times incorrectly (e.g., deletion time less than one week ahead) will cause errors. Confirm timestamps are valid Unix milliseconds and meet Short.io requirements.
- Password Protection: Using password protection requires a paid plan. Attempting to set a password without proper plan access will fail.
- API Rate Limits: Frequent updates might hit rate limits imposed by Short.io. Implement error handling and retries as needed.