WaAPI icon

WaAPI

Interact with WaAPI API

Actions83

Overview

This node interacts with the WaAPI API to retrieve information about blocked contacts. Specifically, for the "Contact" resource and the "Get Blocked Contacts" operation, it fetches a list or details of contacts that have been blocked in the system identified by an instance ID.

Common scenarios where this node is useful include:

  • Managing contact lists by identifying which contacts are blocked.
  • Automating workflows that need to handle blocked contacts differently, such as excluding them from marketing campaigns.
  • Auditing or reporting on blocked contacts within a communication platform.

Example: A user wants to automatically fetch all blocked contacts from their messaging service to update their CRM or notify a team member.

Properties

Name Meaning
Id Instance ID (number) - The unique identifier of the instance from which to retrieve blocked contacts. This property is required.

Output

The node outputs JSON data containing the details of the blocked contacts retrieved from the WaAPI API. The exact structure depends on the API response but typically includes contact identifiers, status, and related metadata.

If the API supports binary data (e.g., attachments or media), the node would handle it accordingly, but based on the provided code and operation, the output is primarily JSON.

Dependencies

  • Requires an API key credential for authenticating with the WaAPI API.
  • The node uses the base URL https://waapi.app/api/v1 to make requests.
  • The node depends on the external package @devlikeapro/n8n-openapi-node for building properties and handling OpenAPI specifications.

Troubleshooting

  • Missing or invalid API credentials: Ensure that a valid API key credential is configured in n8n for the WaAPI service.
  • Invalid Instance ID: The "Id" property must be a valid number corresponding to an existing instance; otherwise, the API may return errors or empty results.
  • Network issues: Connectivity problems to https://waapi.app/api/v1 will cause request failures.
  • API rate limits or permissions: If the API key lacks necessary permissions or exceeds rate limits, the node will fail to retrieve data.

Links and References

Discussion