Actions20
Overview
This node integrates with the Linq API to manage webhook subscriptions among other resources. Specifically, for the Webhook Subscription - Get One operation, it retrieves detailed information about a single webhook subscription by its ID. This is useful when you want to fetch the current configuration or status of a specific webhook subscription in your Linq account.
Common scenarios include:
- Verifying the details of a webhook subscription before updating or deleting it.
- Auditing webhook subscriptions to ensure they are active and configured correctly.
- Fetching webhook subscription data to use in subsequent workflow steps.
Example: You have a webhook subscription ID and want to retrieve its URL, events subscribed to, version, and active status to confirm it matches your expected setup.
Properties
| Name | Meaning |
|---|---|
| Webhook Subscription ID | The unique identifier of the webhook subscription to retrieve. |
Output
The node outputs a JSON object representing the webhook subscription details as returned by the Linq API. This typically includes fields such as:
id: The webhook subscription's unique ID.webhook_url: The URL where webhook events are sent.events: An array of event names the webhook subscribes to.version: The version number of the webhook subscription.active: A boolean indicating whether the webhook subscription is currently active.- Other metadata related to the webhook subscription.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Linq API.
- The node makes HTTP requests to the Linq API endpoints at
https://api.linqapp.com/api/partner/v2/webhook_subscriptions. - Proper network connectivity to the Linq API service is necessary.
Troubleshooting
- Rate Limit Exceeded: If the node throws an error stating "Rate limit exceeded. Please try again after 10 seconds.", it means too many requests were made in a short period. Wait and retry after some time.
- Invalid Webhook Subscription ID: Providing an incorrect or non-existent webhook subscription ID will likely result in a 404 or similar error from the API. Verify the ID is correct.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
- Network Issues: Connectivity problems can cause request failures; check your internet connection and firewall settings.
Links and References
- Linq API Documentation (general reference for API endpoints and webhook subscriptions)
- n8n Documentation on Credentials (for setting up API authentication)