TailURL icon

TailURL

Interact with TailURL API for URL shortening, QR codes, and analytics
Join our community

Actions7

Overview

This node integrates with the TailURL API to manage URL shortening, QR code generation, analytics retrieval, and webhook management. It is useful for automating workflows involving URL tracking, marketing campaigns, or any scenario where shortened URLs and their analytics are needed.

For the List URLs operation specifically, the node fetches a paginated list of URLs associated with a team (or the default account if no team is specified). This is beneficial when you want to retrieve and process multiple shortened URLs in bulk, for example, to analyze usage patterns or to export URL data.

Practical Example

  • Retrieve the first 50 URLs created under a specific team to display them in a dashboard.
  • Paginate through all URLs by adjusting the offset to process large URL sets in batches.

Properties

Name Meaning
Team Name or ID Select the team whose URLs you want to list. You can choose from a dropdown of teams or specify an ID via expression. Optional; if empty, defaults to the main account's URLs.
Limit Maximum number of URLs to return in one request. Must be at least 1. Default is 50.
Offset Number of URLs to skip for pagination purposes. Must be 0 or greater. Default is 0.

Output

The output JSON contains the response from the TailURL API listing URLs. It typically includes metadata about each URL such as its ID, original URL, shortened URL, creation date, and possibly other related properties depending on the API response.

Example structure (simplified):

{
  "success": true,
  "urls": [
    {
      "id": "url_123456",
      "originalUrl": "https://example.com",
      "shortUrl": "https://short.ly/abc123",
      "createdAt": "2024-01-01T12:00:00Z",
      ...
    },
    ...
  ],
  "total": 100,
  "limit": 50,
  "offset": 0
}

No binary data is output by this operation.

Dependencies

  • Requires an API key credential for the TailURL service configured in n8n.
  • The node makes authenticated HTTP requests to https://tailurl.com/api/urls.
  • Pagination parameters (limit and offset) control the subset of URLs returned.

Troubleshooting

  • Common issues:

    • Invalid or missing API key credential will cause authentication failures.
    • Specifying a non-existent team ID may result in empty results or errors.
    • Exceeding API rate limits could cause temporary request failures.

  • Error messages:

    • "Failed to list URLs: <error message>" indicates the API call did not succeed. Check your API key, permissions, and network connectivity.
    • If the error mentions unauthorized access, verify that the API key has permission to access the requested team's URLs.
    • Pagination parameters must be valid numbers; otherwise, the API might reject the request.

Links and References

Discussion