Crowd Handle icon

Crowd Handle

Extract handle details through the ADA handle public API
Join our community

Overview

This node resolves ADA (Cardano) blockchain handles using the public API of a service that manages ADA handles. It takes an ADA handle name as input and fetches the associated Cardano address and related details from the external API. This is useful for workflows that need to translate human-readable ADA handles into blockchain addresses for transactions, verification, or data enrichment.

Practical examples include:

  • Automatically resolving user handles to their Cardano addresses before sending tokens.
  • Validating ADA handles in user-submitted forms by checking their existence and retrieving associated addresses.
  • Enriching datasets with blockchain address information based on known handles.

Properties

Name Meaning
Handle Name The ADA handle name to resolve (without the $ prefix). For example, crowdtrendz.

Output

The node outputs an array with one item per input. Each output item contains a JSON object with the following fields:

  • handleName: The original handle prefixed with $.
  • cleanHandleName: The handle without the $ prefix.
  • cardanoAddress: The resolved Cardano blockchain address if found; otherwise null.
  • status: A string indicating the resolution status. Possible values:
    • "success": Address was successfully resolved.
    • "not_found": No address found for the given handle.
    • "error": An error occurred during resolution.
  • apiResponse: The full raw response object returned by the external API.
  • resolvedWith: A string indicating the source of resolution, here always "handle.me_api".
  • error (only present if status is "error"): The error message describing what went wrong.

The node does not output any binary data.

Dependencies

  • Requires internet access to call the external ADA handle resolution API at https://api.handle.me/handles/{handle}.
  • Needs an HTTP request helper available in the n8n environment to perform GET requests.
  • No special credentials are required as the API appears to be public.

Troubleshooting

  • Empty Handle Name: If the input handle is empty or only whitespace, the node will throw an error "Handle name cannot be empty". Ensure the input property is correctly set.
  • Invalid Handle Format: The node automatically strips a leading $ if present, but other invalid characters may cause the API to fail.
  • API Errors or Network Issues: If the external API is unreachable or returns an error, the node will either throw an error or continue with an error status depending on the workflow's "Continue On Fail" setting.
  • Not Found Status: If the handle does not exist in the API database, the node returns status "not_found" with no Cardano address.
  • To resolve errors, verify network connectivity, ensure valid handle names, and check the external API availability.

Links and References

Discussion