Actions10
- Blocklet Actions
- Tag Actions
- User Actions
Overview
The "Get User" operation of the Blocklet Server node retrieves detailed information about a specific user within a given Blocklet app (team). This operation is useful when you need to fetch user profile data, including optional related information such as connected accounts, tags, and passports associated with that user.
Practical scenarios include:
- Fetching user details for display in an admin dashboard.
- Retrieving user metadata before performing updates or audits.
- Integrating user information into workflows that require user verification or tagging.
Properties
| Name | Meaning |
|---|---|
| App DID | The Decentralized Identifier (DID) of the Blocklet app (team) where the user belongs. |
| User DID | The Decentralized Identifier (DID) of the user whose information is being retrieved. |
| Enabled Connected Account | Boolean flag indicating whether to search for the user's enabled connected account. |
| Include Tags | Boolean flag indicating whether to include the tags associated with the user in the response. |
| Include Connected Accounts | Boolean flag indicating whether to include all connected accounts of the user in the response. |
| Include Passports | Boolean flag indicating whether to include the passports associated with the user. |
Output
The output JSON contains the user data fetched from the Blocklet Server API. It includes the core user profile identified by the provided User DID within the specified app (team).
Depending on the input properties, the output may also include:
- Tags: Metadata tags assigned to the user.
- Connected Accounts: External accounts linked to the user.
- Passports: Verified credentials or identity documents associated with the user.
- Enabled Connected Account: Specific connected account flagged as enabled.
The structure is a JSON object representing the user and optionally nested arrays or objects for tags, connected accounts, and passports.
This node does not output binary data.
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 app (team).
- No additional external dependencies are required beyond the API access.
Troubleshooting
Common Issues:
- Invalid or missing App DID or User DID will cause the API request to fail.
- Insufficient permissions or invalid API credentials can result in authorization errors.
- Requesting optional fields (tags, connected accounts, passports) for users without those associations may return empty or partial data.
Error Messages:
"Not implemented user action: getUser": Indicates a misconfiguration or unsupported operation; ensure the operation name is correct.- API errors related to authentication or resource not found typically indicate issues with the provided DIDs or credentials.
Resolution Tips:
- Verify that the App DID and User DID are correct and exist in the Blocklet system.
- Ensure the API key credential has sufficient permissions.
- Use the boolean flags judiciously to avoid requesting unnecessary data.