Actions20
Overview
This node interacts with the Linq API to manage webhook subscriptions among other resources. Specifically, the Update operation for the Webhook Subscription resource allows you to modify an existing webhook subscription by changing its URL, subscribed events, version, and active status.
Use cases include:
- Updating the callback URL of a webhook subscription when your endpoint changes.
- Modifying which events trigger the webhook notifications.
- Activating or deactivating a webhook subscription without deleting it.
- Changing the webhook version to support new features or API changes.
For example, if you have a webhook subscription that listens to message events but want to add contact update events, you can update the subscription's events list accordingly.
Properties
| Name | Meaning |
|---|---|
| Webhook Subscription ID | The unique identifier of the webhook subscription to update. |
| Webhook URL | The new URL where webhook notifications should be sent. |
| Events | Comma-separated list of event names to subscribe to (e.g., "message.created,message.deleted"). |
| Version | Numeric version of the webhook subscription (default is 2). |
| Active | Boolean flag indicating whether the webhook subscription is active (true) or inactive (false). |
Output
The node outputs the JSON response from the Linq API after updating the webhook subscription. This typically includes the updated webhook subscription object with fields such as its ID, URL, subscribed events, version, active status, and possibly timestamps or metadata.
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
https://api.linqapp.com/api/partner/v2/webhook_subscriptions/{id}using the PUT method. - The API key must be configured in n8n credentials and passed as a header
X-LINQ-INTEGRATION-TOKEN. - The node expects the Linq API to be reachable and responsive.
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 time. Wait at least 10 seconds before retrying.
- Invalid Webhook Subscription ID: Ensure the provided ID exists and is correct; otherwise, the API will return an error.
- Malformed Events List: The events property must be a comma-separated string. Incorrect formatting may cause the API to reject the request.
- Inactive Webhook Not Receiving Calls: If you set
Activeto false, the webhook will not receive events until reactivated. - Authentication Errors: Verify that the API key credential is valid and has sufficient permissions.
Links and References
- Linq API Documentation - Webhook Subscriptions (hypothetical link, replace with actual if available)
- n8n Documentation - Creating Custom Nodes
- Handling Rate Limits in APIs