Actions99
- Expenses Actions
- Group Accounts Actions
- Group Account Codes Actions
- Accounts Actions
- Purchase Orders Actions
- Get A List Of Purchase Orders
- Create A New Purchase Order
- Get A Purchase Order
- Update A Purchase Order
- Open A Purchase Order
- Get A List Of Purchase Orders Items For A Specific Purchase Order
- Create A Purchase Order Item
- Get A Purchase Order Item
- Update A Purchase Order Item
- Delete A Purchase Order Item
- Get A List Of Goods Received Notes For A Specific Purchase Order
- Create A Goods Received Note
- Attach A File To A Goods Received Note
- Delete A Goods Received Note
- Suppliers Actions
- Fund Accounts Actions
- Cards Actions
- Expense Categories Actions
- Tax Rates Actions
- Amortizations Actions
- Account Teams Actions
- Account Codes Actions
- External Teams Actions
- Custom Fields Actions
- Get Custom Fields
- Create A New Custom Field
- Get Custom Field
- Update Custom Field
- Delete A Custom Field And All Its Values
- Get Custom Field Values
- Create A Custom Field Value
- Delete Custom Field Values
- Get A Custom Field Value
- Update A Custom Field Value
- Delete A Custom Field Value
- Get Managers For A Specific Custom Field Value
- Adds Managers For A Specific Custom Field Value
- Replaces Managers For A Specific Custom Field Value
- Removes Managers For A Specific Custom Field Value
- Webhook Subscriptions Actions
- Group Teams Actions
Overview
This node operation removes a webhook subscription from an account. It is useful when you want to stop receiving webhook notifications for a specific subscription, effectively disabling the integration or event forwarding associated with that subscription.
Common scenarios include:
- Cleaning up unused or obsolete webhook subscriptions.
- Managing webhook lifecycle by programmatically removing subscriptions when they are no longer needed.
- Automating subscription management in workflows that handle multiple accounts or services.
Example: If you have set up webhook subscriptions to receive event notifications from an external service and want to revoke one subscription due to changes in your workflow or security reasons, this operation allows you to remove it by specifying the account and subscription identifiers.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account from which the webhook subscription will be removed. |
| Subscription Id | Identifier of the webhook subscription to be removed. |
Output
The output JSON typically contains confirmation details about the removal of the webhook subscription. This may include status information or metadata confirming that the subscription was successfully deleted.
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to authorize requests against the external service managing webhook subscriptions.
- The node depends on the external service's API endpoint that handles webhook subscription deletion.
- Proper base URL configuration for the API is necessary (usually provided via credentials).
Troubleshooting
- Invalid Account Id or Subscription Id: Ensure that both identifiers are correct and correspond to existing resources in the external service.
- Authentication Errors: Verify that the API key or authentication token is valid and has sufficient permissions to delete webhook subscriptions.
- Network Issues: Check connectivity to the external API endpoint.
- Permission Denied: The authenticated user might lack rights to remove the subscription; check roles and permissions.
- Subscription Not Found: If the subscription ID does not exist or was already removed, the API may return an error indicating the resource was not found.
Resolving these issues usually involves verifying input parameters, checking credentials, and ensuring the external service is reachable and operational.
Links and References
- Refer to the external service’s official API documentation for webhook subscription management.
- Consult n8n documentation on setting up API credentials and handling HTTP request nodes for additional context on authentication and error handling.