Actions76
- Chat Actions
- Contact Actions
- Profile Actions
- LID Actions
- File Actions
- Message Actions
- Group Actions
- Create
- List
- Get
- Delete
- Join
- Get Join Info
- Leave
- Get Picture
- Set Picture
- Delete Picture
- Update Subject
- Update Description
- Get Security Info Admin Only
- Set Security Info Admin Only
- Get Security Messages Admin Only
- Set Security Messages Admin Only
- Get Participants
- Add Participant
- Remove Participant
- Promote Admin
- Demote Admin
- Status Actions
- Channel Actions
- Poll Actions
Overview
This node allows users to interact with the Wappfy API, specifically enabling operations related to WhatsApp communication and management. The "Channel" resource's "Search by View" operation lets users search for public channels based on predefined views, filtered optionally by countries and categories, with support for pagination.
Practical scenarios include:
- Discovering recommended or popular WhatsApp channels in specific countries or categories.
- Browsing channels by thematic views without needing to specify exact search text.
- Paginating through large sets of channel results efficiently.
Example use case: A marketing automation workflow that fetches a list of recommended WhatsApp channels in certain countries to analyze or target them for campaigns.
Properties
| Name | Meaning |
|---|---|
| Search View | View type for search (e.g., "RECOMMENDED"). Specifies the predefined view/filter to apply. |
| Countries | Comma-separated list of country codes to filter channels geographically (optional). |
| Categories | Comma-separated list of categories to filter channels by topic or theme (optional). |
| Start Cursor | Cursor string used for pagination to continue fetching subsequent pages of results (optional). |
Output
The output is an array of JSON objects representing the channels matching the search criteria. Each item corresponds to one channel's data as returned by the Wappfy API.
The structure of each JSON object depends on the API response but typically includes channel details such as ID, name, description, category, country, and possibly media like pictures.
No binary data output is involved in this operation.
Dependencies
- Requires an active Wappfy API credential with base URL, instance name, and an API key.
- The node makes HTTP POST requests to the endpoint
/api/{instanceName}/channels/search/by-view. - Proper configuration of the Wappfy API credentials in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing API key or instance name will cause authentication failures.
- Incorrect or unsupported "Search View" values may result in empty or error responses.
- Malformed country or category lists (e.g., improper commas or spaces) might lead to unexpected filtering.
- Pagination cursors must be correctly passed; otherwise, repeated or incomplete results may occur.
Error messages:
- Authentication errors: Check API key validity and credential setup.
- HTTP 400/422 errors: Verify that required parameters like "Search View" are provided and valid.
- Network errors: Ensure connectivity to the Wappfy API endpoint.
Links and References
- Wappfy API Documentation (general reference for API endpoints and parameters)
- n8n documentation on HTTP Request Node for understanding how API calls are made within nodes.