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
Other → Send API request
AI-generatedOverview
This node allows users to send custom API requests directly to the WaliChat WhatsApp API under the "Other" resource with the "Send API request" operation. It is designed for advanced use cases where predefined operations do not cover specific API endpoints or when users want to interact with new or less common API features by specifying their own HTTP method, endpoint path, headers, URL parameters, and JSON body.
Typical scenarios include:
- Accessing experimental or undocumented API endpoints.
- Performing batch operations or custom queries not supported by standard node operations.
- Integrating with additional WaliChat API features as they become available without waiting for node updates.
Example: Sending a POST request to /custom-endpoint with specific headers and a JSON payload to trigger a custom workflow in WaliChat.
Properties
| Name | Meaning |
|---|---|
| API endpoint | The URL path appended to the base URL https://api.wali.chat/v1. Example: /messages/send. |
| HTTP Method | The HTTP method used for the request. Options: GET, POST, PUT, PATCH, DELETE. |
| Headers | Key-value pairs of HTTP headers to include in the request. |
| URL Params | Key-value pairs of URL query parameters appended to the endpoint URL. |
| Body | JSON-formatted string representing the request body. Required only for POST, PUT, PATCH, DELETE methods. |
Output
The node outputs a JSON object containing the response from the WaliChat API corresponding to the custom request made. The structure of this JSON depends entirely on the API endpoint called and the data returned by that endpoint.
If the API returns binary data (not typical for this operation), it would be included in the binary output field, but this node primarily handles JSON responses.
Dependencies
- Requires an API key credential for authenticating with the WaliChat API.
- The base URL for all requests is fixed as
https://api.wali.chat/v1. - No other external dependencies are required.
- Proper network access to the WaliChat API endpoint must be configured.
Troubleshooting
- Invalid URL Path: If the API endpoint path is incorrect or does not exist, the API will return an error. Verify the endpoint path matches the WaliChat API documentation.
- Authentication Errors: Missing or invalid API key credentials will cause authentication failures. Ensure the API key is correctly configured in the node credentials.
- Malformed JSON Body: For methods requiring a body, ensure the JSON is valid and properly formatted; otherwise, the API may reject the request.
- Unsupported HTTP Method: Only GET, POST, PUT, PATCH, and DELETE are supported. Using others will cause errors.
- Header or Parameter Issues: Incorrect headers or URL parameters can lead to unexpected API responses or errors. Double-check keys and values.
- API Rate Limits: Excessive requests may be throttled by the API. Implement retry logic or reduce request frequency if needed.
Links and References
- WaliChat API Documentation (Assumed official docs URL)
- n8n Documentation on HTTP Request Node for general concepts of sending custom API requests.