Blocklet Server icon

Blocklet Server

Consume Blocklet Server API

Overview

This node interacts with the Blocklet Server API to manage tags within a blocklet app (team). Specifically, the "Delete Tag" operation removes a tag identified by its ID from a specified blocklet app. This is useful for maintaining and organizing tags by removing obsolete or incorrect ones.

Practical example: If you have a team managing content or users categorized by tags, and a tag is no longer relevant, you can use this node to delete that tag programmatically as part of your workflow automation.

Properties

Name Meaning
App DID The Decentralized Identifier (DID) of the blocklet app (team) where the tag exists.
ID The unique identifier of the tag to be deleted. Usually auto-generated when the tag was created.

Output

The output is a JSON object representing the response from the Blocklet Server API after attempting to delete the tag. It typically contains confirmation of deletion or details about the deleted tag.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Blocklet Server API.
  • The node depends on the blockletServerApiRequest function to communicate with the external Blocklet Server service.
  • Proper configuration of the API authentication in n8n credentials is necessary.

Troubleshooting

  • Common issues:
    • Missing or invalid App DID or Tag ID will cause the request to fail.
    • Network or authentication errors if the API key is not configured correctly.
  • Error messages:
    • "Not implemented tag action: deleteTag": Indicates the operation name might be misspelled or unsupported; ensure the operation parameter is exactly "deleteTag".
    • API error messages related to authorization or resource not found usually mean the App DID or Tag ID is incorrect or the user lacks permission.
  • Resolution:
    • Verify that the App DID and Tag ID are correct and exist.
    • Check API credentials and permissions.
    • Enable "Continue On Fail" in the node settings to handle errors gracefully in workflows.

Links and References

Discussion