WaAPI icon

WaAPI

Interact with WaAPI API
Join our community

Actions85

Overview

This node interacts with the WaAPI API to retrieve information about channels. Specifically, the "Get Channels" operation under the "Channel" resource fetches details of a channel instance by its ID. This is useful in scenarios where you need to programmatically access channel data from WaAPI, such as integrating channel information into workflows, monitoring channel status, or automating channel management tasks.

Practical examples include:

  • Fetching channel details to display in a dashboard.
  • Using channel data to trigger other workflow actions based on channel properties.
  • Automating updates or audits of channel configurations.

Properties

Name Meaning
Id The unique identifier (Instance ID) of the channel to retrieve. This is a required numeric value specifying which channel's data to fetch.

Output

The node outputs JSON data representing the channel details retrieved from the WaAPI API. The structure typically includes all relevant fields describing the channel instance identified by the provided ID. The exact fields depend on the API response but generally contain metadata and configuration details of the channel.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the WaAPI API service.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • The base URL for API requests is https://waapi.app/api/v1.
  • The node uses standard HTTP headers for JSON content negotiation (Accept: application/json and Content-Type: application/json).

Troubleshooting

  • Invalid or missing ID: If the provided channel ID does not exist or is invalid, the API may return an error or empty response. Ensure the ID is correct and corresponds to an existing channel.
  • Authentication errors: Missing or incorrect API credentials will cause authorization failures. Verify that the API key/token is correctly set up in n8n credentials.
  • Network issues: Connectivity problems can prevent reaching the WaAPI endpoint. Check network settings and firewall rules.
  • Unexpected API responses: Changes in the WaAPI API schema might affect the node’s ability to parse responses. Keep the node and API documentation updated.

Links and References

Discussion