Actions10
- Blocklet Actions
- Tag Actions
- User Actions
Overview
This node interacts with a Blocklet Service API to manage users. Specifically, the "Remove User" operation deletes a user identified by their DID (Decentralized Identifier) from the service. This is useful in scenarios where you need to programmatically revoke access or clean up user data from your system.
Practical examples include:
- Automatically removing users who have unsubscribed or violated terms.
- Cleaning up test or temporary users after certain workflows.
- Integrating user lifecycle management into broader automation pipelines.
Properties
| Name | Meaning |
|---|---|
| User DID | The Decentralized Identifier (DID) of the user to be removed. This uniquely identifies the user in the Blocklet Service. |
Output
The output JSON contains the response from the Blocklet Service API after attempting to remove the user. Typically, this will confirm whether the removal was successful or provide error details if it failed.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Blocklet Service API.
- The node depends on the
blockletServiceApiRequestfunction to communicate with the external API. - Proper configuration of the API credentials within n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Invalid or missing User DID: Ensure the DID provided is correct and corresponds to an existing user.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Network or API downtime: Check connectivity and the status of the Blocklet Service API.
Error messages:
"Not implemented user action: removeUser": Indicates a misconfiguration or unsupported operation; ensure the operation parameter is set exactly to "removeUser".- API error responses will be passed through; check the message for details such as "User not found" or permission denied.
Links and References
- Blocklet Service API Documentation (general reference for API endpoints)
- n8n documentation on Creating Custom Nodes