Actions4
- Allocation Actions
- Certificate Actions
Overview
This node interacts with the Dots eco API to fetch a list of certificates associated with a specific user and application. It is useful in scenarios where you need to retrieve all certificates issued to a particular user within an application context, such as for displaying user achievements, verifying issued certificates, or managing certificate records.
For example, if you have an application that issues environmental impact certificates to users, this node can fetch all certificates linked to a given user ID and application token, enabling you to display or process them further.
Properties
| Name | Meaning |
|---|---|
| Application Token | Mandatory string representing the application ID and the first part of the application UUID stored in Dots.eco. Identifies the application context for fetching certificates. |
| Remote User ID | Mandatory string representing the User ID to whom the certificates were issued. Used to filter certificates belonging to this user. |
Output
The output is a JSON array containing the list of certificates fetched from the Dots eco API for the specified application token and remote user ID. Each item in the array represents a certificate object with details as returned by the API.
No binary data is output by this operation.
Dependencies
- Requires an active connection to the Dots eco API.
- The node depends on credentials configured with:
- A base URL for the Dots eco API.
- An API authentication token (or equivalent) to authorize requests.
- The node uses HTTP GET requests to the endpoint pattern:
/certificate/list/{app_token}/{remote_user_id}.
Troubleshooting
- Missing or invalid API base URL: If the API base URL is not set in the credentials or is empty, the node will throw an error prompting to add the API base URL under credentials.
- Authentication errors: Ensure the API authentication token or credentials are valid and have sufficient permissions to access the certificate list endpoint.
- Invalid input parameters: Both
Application TokenandRemote User IDare required. Missing or incorrect values may result in empty responses or API errors. - Network issues: Connectivity problems to the Dots eco API server will cause request failures; verify network access and API availability.
Links and References
- Dots eco API Documentation (Assumed link, replace with actual if available)
- n8n HTTP Request Node documentation for understanding requestWithAuthentication usage: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/