WbCommunication icon

WbCommunication

n8n node to interact with WB API

Overview

This node interacts with a question management API to retrieve the count of questions within a specified time period. It is useful for scenarios where you need to monitor or report on the volume of questions received or processed over time, such as customer support dashboards or analytics workflows.

For example, you can use this node to:

  • Get the number of answered questions between two dates.
  • Track how many new questions arrived in a given timeframe.
  • Filter counts based on whether questions have been handled or not.

Properties

Name Meaning
Date From Start date of the period (Unix timestamp) from which to count questions.
Date To End date of the period (Unix timestamp) until which to count questions.
Is Answered Filter by question status: true for answered questions, false for unanswered questions.

Output

The node outputs JSON data containing the count of questions matching the specified criteria. The exact structure depends on the API response but typically includes a numeric field representing the total number of questions found.

No binary data output is involved.

Dependencies

  • Requires an API key credential for authentication with the external question management service.
  • The node uses HTTP requests configured with appropriate headers (Accept: application/json, Content-Type: application/json) and a base URL defined in the node's configuration.
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Common issues:

    • Incorrect Unix timestamps may lead to empty or unexpected results.
    • Missing or invalid API credentials will cause authentication failures.
    • Network connectivity problems can prevent successful API calls.
  • Error messages:

    • Authentication errors usually indicate missing or incorrect API keys; verify your credentials.
    • Validation errors may occur if date parameters are malformed; ensure timestamps are valid numbers.
    • Timeout or connection errors suggest network issues; check your internet connection and API endpoint availability.

Links and References

Discussion