Overview
This node integrates with the TailURL API to manage webhooks, URLs, QR codes, and analytics related to URL shortening and tracking. Specifically, the Create Webhook operation allows users to create webhook endpoints that listen for specific events such as URL creation, clicks, QR code scans, and team member changes. This is useful for automating workflows triggered by these events, for example:
- Automatically notifying a Slack channel when a new shortened URL is created.
- Triggering downstream processes when a QR code is scanned.
- Keeping an audit log of URL updates or deletions.
By creating webhooks, users can build reactive automations that respond in real-time to activities within their TailURL account.
Properties
| Name | Meaning |
|---|---|
| Team Name or ID | Select the team context for this webhook (optional). Choose from a list or specify an ID via expression. |
| Webhook Name | The name assigned to the webhook for identification purposes. |
| Endpoint URL | The URL where webhook event payloads will be sent (the webhook listener endpoint). |
| Events | List of events to subscribe to. Options include: Analytics Threshold, QR Code Generated, QR Code Scanned, Team Member Changes, URL Clicked, URL Created, URL Deleted, URL Updated. Default subscribes to URL Created and URL Clicked. |
Output
The node outputs a JSON object representing the response from the TailURL API after attempting to create the webhook. This typically includes details about the newly created webhook such as its ID, name, subscribed events, endpoint URL, and associated team if specified.
Example output structure (simplified):
{
"success": true,
"webhook": {
"id": "webhook_123456",
"name": "n8n Automation Hook",
"endpointUrl": "https://your-n8n.com/webhook/unique-ID",
"events": ["url.created", "url.clicked"],
"teamId": "team_789"
}
}
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the TailURL API.
- The node makes HTTP requests to
https://tailurl.com/api/webhooksendpoint. - Proper configuration of the TailURL API credentials in n8n is necessary.
- The webhook endpoint URL must be accessible and able to receive POST requests from TailURL.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Incorrect or unreachable webhook endpoint URL may result in failed webhook creation or delivery.
- Subscribing to events without proper permissions might lead to access denied errors.
Error messages:
"Failed to create webhook: <error message>"indicates the API returned an error; check the error details for causes like invalid parameters or permission issues.- Authentication errors suggest verifying the API key credential setup.
- Network errors imply checking connectivity and endpoint URL correctness.
Resolution tips:
- Ensure the API key credential is correctly configured and has required permissions.
- Verify the webhook endpoint URL is publicly accessible and responds correctly.
- Confirm selected events are valid and supported by your TailURL account.
Links and References
- TailURL API Documentation (for detailed API usage and event types)
- n8n Expressions Documentation (for using expressions in property fields)