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, webhooks, QR code generation, and analytics. It is useful for automating workflows that involve creating short URLs, tracking their usage, generating QR codes for easy sharing, and managing webhook subscriptions for real-time event notifications.

For the List Webhooks operation specifically, the node retrieves all webhook endpoints associated with a team or the default account. This is beneficial when you want to monitor or audit existing webhook configurations or use them in further automation steps.

Practical Example

  • Automatically fetch all webhooks for a marketing team to verify which events are being tracked.
  • Use the list of webhooks to dynamically update or delete outdated webhook endpoints in your system.

Properties

Name Meaning
Team Name or ID Select the team for this operation (optional). Choose from the list of teams or specify an ID using an expression. If left empty, defaults to the main account's team.

Output

The output is a JSON object containing the response from the TailURL API listing the webhooks. The structure typically includes:

  • success: Boolean indicating if the request was successful.
  • webhooks: An array of webhook objects, each representing a webhook endpoint with details such as its ID, name, subscribed events, and endpoint URL.

Example output snippet:

{
  "success": true,
  "webhooks": [
    {
      "id": "webhook_123",
      "name": "n8n Automation Hook",
      "endpointUrl": "https://your-n8n.com/webhook/unique-ID",
      "events": ["url.created", "url.clicked"],
      "teamId": "team_456"
    }
  ]
}

No binary data is produced by this operation.

Dependencies

  • Requires an API key credential for the TailURL API configured in n8n.
  • Network access to https://tailurl.com/api/webhooks endpoint.
  • Optional: Team context requires the ability to load teams via the API.

Troubleshooting

  • Invalid API Credentials: If the API key is missing or incorrect, the node will fail to authenticate. Ensure the API key credential is properly set up.
  • Access Denied Errors: If the API key lacks permission to access team data or webhooks, check the permissions associated with the API key.
  • Failed to List Webhooks: Could be due to network issues or API downtime. Verify connectivity and TailURL service status.
  • Empty Webhook List: May indicate no webhooks exist for the specified team or default account.

If errors occur, the node throws descriptive messages including the error returned by the API, aiding diagnosis.

Links and References

Discussion