Actions85
- Instances Actions
- Client Actions
- Message Actions
- Chat Actions
- Contact Actions
- Number Actions
- Group Actions
- Channel Actions
- Label Actions
- Story Actions
Overview
This node interacts with the WaAPI API to retrieve information about blocked contacts. Specifically, the "Get Blocked Contacts" operation under the "Contact" resource fetches details of contacts that have been blocked in the system identified by a given instance ID.
Common scenarios for this node include:
- Managing contact lists by identifying which contacts are blocked.
- Automating workflows that need to handle or report on blocked contacts.
- Integrating blocked contact data into CRM or customer support systems.
For example, a user might use this node to periodically check and export all blocked contacts from their messaging platform to update their internal records or trigger follow-up actions.
Properties
| Name | Meaning |
|---|---|
| Id | Instance ID (number) - The unique identifier of the instance from which to retrieve blocked contacts. This is a required field. |
Output
The node outputs JSON data containing the list of blocked contacts retrieved from the WaAPI API. Each item in the output typically represents a blocked contact with its associated details as provided by the API response.
If the API supports binary data related to contacts (e.g., profile pictures), it would be included accordingly, but based on the code and operation, the primary output is structured JSON data representing blocked contacts.
Dependencies
- Requires an API key credential for authenticating with the WaAPI API.
- The node uses the base URL
https://waapi.app/api/v1for API requests. - The node depends on the external package
@devlikeapro/n8n-openapi-nodefor building properties and handling OpenAPI specifications.
Troubleshooting
- Missing or invalid Instance ID: Since the "Id" property is required, ensure it is provided and valid; otherwise, the API call will fail.
- Authentication errors: Verify that the API key credential is correctly configured and has the necessary permissions.
- Network issues: Ensure that the n8n instance can reach
https://waapi.app/api/v1. - Unexpected API responses: If the API changes or returns errors, check the API documentation and update credentials or node configuration accordingly.