Actions6
Overview
This node integrates with the Short.io service to manage and shorten URLs. It allows users to retrieve lists of shortened links, get detailed information about a specific link, create new shortened links, update existing ones, and delete links. This is useful for marketing teams, content creators, or developers who want to programmatically handle URL shortening and tracking within their workflows.
A common scenario is automating the creation of branded short links for campaigns or retrieving analytics-related data on existing links. For example, a user can fetch a list of recently created short links filtered by date or create a new short link with custom parameters like expiration date or UTM tags.
Properties
| Name | Meaning |
|---|---|
| Results To Return | The number of domains (shortened links) to return. Must be at least 1. |
| Additional Fields | Optional filters and sorting options when retrieving the link list: |
| - Before Date | Only return links created before this date. |
| - After Date | Only return links created after this date. |
| - Date Sort Order | Sort order of the returned links by date; options are "Descending" or "Ascending". |
Output
The node outputs JSON data under the field shortIoResponse inside each item's .json property. For the "Get Link List" operation, this includes:
links: An array of link objects representing the retrieved short links.count: Total count of links matching the query.nextPageToken: Token used for pagination to fetch subsequent pages if more results exist.
For other operations (like creating, updating, deleting, or getting info on a single link), the output contains the respective API response object from Short.io under the same shortIoResponse field.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for Short.io to authenticate requests.
- Uses Short.io's REST API endpoints at
https://api.short.io/api. - Pagination is handled internally for large result sets (over 150 items).
Troubleshooting
Common issues:
- Requesting more than 150 results in one call triggers internal pagination; ensure your workflow handles multiple pages correctly.
- Invalid or missing API credentials will cause authentication errors.
- Providing invalid dates or malformed parameters in additional fields may lead to API errors.
Error messages:
- Authentication failures typically indicate incorrect or missing API keys.
- HTTP request errors may occur if the domain ID cannot be resolved or if the Short.io API is unreachable.
- If the node throws an error referencing item indexes, it indicates which input item caused the failure, helping isolate problematic data.
To resolve errors, verify API credentials, check parameter formats, and ensure network connectivity to Short.io's API.