Actions148
- Send messages Actions
- Outbound Messages Actions
- WhatsApp Numbers Actions
- Groups Actions
- Channels Actions
- Chats Actions
- Chat Contacts Actions
- Chat Messages Actions
- Chat Files Actions
- Team Actions
- Labels Actions
- Departments Actions
- Files Actions
- Quick replies Actions
- Queue Actions
- WhatsApp session Actions
- WhatsApp profile Actions
- Business catalog Actions
- Campaigns Actions
- Meeting Links Actions
- User Status Actions
- Webhooks Actions
- Other Actions
Webhooks → Get Webhooks
AI-generatedOverview
This node integrates with the WaliChat WhatsApp API, specifically providing functionality to manage and retrieve webhooks. The "Get Webhooks" operation under the "Webhooks" resource allows users to fetch a list of configured webhooks filtered by various criteria such as device IDs, status, search terms, pagination size, and page number.
Typical use cases include:
- Monitoring webhook configurations associated with specific devices.
- Filtering webhooks by their operational status (active, disabled, pending).
- Searching for webhooks by text to quickly locate relevant entries.
- Paginating through large sets of webhook data for management or auditing purposes.
For example, a user might want to retrieve all active webhooks linked to certain devices to verify their setup or troubleshoot event delivery issues.
Properties
| Name | Meaning |
|---|---|
| Filters | A collection of filters to narrow down the webhooks retrieved: |
| - Device IDs | Select one or multiple device IDs to filter webhooks associated with those devices. |
| - Status | Filter webhooks by their status. Options: Active, Disabled, Pending. |
| - Search Term | Text string to search webhooks by matching text fields. |
| - Results Page Size | Number specifying how many results to return per page (default 20). |
| - Page Number | Number indicating which page of results to retrieve, starting from 0 (default 0). |
Output
The node outputs an array of JSON objects representing the webhooks that match the specified filters. Each object contains the details of a webhook as returned by the WaliChat API. The exact structure depends on the API response but typically includes webhook identifiers, associated device information, status, URL, and other metadata.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the WaliChat WhatsApp API.
- The node relies on the WaliChat API endpoints related to webhook management.
- Proper configuration of the API key credential within n8n is necessary for successful execution.
Troubleshooting
Common Issues:
- Invalid or missing API key credential will cause authentication failures.
- Providing invalid device IDs or unsupported filter values may result in empty responses or errors.
- Pagination parameters out of range could lead to no results being returned.
Error Messages:
- Authentication errors typically indicate issues with the API key; ensure it is correctly set up.
- Validation errors on filters suggest incorrect input types or unsupported values; verify filter inputs.
- Network or API downtime errors require checking connectivity and WaliChat service status.
Links and References
- WaliChat Official API Documentation (replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes
- General info on Webhook Concepts
Note: This summary is based solely on static analysis of the provided source code and property definitions.