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 provide URL shortening and related functionalities such as generating QR codes, managing webhooks, retrieving analytics, and listing URLs. The "Shorten URL" operation specifically creates a new shortened URL from a provided long URL, optionally allowing customization of the slug and title, and associating it with a team.

Common scenarios where this node is beneficial include:

  • Creating short, shareable links for marketing campaigns or social media.
  • Customizing short URLs with branded slugs for better recognition.
  • Organizing URLs under different teams or projects.
  • Automating URL shortening workflows within larger automation sequences.

Practical example:

  • Automatically shorten URLs generated by an e-commerce platform before sharing them in newsletters.
  • Generate custom short links with specific slugs for tracking campaign performance.

Properties

Name Meaning
Original URL The long URL that you want to shorten.
Custom Slug Optional custom identifier appended to the shortened URL instead of a random string.
Title Optional descriptive title for the shortened URL.
Team Name or ID Optionally select or specify the team under which the shortened URL will be created.

Output

The output JSON contains the full response from the TailURL API after creating the shortened URL. This typically includes details such as:

  • The shortened URL itself.
  • The original URL.
  • Any custom slug used.
  • Associated metadata like title and team information.
  • Status or success indicators.

No binary data is output by this operation.

Dependencies

  • Requires an API key credential for authenticating with the TailURL API.
  • Network access to https://tailurl.com/api/urls endpoint.
  • Proper configuration of the TailURL API credentials in n8n is necessary.

Troubleshooting

  • Invalid API Credentials: If the API key is missing or incorrect, requests will fail. Ensure the API key credential is configured correctly.
  • Permission Denied: If the API key lacks permissions for the selected team, operations may return access errors.
  • Custom Slug Conflicts: Using a custom slug that already exists may cause the API to reject the request.
  • Missing Required Fields: The "Original URL" is mandatory; omitting it will cause errors.
  • API Errors: The node throws errors if the API response indicates failure, including error messages returned by the API.

To resolve these issues:

  • Verify API credentials and permissions.
  • Use unique custom slugs.
  • Provide all required parameters.
  • Check network connectivity to the TailURL service.

Links and References

Discussion