Blocklet Server icon

Blocklet Server

Consume Blocklet Server API
Join our community

Actions10

Overview

This node interacts with the Blocklet Server API to update the approval status of a user within a specific Blocklet app (team). It allows you to mark whether a user is approved or not, which can be useful for managing user access, permissions, or workflow states in applications that rely on user approval processes.

Common scenarios:

  • Automatically approving or revoking approval for users based on external triggers.
  • Integrating user approval workflows into automation pipelines.
  • Managing user states in team-based Blocklet apps.

Example:
You might use this node to approve a user after they complete a verification step in your system, by setting the "User Approved?" property to true.

Properties

Name Meaning
App DID DID (Decentralized Identifier) of the Blocklet app (team) where the user belongs.
User DID DID of the user whose approval status you want to update.
User Approved? Boolean flag indicating whether the user should be marked as approved (true) or not (false).

Output

The node outputs JSON data representing the updated user object returned from the Blocklet Server API after changing the approval status. This typically includes user details such as their DID, approval status, and possibly other metadata related to the user.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests to the Blocklet Server API.
  • The node depends on the Blocklet Server API being accessible and properly configured for the target team/app.

Troubleshooting

  • Common issues:

    • Invalid or missing App DID or User DID will cause the API request to fail.
    • Insufficient permissions or invalid API credentials may result in authorization errors.
    • Network connectivity problems can prevent communication with the Blocklet Server API.

  • Error messages:

    • "Not implemented user action: updateUserApproval": Indicates a misconfiguration or unsupported operation; ensure the operation name is correct.
    • API error messages related to authentication or resource not found usually mean the provided DIDs or credentials are incorrect.

  • Resolution tips:

    • Double-check the App DID and User DID values.
    • Verify that the API key credential is valid and has necessary permissions.
    • Ensure the Blocklet Server API endpoint is reachable from your n8n instance.

Links and References

Discussion