Blocklet Service icon

Blocklet Service

Consume Blocklet Service API
Join our community

Actions10

Overview

This node interacts with a Blocklet Service API to manage users and their tags. Specifically, the "Update User Tags" operation allows you to update the tags associated with a particular user identified by their DID (Decentralized Identifier). This is useful in scenarios where you want to categorize or label users dynamically based on certain criteria or events.

Practical examples include:

  • Assigning new interest tags to a user after they complete a survey.
  • Updating user segmentation tags for targeted marketing campaigns.
  • Removing or adding tags to reflect changes in user status or preferences.

Properties

Name Meaning
User DID The Decentralized Identifier (DID) of the user whose tags you want to update.
Tag Names or IDs A list of tag names or IDs to assign to the user. You can select from existing tags or specify them using expressions. Multiple values are supported.

Output

The output JSON contains the response from the Blocklet Service API after updating the user's tags. It typically includes details about the updated user object, reflecting the new set of tags assigned.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests to the Blocklet Service API.
  • The node depends on the Blocklet Service API being accessible and properly configured.
  • Uses internal helper functions to make API requests and handle pagination and sorting when applicable.

Troubleshooting

  • Common issues:

    • Providing an invalid or empty User DID will cause the API request to fail.
    • Specifying tag names or IDs that do not exist in the system may result in errors or no changes applied.
    • Network connectivity problems or incorrect API credentials will prevent successful execution.

  • Error messages:

    • "Not implemented user action: updateUserTags": Indicates a mismatch between the requested operation and the node's implementation; ensure the operation name is correct.
    • API error messages returned from the service will be passed through; check the message for details such as invalid parameters or authentication failures.

  • Resolutions:

    • Verify that the User DID is correct and corresponds to an existing user.
    • Use the "Tag Names or IDs" property’s load options to select valid tags or confirm tag IDs exist.
    • Ensure the API key credential is valid and has sufficient permissions.
    • Check network connectivity and endpoint availability.

Links and References

Discussion