Actions99
- Group Accounts Actions
- Group Account Codes Actions
- Accounts Actions
- Expenses 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 retrieves webhook subscriptions associated with a specific account. It is useful when you want to programmatically fetch and manage the list of webhook subscriptions tied to an account in an external service. For example, you might use this node to audit active webhooks, verify subscription statuses, or synchronize webhook data with other systems.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account whose webhook subscriptions you want to retrieve |
Output
The output JSON contains the details of the webhook subscriptions for the specified account. Each item in the output typically represents a webhook subscription object, including information such as subscription ID, event types subscribed to, callback URLs, status, and other metadata related to the webhook subscription.
If the node supports binary data output (not indicated here), it would represent any binary payloads received or processed, but based on the provided code and properties, the output is purely JSON data describing webhook subscriptions.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to access the external service's API.
- The node depends on an OpenAPI specification (
payhawk.api.json) bundled within the node implementation to define available operations and their parameters. - The base URL for API requests is expected to be set via credentials or environment variables.
Troubleshooting
- Missing or invalid Account Id: Ensure that the "Account Id" property is provided and correctly corresponds to an existing account in the external system.
- Authentication errors: Verify that the API key or authentication token is valid and has sufficient permissions to read webhook subscriptions.
- Network issues: Check connectivity to the external API endpoint and confirm that the base URL is correctly configured.
- Empty results: If no webhook subscriptions are returned, confirm that the account actually has active webhook subscriptions.
Common error messages may include:
- Unauthorized or 401 errors indicating invalid credentials.
- 404 errors if the account ID does not exist.
- Timeout or network errors if the API endpoint is unreachable.
Resolving these usually involves verifying credentials, input parameters, and network configurations.
Links and References
- Refer to the external service’s API documentation for detailed information about webhook subscriptions and their schema.
- Consult n8n documentation on how to configure API credentials and use HTTP request nodes for custom integrations.