Actions76
- Message Actions
- Chat Actions
- Contact 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
- Profile Actions
- LID Actions
- File Actions
Overview
This node enables searching for public channels using a predefined "view" filter through the Wappfy API. It is useful when you want to discover or explore channels based on specific curated views, such as recommended channels or other categorized views provided by the service.
Typical use cases include:
- Finding popular or recommended channels in certain countries or categories.
- Browsing channels with pagination support.
- Filtering channel search results by country codes and categories.
For example, you might use this node to retrieve a list of recommended channels available in the US and Canada under the "Technology" category, helping you to integrate or analyze channel data relevant to your audience.
Properties
| Name | Meaning |
|---|---|
| Search View | The view type used for searching channels. Example values: "RECOMMENDED", etc. |
| Countries | Comma-separated list of country codes to filter the search results (e.g., "US,CA"). |
| Categories | Comma-separated list of categories to filter the search results (e.g., "Technology"). |
| Start Cursor | Cursor string for pagination to fetch subsequent pages of results. |
Output
The output is an array of JSON objects representing the channels found by the search query. Each item corresponds to a channel's data returned by the Wappfy API.
The exact structure depends on the API response but typically includes channel details such as ID, name, description, and possibly metadata related to the channel's view, country, and category.
No binary data output is produced by this operation.
Dependencies
- Requires an active Wappfy API credential with a valid API key and instance name configured in n8n.
- The node makes HTTP requests to the Wappfy API base URL specified in the credentials.
- Proper network access to the Wappfy API endpoints is necessary.
Troubleshooting
- Invalid API Key or Instance Name: If authentication fails, verify that the API key and instance name are correctly set in the credentials.
- Empty or No Results: Ensure that the "Search View" value is valid and that any country or category filters match existing data.
- Pagination Issues: When using the "Start Cursor" property, ensure the cursor value is correct and obtained from previous responses.
- API Rate Limits or Downtime: If requests fail unexpectedly, check for API rate limits or service availability issues.
Common error messages will be those returned by the Wappfy API, such as unauthorized access or invalid parameters. Review the error message details in the node output to diagnose.
Links and References
- Wappfy API Documentation (Assumed official docs for reference)
- n8n Documentation on HTTP Request Node (for understanding HTTP calls)
This summary is based solely on static analysis of the provided source code and input properties.