WibiClick icon

WibiClick

Interact with WibiClick API
Join our community

Actions92

Overview

This node interacts with the WibiClick API to manage "notes" among other resources. Specifically, for the Note - Get Many operation, it retrieves multiple notes associated with a specified website. This is useful when you want to fetch a list of notes for display, reporting, or further processing in your workflow.

Typical use cases include:

  • Fetching all notes related to a particular website for review or analysis.
  • Paginating through large sets of notes by specifying limits and offsets.
  • Integrating note data into dashboards or other systems.

Example: Retrieve up to 50 notes from a website identified by its ID, starting from the first note (offset 0).

Properties

Name Meaning
Website ID The unique identifier of the website whose notes you want to retrieve.
Limit Maximum number of notes to return in one request. Useful for pagination (e.g., 50).
Offset Number of notes to skip before starting to collect the result set. Used for pagination.

Output

The output is an array of JSON objects representing the notes retrieved from the WibiClick API. Each item corresponds to a note and contains the fields as returned by the API under the json property.

Example structure of one output item:

{
  "json": {
    "notes": [
      {
        "id": "note-id-1",
        "title": "Note Title 1",
        "content": "Content of the note",
        "createdAt": "2024-01-01T12:00:00Z",
        ...
      },
      {
        "id": "note-id-2",
        "title": "Note Title 2",
        "content": "Another note content",
        "createdAt": "2024-01-02T08:30:00Z",
        ...
      }
    ]
  }
}

No binary data is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the WibiClick API.
  • The node uses HTTP GET requests to the endpoint /notes with query parameters for website ID, limit, and offset.
  • The base URL for the API is provided via credentials configuration.

Troubleshooting

  • Empty results: Ensure the Website ID is correct and that there are notes available for that website.
  • Invalid API key or authentication errors: Verify that the API key credential is correctly configured and has necessary permissions.
  • Pagination issues: If you receive fewer notes than expected, check the limit and offset values.
  • API errors: The node throws errors if the API response does not contain expected data. Check network connectivity and API status.
  • Rate limiting: If many requests are made rapidly, the API might throttle requests; implement retries or backoff as needed.

Links and References

Discussion