Overview
This node listens for webhook events from TailURL, a URL shortening and tracking service. It triggers workflows in n8n when specific events occur related to shortened URLs, QR codes, analytics thresholds, or team member changes.
Common scenarios where this node is useful include:
- Automating marketing workflows when a shortened URL is clicked.
- Tracking QR code scans to trigger follow-up actions.
- Monitoring analytics thresholds to alert teams or adjust campaigns.
- Responding to URL creation, updates, or deletions to sync data elsewhere.
- Reacting to team membership changes for access control or notifications.
For example, you could use this node to start a workflow that sends an email notification whenever a shortened URL is clicked or to update a CRM system when a new URL is created.
Properties
| Name | Meaning |
|---|---|
| Event | The specific TailURL event that triggers the webhook. Options include: All Events, Analytics Threshold, QR Code Generated, QR Code Scanned, Team Member Changes, URL Clicked, URL Created, URL Deleted, URL Updated. |
| Webhook Secret | Optional secret string used to verify the webhook payload via HMAC signature for security. Recommended to prevent unauthorized requests. |
| Team Name or ID | Optional filter to restrict events to a specific team. You can select from your available teams or specify an ID using an expression. |
| URL Filters | Optional filters to limit triggering events based on URL properties: ā¢ Custom Slug Pattern ā only trigger if the URL slug matches this wildcard pattern. ā¢ Domain Filter ā only trigger if the URL belongs to this domain. |
Output
The node outputs JSON data representing the webhook event received from TailURL. The output includes all event details sent by TailURL, augmented with metadata about the webhook:
webhook.url: The URL of the webhook endpoint.webhook.event: The event type that triggered the webhook.webhook.timestamp: The timestamp when the event was processed.webhook.verified: Boolean indicating whether the webhook signature was successfully verified (if a secret was provided).
If the webhook secret is set, the node verifies the HMAC SHA256 signature included in the request headers to ensure authenticity. If verification fails, the output contains an error message instead of event data.
No binary data is output by this node.
Dependencies
- Requires an API key credential for TailURL to manage webhook registration and load team options.
- Uses TailURL's REST API endpoints to create, check, and delete webhooks.
- Optionally requires a webhook secret configured both in TailURL and this node for secure signature verification.
- The node depends on n8n's HTTP request helper methods and crypto module for signature validation.
Troubleshooting
- Invalid webhook signature: If the webhook secret is set but the signature does not match, the node outputs an error JSON. Ensure the secret configured in TailURL matches exactly the one in this node.
- Webhook creation failure: Errors during webhook setup may indicate invalid API credentials or insufficient permissions. Verify the API key and its access rights.
- No events triggering: Check that the selected event matches the incoming webhook event. Also verify URL filters if set; they may block some events unintentionally.
- Failed to load teams: This usually means the API key is missing, invalid, or lacks permission to list teams. Confirm credentials are correct and have necessary scopes.
Links and References
- TailURL API Documentation (for webhook and team management)
- n8n Expressions Documentation (for dynamic property values)
- HMAC Signature Verification (conceptual background)