WibiClick icon

WibiClick

Interact with WibiClick API
Join our community

Actions92

Overview

This node interacts with the WibiClick API to manage "Note" resources, specifically supporting the "Get" operation among others. The "Get" operation retrieves a single note by its unique Note ID. This is useful in scenarios where you need to fetch detailed information about a specific note associated with a website or user, such as retrieving comments, annotations, or reminders stored as notes.

Practical examples:

  • Fetching a particular note to display its content in a dashboard.
  • Retrieving note details for further processing or integration with other systems.
  • Using the note data to trigger conditional workflows based on note content.

Properties

Name Meaning
Website ID The unique identifier of the website to which the note belongs.
Note ID The unique identifier of the note to retrieve.

Output

The output JSON structure corresponds directly to the response from the WibiClick API for the requested note. It contains all available fields of the note, such as title, content, creation date, and any metadata the API provides.

Example output JSON (simplified):

{
  "id": "note-id-string",
  "title": "Note Title",
  "notes": "Content of the note",
  "createdAt": "2024-01-01T12:00:00Z",
  "userId": "user-id-string",
  ...
}

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the WibiClick API.
  • Requires an API key credential for authentication, passed as a Bearer token in HTTP headers.
  • The node uses HTTP requests to communicate with the WibiClick API endpoints.

Troubleshooting

  • Common issues:

    • Invalid or missing Note ID will result in errors or empty responses.
    • Incorrect or expired API key will cause authentication failures.
    • Network connectivity issues can prevent successful API calls.

  • Error messages:

    • "Failed to create note" (not applicable for Get but shown in code for create).
    • HTTP errors returned by the API are wrapped and thrown as node errors.
    • If the note is not found, the API may return a 404 error, which will be surfaced as an error in the node execution.

  • Resolutions:

    • Ensure the Note ID is correct and exists in the system.
    • Verify that the API key credential is valid and has necessary permissions.
    • Check network connectivity and endpoint URL correctness.

Links and References

Discussion