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 → Create Webhook
AI-generatedOverview
This node integrates with the WaliChat WhatsApp API to manage webhooks. Specifically, the Create Webhook operation allows users to register a webhook URL that will receive HTTP POST notifications when specified WhatsApp-related events occur. This is useful for automating workflows based on real-time WhatsApp activity, such as inbound or outbound messages, status updates, group changes, and more.
Practical examples include:
- Automatically processing new inbound WhatsApp messages by triggering downstream automation.
- Tracking message delivery statuses or failures to update CRM records.
- Monitoring group or chat updates to synchronize with external systems.
- Receiving session status updates to manage device connectivity.
Properties
| Name | Meaning |
|---|---|
| Webhook Name | Internal identifier for the webhook (max 30 characters). |
| Webhook URL | Publicly accessible endpoint URL that will receive HTTP POST requests when the selected events occur. |
| Event Types | List of event types to subscribe to. Options include: - New Inbound Message - New Outbound Message - Outbound Message Sent - Outbound Message Delivery Status - Outbound Message Failed - Message Updated - Message Reaction - Channel Message Received - Status Update - Group Update - Chat Update - Contact Update - WhatsApp Session Status |
| Device ID (Optional) | Restrict webhook notifications to a specific WhatsApp device identified by a 24-character hexadecimal ID. |
Output
The node outputs JSON data representing the result of the webhook creation request. This typically includes details about the created webhook such as its ID, name, subscribed events, target URL, and associated device if specified.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the WaliChat WhatsApp API via an API key credential.
- The webhook URL must be publicly accessible to receive HTTP POST callbacks from WaliChat.
- The node depends on internal methods handling webhook operations within the bundled source code.
Troubleshooting
Common Issues:
- Invalid or unreachable webhook URL: Ensure the URL is publicly accessible and can accept POST requests.
- Missing required properties: The webhook name, URL, and at least one event type are mandatory.
- Device ID restriction errors: If specifying a device ID, verify it matches a valid registered device.
- API authentication failures: Confirm the API key credential is correctly configured and has necessary permissions.
Error Messages:
- Errors related to invalid parameters usually indicate missing or malformed input fields.
- Network or permission errors may arise if the webhook URL is not reachable or the API key lacks rights.
- To resolve, double-check all inputs, ensure network accessibility, and validate credentials.
Links and References
- WaliChat API Documentation (hypothetical link)
- Webhook Concepts and Best Practices
- n8n Webhook Node Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.webhook/ (for general webhook usage concepts)