BeeAI icon

BeeAI

Interact with BeeAI API

Actions16

Overview

The node interacts with the BeeAI API to list facts stored or managed by the service. It allows users to retrieve a paginated list of facts, optionally filtered by whether the fact is confirmed. This node is useful in scenarios where you want to programmatically access factual data maintained by BeeAI, such as for knowledge bases, data validation, or content enrichment.

Practical examples include:

  • Fetching all confirmed facts to display in an application.
  • Retrieving a specific page of facts when dealing with large datasets.
  • Filtering facts based on their confirmation status to ensure data quality.

Properties

Name Meaning
Filter A collection of filters to narrow down the facts returned.
  Confirmed Boolean option to filter facts by their confirmation status (true = confirmed).
Pagination Controls for paginating through the list of facts.
  Page Number The page number to fetch (minimum 1).
  Number of Items per Page Maximum number of results to return per page (minimum 1).

Output

The node outputs JSON data containing the list of facts retrieved from the BeeAI API. Each item in the output corresponds to a fact object as defined by the API's response schema. The output does not include binary data.

Typical structure of each fact in the json output might include fields such as the fact's content, confirmation status, and any metadata provided by the API (not explicitly detailed in the source).

Dependencies

  • Requires an API key credential for authenticating with the BeeAI API.
  • The node sends requests to the base URL: https://api.bee.computer.
  • Proper configuration of the API key credential within n8n is necessary for successful operation.

Troubleshooting

  • Common issues:

    • Invalid or missing API key will result in authentication errors.
    • Requesting pages beyond the available range may return empty results.
    • Using invalid filter values (e.g., non-boolean for "Confirmed") could cause request failures.

  • Error messages:

    • Authentication errors typically indicate problems with the API key setup.
    • HTTP 4xx or 5xx errors suggest issues with request parameters or server availability.

  • Resolutions:

    • Verify that the API key credential is correctly configured and active.
    • Ensure pagination parameters are within valid ranges.
    • Confirm that filter values conform to expected types.

Links and References

Discussion