Actions6
Overview
This node interacts with a URL shortening service API, providing various operations related to managing and retrieving information about shortened URLs. The "Listar URLs" (List URLs) operation specifically fetches a list of shortened URLs from the service, supporting pagination, result limits, sorting options, and filtering by a specific shortened URL.
Common scenarios for this node include:
- Retrieving a paginated list of all shortened URLs managed in an account.
- Filtering to find details about a particular shortened URL.
- Sorting URLs by creation date or number of clicks to analyze link performance.
Practical example:
- A marketing team wants to get the top 50 most recently created shortened URLs to review their campaigns.
- A user wants to look up statistics for a specific shortened URL by entering it directly.
Properties
| Name | Meaning |
|---|---|
| Número Da Página | The page number of results to retrieve (pagination). Defaults to 1. |
| Limite De Resultados | Maximum number of results to return per request. Defaults to 50. |
| Ordenar Por | How to sort the results. Options: "Data" (by date), "Cliques" (by number of clicks). |
| URL Encurtada | Specific shortened URL to search for. If provided, other parameters are ignored. |
Output
The node outputs JSON data representing the list of shortened URLs retrieved from the API. Each item in the output array typically contains details about a shortened URL such as its original URL, shortened form, creation date, click statistics, and possibly campaign-related metadata.
No binary data output is indicated for this operation.
Dependencies
- Requires connection to the URL shortening service 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 shortened URLs available.
- Invalid API credentials: Check that the API key or token is valid and properly configured in n8n.
- Rate limiting or API errors: The API may restrict the number of requests; handle errors gracefully and consider retry logic.
- Filtering by URL ignores other params: When specifying a shortened URL, other filters like page or order are ignored—this is expected behavior.
Links and References
- Refer to the URL shortening service's official API documentation for detailed endpoint descriptions and parameter usage.
- n8n documentation on creating and configuring API credential types for secure access.