WibiClick icon

WibiClick

Interact with WibiClick API
Join our community

Actions92

Overview

This node interacts with the WibiClick API to manage notes and other resources. Specifically, for the Note - Update operation, it updates an existing note's details such as title, description, favorite status, or tag.

Typical use cases include:

  • Modifying the content or metadata of a note after its creation.
  • Marking a note as favorite or changing its categorization via tags.
  • Keeping notes up-to-date in workflows that automate customer or project management.

For example, you might use this node to update a note’s title and description based on new information received from another system or user input.

Properties

Name Meaning
Note ID The unique identifier of the note to update (required).
Update Fields Collection of fields to update on the note. Options include:
- Title: New title of the note.
- Description: New content of the note.
- Is Favorite: Boolean flag indicating if the note is marked as favorite.
- Tag: A tag string to categorize or label the note.

Output

The output JSON contains the response from the WibiClick API after updating the note. It typically includes the updated note object or confirmation data returned by the API.

Example output structure:

{
  "json": {
    "id": "note-id",
    "title": "Updated Title",
    "description": "Updated content",
    "isFav": true,
    "tag": "new-tag",
    // ...other note properties as returned by the API
  }
}

No binary data output is involved in this operation.

Dependencies

  • Requires access to the WibiClick API.
  • Needs an API key credential configured in n8n for authentication.
  • The node uses HTTP requests to communicate with the API endpoints.

Troubleshooting

  • Common issues:

    • Invalid or missing Note ID will cause the update to fail.
    • Providing no fields in "Update Fields" may result in no changes or errors.
    • Network or authentication errors if the API key is invalid or missing.

  • Error messages:

    • "Failed to create note" (not applicable here but similar errors may occur if update fails).
    • HTTP errors from the API are propagated; ensure the Note ID exists and the API key is valid.
    • If the node throws an error about missing parameters, verify all required inputs are provided.

  • Resolution tips:

    • Double-check the Note ID is correct and corresponds to an existing note.
    • Ensure at least one field in "Update Fields" is set to update.
    • Confirm the API key credential is correctly set up and has necessary permissions.

Links and References

Discussion