Blocklet ServerInstall

Overview

This node interacts with the Blocklet Server API to manage user-related data within a Blocklet app (team). Specifically, the "Update User Tags" operation updates the tags associated with a particular user identified by their DID (Decentralized Identifier) in the context of a given app DID. This is useful for categorizing or labeling users dynamically based on custom criteria, enabling better organization, filtering, and targeted actions.

Common scenarios:

• Tagging users based on behavior or attributes for segmentation.
• Updating user metadata to reflect changes in status or roles.
• Automating workflows that depend on user tags, such as notifications or access control.

Example:
You have an app with DID app123 and want to update the tags of a user with DID user456 to include tags like "premium", "betaTester". This node will send those tag updates to the Blocklet Server API to keep user metadata current.

Properties

Output

The output JSON contains the response from the Blocklet Server API after updating the user's tags. It typically includes confirmation of the update and possibly the updated user object with new tags applied.

No binary data output is involved in this operation.

Dependencies

• Requires an API key credential for authenticating requests to the Blocklet Server API.
• The node depends on the internal helper function blockletServerApiRequest to perform HTTP requests.
• No additional external services beyond the Blocklet Server API are required.

Troubleshooting

• Common issues:

  • Invalid or missing App DID or User DID parameters will cause the API call to fail.
  • Providing tags in an incorrect format (e.g., not as strings or including invalid characters) may result in errors.
  • Network or authentication failures if the API key credential is misconfigured.

• Error messages:

  • "Not implemented user action: updateUserTags": Indicates the operation name was misspelled or unsupported; ensure correct operation selection.
  • API errors related to authorization or resource not found usually indicate invalid credentials or incorrect DIDs.

• Resolutions:

  • Verify all required fields are correctly filled.
  • Confirm the API key credential is valid and has necessary permissions.
  • Check that tags are provided as an array of strings or comma-separated strings (the code splits comma-separated tags).
  • Enable "Continue On Fail" in the node settings to handle partial failures gracefully.

Links and References

• Blocklet Server API Documentation (hypothetical link)
• n8n documentation on Creating Custom Nodes
• General info on Decentralized Identifiers (DIDs): https://w3c.github.io/did-core/

Note: The node internally converts tags that contain commas into multiple numeric tag IDs before sending them to the API, so input tags can be either single tags or comma-separated lists.