Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node operation removes a webhook subscription from an account. It is useful when you want to stop receiving event notifications or callbacks that were previously set up via a webhook subscription. For example, if you no longer need to monitor certain events or want to clean up unused subscriptions, this operation allows you to delete the subscription by specifying its unique identifier.

Properties

Name Meaning
Account Id Identifier of the account from which to remove the webhook subscription.
Subscription Id Identifier of the specific 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 identifiers confirming the deletion. The node does not output binary data.

Dependencies

  • Requires an API key credential or similar authentication token configured in n8n to authorize requests.
  • Depends on connectivity to the external service managing webhook subscriptions (the exact service is abstracted here).
  • No additional environment variables are explicitly required beyond standard API credentials.

Troubleshooting

  • Common issues:
    • Invalid or missing Account Id or Subscription Id will cause the operation to fail.
    • Authentication errors if the API key or token is incorrect or expired.
    • Network connectivity problems can prevent successful API calls.
  • Error messages:
    • "Subscription not found" indicates the Subscription Id does not exist or is already deleted.
    • "Unauthorized" or "Authentication failed" suggests issues with the provided API credentials.
  • Resolutions:
    • Verify that both Account Id and Subscription Id are correct and correspond to existing resources.
    • Ensure API credentials are valid and have sufficient permissions.
    • Check network access and retry if transient errors occur.

Links and References

  • Refer to the external service’s API documentation for webhook subscription management for detailed behavior and error codes.
  • n8n documentation on configuring API credentials and using HTTP request nodes may provide additional context.

Discussion