Actions6
Overview
This node interacts with a URL shortening service API, allowing users to manage and retrieve information about shortened URLs. The "Listar URLs" (List URLs) operation fetches a list of shortened URLs from the service, supporting pagination, result limits, sorting, and filtering by a specific shortened URL.
Common scenarios where this node is beneficial include:
- Retrieving a paginated list of all shortened URLs for reporting or monitoring.
- Filtering to find details about a specific shortened URL.
- Sorting URLs by creation date or number of clicks to analyze performance.
Practical example: A marketing team can use this node to list all their campaign URLs sorted by click count to identify the most effective links.
Properties
| Name | Meaning |
|---|---|
| Número Da Página | The page number of results to fetch (pagination). |
| Limite De Resultados | Maximum number of results to return per request. |
| Ordenar Por | How to sort the results; options are "Data" (by date) or "Cliques" (by clicks). |
| URL Encurtada | Specify a particular shortened URL to search for; if provided, other parameters are ignored. |
Output
The node outputs an array of JSON objects representing the shortened URLs retrieved from the API. Each object typically contains details such as the original URL, the shortened URL, creation date, click statistics, and possibly other metadata related to each link.
If binary data were involved (e.g., QR codes or images), it would be included in a separate binary property, but this operation focuses on JSON data only.
Dependencies
- Requires access to the URL shortening service's API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- No additional external dependencies beyond the API and standard HTTP communication.
Troubleshooting
- Empty results: Ensure the page number and limit are set correctly and that the account has existing shortened URLs.
- Invalid API credentials: Check that the API key or token is valid and properly configured in n8n.
- Rate limiting errors: The API may restrict the number of requests; consider adding delays or reducing request frequency.
- Filtering by URL not working: When specifying a shortened URL, other parameters are ignored; ensure the exact short URL string is correct.
Links and References
- Refer to the URL shortening service's official API documentation for detailed endpoint behavior and response formats.
- n8n documentation on creating and configuring API credentials.